Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Address "Spammy" Outgoing Emails / Comply with X-Barracuda-Spam-Report Rules #1007

Open
aaronskiba opened this issue Feb 4, 2025 · 0 comments

Comments

@aaronskiba
Copy link
Collaborator

It turns out that indeed our Barracuda email security filters have blocked the messages with subject "Confirm your DMP Assistant account" that were sent from [email protected]. These messages matched some high-scoring proprietary Barracuda rules and ended up being dropped.

Here is the Barracuda spam report for a message received today:

X-Barracuda-Spam-Report: Code version 3.2, rules version 3.2.3.136681
      Rule breakdown below
       pts rule name description
      ---- ---------------------- --------------------------------------------------
      0.00 MIME_HTML_ONLY BODY: Message only has text/html MIME parts
      0.00 NO_REAL_NAME From: does not include a real name
      -0.00 DKIM_VERIFIED Domain Keys Identified Mail: signature passes
       verification
      0.00 DKIM_SIGNED Domain Keys Identified Mail: message has a signature
      0.00 HTML_MESSAGE BODY: HTML included in message
      1.00 TVD_PH_SUBJ_ACCOUNTS_POST TVD_PH_SUBJ_ACCOUNTS_POST
      5.00 BSF_SC0_MV0979 BSF_SC0_MV0979
      0.50 BSF_SC7_SA578_CH Custom Rule SA578_CH
      5.50 BSF_SC7_SA578e Custom Rule SA578e

I've opened a support case with Barracuda to try and find a solution, but I wanted to give you an update on what was going on. Perhaps there might be something that could be done from your side too to avoid those rules. Sending the message in plain text might help. Using the real name instead of email address in the "Welcome" sentence might help. If you must really send HTML-mail (why, oh, why?), at least compose it properly and definitely send the text/plain equivalent in a multipart/alternative message.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant