[Mailman-Users] Re: Disable unsubscribe notification

2021-01-29 Thread Moritz Fromm

Hi,

Am 28.01.2021 um 21:22 schrieb Mark Sapiro:

Lists have a `send_goodbye_message` attribute which if `False` will do
what you want.

> [...]
> In the interim, you can set it via `mailman shell`.

Thanks, that's perfect!


In Core 3.3.3 this is exposed in REST, but not yet in
Postorius - 


Thanks for opening the issue, if I can find some Time I'll try to 
implement this option.


Best
Moritz

--
NaturFreunde Thüringen e.V.
Die Experten fürs Miteinander.
--
Mailman-Users mailing list -- mailman-users@python.org
To unsubscribe send an email to mailman-users-le...@python.org
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/mailman-users@python.org/
   https://mail.python.org/archives/list/mailman-users@python.org/


[Mailman-Users] Re: Mailing List Bounce Issues

2021-01-29 Thread steve lund
Mark,

...And everyone else who replied, yes, this does indeed look like a DMARC
issue. I looked at the help pages and it looks like some things can be
changed but from what I gather any changes would likely affect
functionality for the users.

I am a member of a different list that munged the FROM header to the list
address with the down side that ALL replies had to go back through the list
even if it was specific to one individual. Not a great experience just to
pick up a few members who had AOL email domains.

I'll forward the help pages to our ISP list admin to see if he has any
thoughts on changes that might help but not restrict functionality.

Thanks,
Steve

On Wed, Jan 27, 2021 at 2:12 PM Mark Sapiro  wrote:

> On 1/26/21 5:57 PM, steve lund wrote:
> >
> > We seem to be having all too frequent occurrences of multiple bounces
> that
> > seem to be related only to the domain of the address recipient.
>
>
> As pointed out in another reply, this is likely a DMARC issue and MM
> 2.1.34 has settings to mitigate this.
>
>
> > The interesting thing about this occurrence other than losing the name
> > associated with the email address (since the members were unsubscribed
> not
> > just disabled) is that I NEVER received ANY bounce notifications other
> than
> > the unsubscribe notification. I find this quite odd and unsettling
> > considering that the list shows that it IS configured to send earlier
> > bounce notifications and I have received them in the past... just not
> > leading up to this latest incident. The typical error message is:
> >
> > jonxx_daj...@yahoo.com  has been removed from
> > MSing-ride. (disabled address)
>
>
> That occurred after the users delivery was disabled by bounce and the
> notices to the user were exhausted. When the delivery was first
> disabled, (three weeks earlier with default bounce settings) there was a
> notice sent to the list admins about the disable if the list's admin
> Bounce processing -> bounce_notify_owner_on_disable setting is Yes.
>
> Also, you can set Bounce processing ->
> bounce_notify_owner_on_bounce_increment to Yes to be sent a notice when
> a bounce is received that increments the score.
>
> If one or both of these settings is Yes and you aren't receiving the
> notices, that's between Mailman's MTA and you.
>
>
> > So I guess that my question is whether or not these types of problems are
> > now endemic to all email lists or ifOur ISP is technically
> "challenged"
> > and
> >
> > 1. Doesn't know how to properly configure Mailman to send out the
> requested
> > notifications.
>
>
> Since you got the unsub notice, I'd expect that all requested notices
> have been sent.
>
>
> > 2. Continues to get blacklisted for sending SPAM even though they don't.
>
>
> What are your settings under Privacy options... -> Sender filters for
> dmarc_moderation_action and dmarc_quarantine_moderation_action? at a
> minimum, they should be Munge From and Yes respectively.
>
> --
> Mark Sapiro The highway is for gamblers,
> San Francisco Bay Area, Californiabetter use your sense - B. Dylan
> --
> Mailman-Users mailing list -- mailman-users@python.org
> To unsubscribe send an email to mailman-users-le...@python.org
> 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/mailman-users@python.org/
> https://mail.python.org/archives/list/mailman-users@python.org/
>
--
Mailman-Users mailing list -- mailman-users@python.org
To unsubscribe send an email to mailman-users-le...@python.org
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/mailman-users@python.org/
https://mail.python.org/archives/list/mailman-users@python.org/


[Mailman-Users] Re: Disable unsubscribe notification

2021-01-29 Thread Mark Sapiro
On 1/29/21 5:19 AM, Moritz Fromm wrote:
> Hi,
> 
> Am 28.01.2021 um 21:22 schrieb Mark Sapiro:
> 
>> In Core 3.3.3 this is exposed in REST, but not yet in
>> Postorius - 
> 
> Thanks for opening the issue, if I can find some Time I'll try to
> implement this option.


Sorry, It's already done. ;)


-- 
Mark Sapiro The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan
--
Mailman-Users mailing list -- mailman-users@python.org
To unsubscribe send an email to mailman-users-le...@python.org
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/mailman-users@python.org/
https://mail.python.org/archives/list/mailman-users@python.org/


[Mailman-Users] Re: Mailing List Bounce Issues

2021-01-29 Thread Mark Sapiro
On 1/29/21 5:38 AM, steve lund wrote:
> 
> ...And everyone else who replied, yes, this does indeed look like a DMARC
> issue. I looked at the help pages and it looks like some things can be
> changed but from what I gather any changes would likely affect
> functionality for the users.
> 
> I am a member of a different list that munged the FROM header to the list
> address with the down side that ALL replies had to go back through the list
> even if it was specific to one individual. Not a great experience just to
> pick up a few members who had AOL email domains.


Is this a Mailman list? Both Mailman 2.1 and Mailman 3 take pains to
create Munged From messages which exhibit the same behavior for 'reply'
and 'reply-all' as non-munged messages. Here's what we say:

> # MAS: We need to do some things with the original From: if we've munged
> # it for DMARC mitigation.  We have goals for this process which are
> # not completely compatible, so we do the best we can.  Our goals are:
> # 1) as long as the list is not anonymous, the original From: address
> #should be obviously exposed, i.e. not just in a header that MUAs
> #don't display.
> # 2) the original From: address should not be in a comment or display
> #name in the new From: because it is claimed that multiple domains
> #in any fields in From: are indicative of spamminess.  This means
> #it should be in Reply-To: or Cc:.
> # 3) the behavior of an MUA doing a 'reply' or 'reply all' should be
> #consistent regardless of whether or not the From: is munged.
> # Goal 3) implies sometimes the original From: should be in Reply-To:
> # and sometimes in Cc:, and even so, this goal won't be achieved in
> # all cases with all MUAs.  In cases of conflict, the above ordering of
> # goals is priority order.

I.e. preserving 'reply' and 'reply all' behavior is goal 3, but note
that "this goal won't be achieved in all cases with all MUAs".

I.e. some MUAs that don't follow RFC recommendations for replying may
not reply appropriately. This is an MUA issue. Mailman is doing the best
it can.

-- 
Mark Sapiro The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan
--
Mailman-Users mailing list -- mailman-users@python.org
To unsubscribe send an email to mailman-users-le...@python.org
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/mailman-users@python.org/
https://mail.python.org/archives/list/mailman-users@python.org/