View Issue Details
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0016688||phpList 3 application||public||02-10-12 14:16||02-11-12 18:35|
|Priority||normal||Severity||feature||Reproducibility||have not tried|
|Target Version||Fixed in Version||2.11.8|
|Summary||0016688: gmail wants the precedence header|
|Description||We have just started to use PHPList and out initial tests when sending to GMail users are all being marked as SPAM. We have static forward and rDNS entries, SPF records are in place, and all messages are DKIM signed.|
Based on http://forums.phplist.com/viewtopic.php?t=9564 I have added a Reply-To header but that produced the same result.
On reading https://support.google.com/mail/bin/answer.py?hl=en&answer=81126&rd=1 under the section Format it says "Messages should indicate that they are bulk mail, using the 'Precedence: bulk' header field." though according to http://mantis.phplist.com/view.php?id=15562 that header got removed.
Even though it is discouraged for such a large provider would it not be better to adhere to their request ?
|Tags||No tags attached.|
Yes, interesting. I took out the "Precedence: bulk" which had been part of the headers from the start, as it seemed to be an old header and the RFC had superceded this value. Strange that Gmail still uses it, and I'll put it back in.
I still haven't cracked Gmail in it's way to identify SPAM. I suggest to get together with a few Gmail users and mark the emails as not spam, and quite soon, it'll be fine. phpList Hosted sends a fair amount to Gmail and they are not marked spam, in most cases. And all is set there as well, as you write, "rDNS, SPF and DKIM".
||added option USE_PRECEDENCE_HEADER, defaulting to true, so that ppl can switch it off if they don't like it.|