I just got this On 9 Feb 2019, at 00:00, dovecot-request at dovecot.org wrote:> Your membership in the mailing list dovecot has been disabled due to > excessive bounces The last bounce received from you was dated > 02-Feb-2019. You will not get any more messages from this list until > you re-enable your membership. You will receive 1 more reminders like > this before your membership in the list is deleted. > > To re-enable your membership, you can simply respond to this message > (leaving the Subject: line intact), or visit the confirmation page at > > https://dovecot.org/mailman/confirm/dovecot/41881d?When clicking the link I get "Bad confirmation sting" and something about maybe the link expired. I see no connection attempts from dovecot.org over the last few days other than this message. -- If at first you don't succeed, destroy all evidence that you tried.
<!doctype html>
<html>
<head>
<meta charset="UTF-8">
</head>
<body>
<div>
For some reason mailman failed to "munge from" for senders with
dmarc policy ;(
</div>
<div>
<br>
</div>
<div>
It's now configured to always munge to avoid this again.
</div>
<div>
<br>
</div>
<div>
Aki
</div>
<blockquote type="cite">
<div>
On 09 February 2019 at 11:21 "@lbutlr via dovecot" <
<a
href="mailto:dovecot@dovecot.org">dovecot@dovecot.org</a>>
wrote:
</div>
<div>
<br>
</div>
<div>
<br>
</div>
<div>
I just got this
</div>
<div>
<br>
</div>
<div>
On 9 Feb 2019, at 00:00,
<a
href="mailto:dovecot-request@dovecot.org">dovecot-request@dovecot.org</a>
wrote:
</div>
<blockquote type="cite">
<div>
Your membership in the mailing list dovecot has been disabled due to
</div>
<div>
excessive bounces The last bounce received from you was dated
</div>
<div>
02-Feb-2019. You will not get any more messages from this list until
</div>
<div>
you re-enable your membership. You will receive 1 more reminders like
</div>
<div>
this before your membership in the list is deleted.
</div>
<div>
<br>
</div>
<div>
To re-enable your membership, you can simply respond to this message
</div>
<div>
(leaving the Subject: line intact), or visit the confirmation page at
</div>
<div>
<br>
</div>
<div>
<a href="https://dovecot.org/mailman/confirm/dovecot/41881d…"
rel="noopener"
target="_blank">https://dovecot.org/mailman/confirm/dovecot/41881d…</a>
</div>
</blockquote>
<div>
When clicking the link I get "Bad confirmation sting" and
something about maybe the link expired.
</div>
<div>
<br>
</div>
<div>
I see no connection attempts from dovecot.org over the last few days other
than this message.
</div>
<div>
<br>
</div>
<div>
<br>
</div>
<div>
--
</div>
<div>
If at first you don't succeed, destroy all evidence that you tried.
</div>
<div>
<br>
</div>
</blockquote>
<div>
<br>
</div>
<div class="io-ox-signature">
---
<br>Aki Tuomi
</div>
</body>
</html>
Juri Haberland
2019-Feb-09 18:48 UTC
offtopic: rant about thoughtless enabling DMARC checks [was: Re: Bounces?]
On 09/02/2019 10:44, Aki Tuomi via dovecot wrote:> For some reason mailman failed to "munge from" for senders with dmarc policy ;( > > It's now configured to always munge to avoid this again.I'd say, let Mailman throw all people off the list that have enabled DMARC checking without using exceptions for the lists they are on. It's a known fact that DMARC does not cope well with mailing lists. Blindly enabling DMARC checks without thinking about the consequences for themselves should not be the problem of other well behaving participants. Most people use OpenDMARC and there are patches to mark certain hosts as mailing lists senders, so it is possible. And everyone using p=reject should think about it as well - as I said, DMARC does not play well with mailing lists, so setting p=reject on a domain used to participate on mailing lists is not wise, to say the least. You should not follow Yahoo and AOL - you know, why they did it, don't you? And Aki, please go back to "munge only if needed" - munging all messages leads to a really bad "user experience". Thanks. Back to lurking, Juri