[Mailman-Users] Mailman and dmark help -- please

[Mark Sapiro]

Sent previously, but inadvertently to the OP only. Much overlap with
Stephen's reply.

On 05/01/2015 07:14 AM, Dennis Longnecker wrote:
> I have a mailing list setup for our boy scout troop.  The site is running
> mailman version version 2.1.18-1.   I looking at various lists, I believe I
> have as much set as I can.
> 
> (Details for from_is_list) = Munge From


While it doesn't really say so, from_is_list should be considered
deprecated. Use Privacy options... -> Sender filters ->
dmarc_moderation_action instead for a less generally disruptive approach.


> I really -- really want the list set so when someone gets an e-mail from the
> list they can see who sent it and when they click reply it goes to the
> original sender.  When I have the remove sender option, etc. People don't
> know who the e-mail came from or how to directly reply.


What remove sender option? Have you set anonymous_list = Yes?


> I was reading about some DNS DMARC settings, but frankly it really confused
> me.  What I have observed:
> 
> E-mail from MSN to list
> Comcast Users = DOn't Get it
> AOL Users = Don't Get it
> Yahoo Users = Don't Get it
> users with arvixe accounts = Do Get it.


This isn't DMARC. msn.com doesn't publish a DMARC policy.


> E-mail from GMAIL to list
> Comcast Users = DOn't Get it
> AOL Users = Don't Get it
> Yahoo Users = Don't Get it
> users with arvixe accounts = Do Get it.


This isn't DMARC. gmail.com publishes a DMARC p=none policy.


> E-mail from Comcast to list
> Comcast Users = DO Get it
> AOL Users = Don't Get it
> Yahoo Users = Do Get it
> outlook.com = Do Get it
> users with arvixe accounts = Do Get it.


This isn't DMARC. comcast.net publishes a DMARC p=none policy. Also,
only AOL doesn't like it.


> E-mail from AOL to list
> Comcast Users = DO Get it
> AOL Users = Don't Get it
> Yahoo Users = Dont Get it
> outlook.com = Dont Get it
> users with arvixe accounts = Do Get it.


aol.com publishes DMARC p=reject. Comcast honors that policy, so
whatever DMARC mitigation policy is in effect seems to be working in
this case.


> E-mail from Outlook to list
> Comcast Users = DO Get it
> AOL Users = Don't Get it
> Yahoo Users = Dont Get it
> outlook.com = Dont Get it
> users with arvixe accounts = Do Get it.


This isn't DMARC. outlook.com publishes a DMARC p=none policy.


> E-mail from Yahoo to list
> Comcast Users = DO Get it
> AOL Users = Don't Get it
> Yahoo Users = Do Get it
> outlook.com = Do Get it
> users with arvixe accounts = Do Get it.


See AOL above. The same things apply to yahoo.com.


> Any sugestions?  My site is troop101-wa.org if looking at its DNS records
> could help.

I see you do have an SPF record which is good in general, but won't help
with DMARC. You might also consider DKIM signing your outgoing mail
which also will help in general but not with DMARC.

You clearly have deliverability issues, but they don't seem to be DMARC
related.

Also, simple From: munging for DMARC should preserve the From: display
name or list member's 'real name' in the resulting From: John Doe via
list <list at example.com> header and put the original From: data in
Reply-To: so with an RFC compliant MUA, 'reply' will go to the original
From: and 'reply all' will go to the original From: and the list.

What are your settings for General Options ->
 from_is_list
 anonymous_list
 first_strip_reply_to
 reply_goes_to_list
 reply_to_address
	
For your deliverability, you need to see the server's outgoing MTA logs
to see if any of the undelivered mail is rejected at SMTP time and why
and also look at Mailman's bounce log to see if mail is otherwise
bouncing. You probably have to get your hosting provider to do this if
you can. See <http://wiki.list.org/DOC/Mailman%20and%20CPanel>.

Also see <http://wiki.list.org/x/4030690> for some general information
on deliverability.

-- 
Mark Sapiro <mark at msapiro.net>        The highway is for gamblers,
San Francisco Bay Area, California    better use your sense - B. Dylan