On 06/23/2011 11:41 AM, Kevin A. McGrail wrote: >> [Now if only the apache.org DNS administrator would insert an SPF >> record for bugzilla's use, the world would be one step closer to >> perfect.] ;-) >> > Are you having deliverability issues that justify opening a JIRA > ticket for this? If so, I'm happy to ask.
Like the bounce you just got for responding to [email protected] (much like responding to [email protected])? The bugzilla commenter will not see your reply. % host -tmx bugzilla.spamassassin.org bugzilla.spamassassin.org is an alias for issues.apache.org. % host -tmx issues.apache.org. issues.apache.org has no MX record Oddly enough, it actually makes sense for that domain to lack an MX record since it doesn't accept /incoming/ mail. That said, challenge-response and sender-verify (sender callouts, SAV) systems (both of which are bad practices for other reasons) break when unable to find a sender's MX. Additionally, I believe some MTAs will block envelope-from domains lacking MX records wholesale. Given that unconventional setup, SPF seems highly appropriate. Adding an incoming MTA is too, though that's a little bit more work (not much, just set the MX record to an existing one, add the virtuserdomain, /dev/null a few virtusers, forward the required postmaster@, and error:nouser the rest ... alternatively, make it a spam trap e.g. by talking to Marc Perkel).
signature.asc
Description: OpenPGP digital signature
