Hi! My forum has a lot of imported users that have a specific email domain that doesn’t work anymore. A few thousand users have such an email address. It was not an issue until now, but I increased suppress digest email after days value, and my forum sent a lot of digest emails, including to a lo…

I think I might UserEmail.where("email like '%@brokendomain.com'").each do |e| e.update(email: SecureRandom.hex + "@email.invalid) end Yours could work too, but Im’ not sure if the User model got updated to be able to do a u.email.include? after they moved emails to another model/table.

For some reason I didn’t find this topic using the search… I guess I panicked! :sweat_smile: Thanks you very much for your fast answer!

But if there are a zillion email addresses like bademail.domain, maybe what you want to do is something like rake posts:remap['bademail.domain', 'no-email.invalid'] as described in Replace a string in all posts . That will make all of those email addresses such that Discourse won’t send to them. An…

Yeah, I thought about doing this to get rid of these email domains. I notice that a Discourse method creates @no-email.invalid emails: app/services/user_merger.rb main Invite .with_deleted .where(invited_by_id: @source_user.id) …

[이미지] Canapin: I’m not sure to understand why I should remap in posts I’m fairly certain that posts:remap remaps that domain across all tables, but they had to put it in some class. You could also just write your own replacement in the UserEmails table (or whatever it’s called). I’m fairly …

Neat. So I guess this would do the trick? User.find_each do |u| if u.email.include? "@brokendomain.com" u.update(email: SecureRandom.hex + "@email.invalid") end end

I tried my script just to see if it was returning the target email addresses and it works. Your script should be faster than mine since you use a query to select specific email domains instead of looping through all the users. Thank you very much for your help :+1:

Ooops. Here’s the remap I meant. It’s just discourse remap old new See Change the domain name or rename your Discourse . I think that the above would work, but the UserEmails solution is probably a tiny bit better.

[이미지] pfaffman: I think that the above would work, but the UserEmails solution is probably a tiny bit better. Thank you. This is the one I used. More than 5000 users of a total of 17000 users had such email domains. No wonder the number of bounces when I increased suppress digest email after…

[이미지] pfaffman: I’m fairly certain that whatever.invalid will tell The World that it’s an invalid address and it won’t try to send it. This is special handling by Discourse for anything ending in .invalid, which is a reserved TLD.

사용자 이메일 도메인이 너무 많아 작동하지 않아 Mailgun 도메인이 비활성화되었습니다: 어떻게 해야 하나요?

지원

pfaffman (Jay Pfaffman) 10월 20, 2020, 7:51오후 2

Check out Handling bouncing e-mails

글		댓글	조회수
Migrated forum with many invalid (bouncing) emails Support	1	984	7월 23, 2019
How can I bulk remap/update user email addresses? Support	13	3035	1월 29, 2017
Mailgun "temporarily disabled due to high bounce rate" Support	9	4228	6월 1, 2018
Discourse user email rejected by recipients what is the best practice for this user Support	6	788	8월 12, 2021
Migrating users with invalid emails Support	3	959	4월 20, 2017

사용자 이메일 도메인이 너무 많아 작동하지 않아 Mailgun 도메인이 비활성화되었습니다: 어떻게 해야 하나요?

Related topics