Email stack:- dovecot
- postfix
- SPF
- DKIM
note: I basically followed the setup here (with minor adjustments):
https://library.linode.com/email/postfi ... 0.04-lucidMail server OS: - ubuntu 12.04
Mail client:- apple mail
Scenario:- I send an email to someone.
- They don't respond, and instead of sending a new email I just reply to the original email.
- e.g. "References:" and "In-Reply-To:" headers are the same as the original "Message-Id:" header.
- I receive a bounce-back email from
mailer-daemon@googlemail.com suggesting I visit this link:
http://mail.google.com/support/bin/answ ... wer=188131 - note: see below for relevant text from support link
SPF and DKIM info from bounced-back email headers:- spf=softfail (google.com: domain of transitioning
email@domain.com does not designate [string of numbers and chars] as permitted sender)
smtp.mail=email@domain.com;
- dkim=pass
header.i=@domain.com;
Relevant text from Google support link:Quote:
If you're a mail server administrator:
Ownership and Filtering
We recommend that you do not change the envelope sender when forwarding email to Gmail. Sometimes, when forwarding email, the envelope sender gets changed to your domain. When this happens, Gmail may learn that your domain is sending spam, and will treat other emails from this domain as spam as well.
Are you using procmail for forwarding?
Please note that procmail is one of the most common reasons why the envelope sender gets changed when forwarding. Adding the following to your config file will fix this issue:
SENDER=`formail -c -x Return-Path`
SENDMAILFLAGS="-oi -f $SENDER"
Alternatively, changing the envelope sender is ok if you do one of the following:
Put "SPAM" in the subject
OR discard any spam emails and not forward them to Gmail at all.
SpamAssassin is a free spam filter that can be used for identifying spam outside of Gmail, and putting "SPAM" in the subject.
Authentication
- Do not modify, remove or shuffle message headers or modify the body of the message. DKIM or DomainKeys signatures will break if the body is altered, and all authentication information will be lost.
- Common DKIM breakages include modifying the mime boundaries, anti-virus or anti-spam programs modifying the body of the message, expanding the message recipient using LDAP, and re-encoding the message.
- Several highly-phished domains have asked Gmail to enforce strict authentication checks on their mail. These domains include eBay, Paypal, and Google. If your mail server modifies the forwarded messages from these domains, these messages will be marked as phishing.
- One symptom of this problem is that a messages from these domains forwarded through your mail server to Gmail will have an Authentication-Results header that show that DKIM did not pass, while messages sent directly to Gmail will have a passing signature.
My questions:- Has anyone else had this issue, and if so, could you provide me with some guidance?
- Email I've sent has been bounced back three times, and each time the scenario has been the same (i.e. replying to an email I initially sent). What is causing this?
- Will setting up procmail fix this? I've scanned the documentation, however, it's not clear to me why it would fix.
- Could you suggest anything else I should be looking into to fix this?
Thanks in advance for help/guidance.
FAQ
Search
Members
Register
Login [ Anonymous ]
