Description of regular, non-Discourse flow. Presently (completely independent of Discourse), I use a published email address as an alias that sends an inquiry email message to a number of email addresses. The group rely on their email providers’ Spam detection. Most of them use Gmail. People work independently on answering inquiries. It sometimes leads to duplicated effort or other problems. How things might change using my Discourse. My Discourse instance is completely private and requires members to login. I’ve begun to use the Mail-Receiver plugin so members can reply to topics by email and it seems to work well. I’ve been reading about and testing the related Groups option that accepts incoming email to a custom address. I’m considering that for an inquiries email address. I can’t see how Mail-Receiver would adequately detect and prevent Spam. I’ve also read that the Discourse team itself is using incoming email as a Support feature, so perhaps Spam isn’t getting in their way.

[图片] tkforbes: I can’t see how Mail-Receiver would adequately detect and prevent Spam. There is a guide here: [图片] Filter known-bad sender domains from your mail-receiver Sysadmins If you run your own incoming mail, and you find that you’re getting more abusive mail than you’re willing to tolerate, this guide is for you! It’ll show you how to configure your mail-receiver container to block e-mail from any domain on a list you create, and how you can add and remove domains from that list over time. Setup Using the custom Postfix configuration guide, configure your mail-receiver container to have an /etc/postfix/shared volume (see the “Addendum” section at the bottom). … I haven’t had issues with spam e-mails sent to mail-receiver address, but there is a risk that can happen if you have the address listed in public registries those can start to get spam/marketing e-mail.

Yeah, I saw that guide. However, maintaining a list of banned domains isn’t an option. It’s impossible to stay ahead of the spammers - we get Spam daily to the addresses that are published on our web site, but at least most of those first go through detection services that we do not maintain i.e. Gmail, miab … I might get brave enough to try using a Discourse Group email address although I think I can predict that we won’t be able to live with the result. We could always go back to our original process, but I really liked the idea of being able to distribute the work in a natural manner and which preserves the communications.

[图片] tkforbes: Spam daily to the addresses that are published on our web site To avoid that probably protecting address from web crawlers if possible could help. I’m not certain how that is done, but have seen that implemented to have a captcha or just “click to show address” option could prevent crawler scrapping of address. Is simple to change address if spam gets too bad. When there is e-mail in will create staged user, with spam you can immediately block both e-mail and I.P. address of those.

I agree with you that blocking domains isn’t a solid general-purpose anti-spam measure – it’s more for whacking the occasional “heavy hitter”. It is entirely possible, though, to customise mail-receiver to do whatever additional pre-delivery filtering you need, such as running incoming messages through SpamAssassin or similar, since you have the entire Power of Postfix at your command. I’ve been considering building a “mail receiver 9001” that incorporates these sorts of things out of the box, but it’d need to be a sponsored effort, as I don’t personally have a need for it at present.

Subsequent to opening this topic a couple of years ago, we engaged in a test using a honeypot email address that is published on our web site. Humans would know not to use it. In all this time we have had just a small number of spam emails. I recently stumbled across the Rejected tab of the Discourse admin page called Email Logs. While there, I found numerous examples of Discourse rejecting spam email. An easy way for other admins to find their own examples is to type “autogenerated” into the Error filter box that appears on that page, or you could use this link when logged in as admin… https://yourdiscourse.com/admin/email-logs/rejected?to=contact&error=autogenerated In every case, the emailer attempting to send spam to us had an auto-reply address and this is one of the criteria that triggers rejection.

Mail-Receiver - 公开电子邮件地址，我需要担心垃圾邮件吗？

产品支持

Architect 2024 年8 月 21 日 13:48 2

这里有一个指南：

我没有遇到发送到 mail-receiver 地址的垃圾邮件问题，但如果该地址列在公共注册表中，则存在可能发生这种情况的风险，这些注册表可能会开始收到垃圾邮件/营销邮件。

话题		回复	浏览量
Reducing backscatter in email interface? Feature	22	3655	2025 年11 月 27 日
Allowing topic creation through direct delivery email in makes my forum vulnerable to spammers Product Support	16	2549	2019 年5 月 27 日
Any way to block incoming qq spam that generates backscatter? Product Support	4	1036	2018 年12 月 13 日
Spam Filter / Whitelist suggestions Self-hosting hosting	3	1868	2016 年10 月 15 日
Discourse Mailgun Routes Plugin	6	2600	2023 年1 月 18 日

Mail-Receiver - 公开电子邮件地址，我需要担心垃圾邮件吗？

相关话题