On Feb 28, 2014, at 12:49 PM, Matt Simerson <[email protected]> wrote:

> 
> On Feb 28, 2014, at 1:02 AM, Murray S. Kucherawy <[email protected]> wrote:
> 
>> On Thu, Feb 27, 2014 at 11:22 AM, Matt Simerson <[email protected]> 
>> wrote:
>>> Matt's message, as evaluated by Gmail, failed alignment, and was 
>>> consequently marked as spam.
>> 
>> Thanks to DMARC reports, the sender is quite aware. Of course I'd prefer 
>> that this list didn't invalidate my DKIM signatures. I'd also prefer that 
>> Google's SPF recognized that this list server is SPF permitted for 
>> @tnpi.net. But that's outside my ability to influence.
>> 
>> Have you reported that to Google?
> 
> Surely I have, and you likely have too, dozens of times over months and 
> months, using this cool new email technology called DMARC. ;-)
> 
> I may have done so again by pointing out the issue on this list. But no, I 
> didn't ever raise the issue with Google because back when I first noticed it 
> I still:
> 
>  a) wanted to fully understand the consequences of posting to lists with 
> p=reject
>  b) having recipients on this list that validate SPF differently provides 
> useful information
>  c) I haven't done enough debugging to determine exactly why it fails
>  d) Quite a few @gmail recipients on this list are conditioned to check their 
> Junk folders, so end up getting the messages anyway
> 
> For everyone besides Murray, the most serious consequence of posting to lists 
> from a domain with p=reject is upsetting the list administrator. That's why 
> when I remember, I post here from my @gmail address. When I forget, I get 
> DMARC reminders. :-)
> 

Other list management systems than mailman have a different approach and send a 
last ping before unsubscribing someone due to bounces. Because this probe is 
sent from the list domain, it does not bounce and the member stay subscribed.

The other way to alleviate it is to raise the limit of days of bouncing before 
unsubscribing someone. As long as people with p=reject don't contribute much to 
a list, then it is all fine, you are not passing the thresholds where mailman 
thinks all the members at gmail, yahoo, hotmail,... are not there anymore due 
to too much bouncing.

http://www.gnu.org/software/mailman/mailman-admin/node25.html

I suspect setting bounce_you_are_disabled_warnings to >0 could help on this 
list.


Attachment: signature.asc
Description: Message signed with OpenPGP using GPGMail

_______________________________________________
dmarc-discuss mailing list
[email protected]
http://www.dmarc.org/mailman/listinfo/dmarc-discuss

NOTE: Participating in this list means you agree to the DMARC Note Well terms 
(http://www.dmarc.org/note_well.html)

Reply via email to