Jerry Barnabee via Mailman-Users writes:

 > I am running Mailman via CPANEL and I am not having these issues -
 > are you using CPANEL ?

It's almost never the software.  It's almost always the sending
domain's reputation and the recipient's spam paranoia.

 > When I lookup livingaudio.net <http://livingaudio.net/> it shows
 > that there is no DMARC record for that domain ? Most of the email
 > servers in the world now require DMARC records or they will reject
 > your emails.

Maybe this is new, but:
% host -t txt _dmarc.livingaudio.net
_dmarc.livingaudio.net descriptive text 
"v=DMARC1;p=quarantine;rua=mailto:[email protected];ruf=mailto:[email protected];";

That's something I hadn't thought of: Bernard's record says to
"quarantine" the email.  I don't think that should generate a
rejection, which would be some protection from DMARC bounces.

Note that DMARC is a demand by *senders* that receivers reject email
apparently from them in certain circumstances.  If there is a non-null
DMARC policy, most recipients will respect it.  But (outside of the
authoritarian crank faction of the IETF's email working group) I've
never heard a suggestion that *recipients* should demand a DMARC
record of senders.  I really doubt that Microsoft is that kind of
authoritarian crank, though -- their clients would notice loss of
*lots* of mail.

What Bernard needs is a DKIM record, and here it is:
% host -t txt default._domainkey.livingaudio.net
default._domainkey.livingaudio.net descriptive text "v=DKIM1; k=rsa; 
p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAxigpYyliFG2MbtvHRQF8pZabvm0PwIZSi1qbFbCGMQXBRC1NxfQeVEQkAptcn6kEZ115XDxONQj3mVooy8XJPOz9/s8uFS2prb8BstAwYRibjMvkPFPU1NYbnnKP90Zx1yo3ZeJ7ztDhKSXuR3y9l+iLgyFMr6mLsXTw3uZMrLQQ2KYMaQ/1LssiBswGcZHbK"
 
"pebH6LW+vVVd8RNtCh+1mn63Zxg1XVzdWr+txyH+uzFQhisPD3XXIAjYQxaz25Rn0N9j31Lj7b6H9PaKUexHdIJa7WFtMMDwqJQ9ko8KfpAXF8BL/wEkJXrURDnaJZvpL/j6S/LFJRiqjlAALW6WQIDAQAB;"

That's hard to look up without looking into message headers because
the pseudo-domain contains a "selector".  That can change arbitrarily
often, and there's no standard way to indicate the naming pattern or
schedule, so you need the s= parameter from a DKIM signature.  (In
theory a DNS zone transfer would give it to you, but those require
authorization from the domain owner these days.)

Steve

-- 
GNU Mailman consultant (installation, migration, customization)
Sirius Open Source    https://www.siriusopensource.com/
Software systems consulting in Europe, North America, and Japan
------------------------------------------------------
Mailman-Users mailing list -- [email protected]
To unsubscribe send an email to [email protected]
https://mail.python.org/mailman3/lists/mailman-users.python.org/
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: https://www.mail-archive.com/[email protected]/
    https://mail.python.org/archives/list/[email protected]/
Member address: [email protected]

Reply via email to