Autoreplies confirm subscription invitations

Bug #265831 reported by Stoneyb on 2003-01-05
4
Affects Status Importance Assigned to Milestone
GNU Mailman
Status tracked in 3.0
2.1
Medium
Mark Sapiro
3.0
Low
Unassigned

Bug Description

I'm not sure of the exact circumstances (maybe
personalization needs to be on), bu t i fyou "invite"
people to join a mailing list, or, presumably, if
someone sends a message to list-join, and there is an
autoresponder at that address, the address is
subscribed to the list without the subscriber being
aware of it.

[http://sourceforge.net/tracker/index.php?func=detail&aid=662163&group_id=103&atid=100103]

Lukáš Lánský (kz-lukas) wrote :

Please note that RFC 3834 says: "Automatic responses SHOULD NOT be issued in response to any message which contains an Auto-Submitted header field (see below), where that field has any value other than "no"." I think that system messages from Mailman are in scope of this header semantics (with the value "auto-generated") and we would solve the problem if we implement this. Do you agree? I would gladly implement it.

Mark Sapiro (msapiro) wrote :

I am testing an implementation that would include an Auto-Submitted: auto-generated header in invitations and in subscription confirmations from web subscribes and from email subscribes from a 'different' address. For email subscribes from 'this' address the header included is Auto-Submitted: auto-replied.

Changed in mailman:
assignee: nobody → Mark Sapiro (msapiro)
milestone: 2.1-stable → 2.1.15
status: New → In Progress
Barry Warsaw (barry) wrote :

Mark, is there a MM3 task lurking in here too?

Mark Sapiro (msapiro) on 2012-03-27
tags: added: mailman3
removed: x-un-subscribing

On Mar 28, 2012, at 04:45 PM, Bernard wrote:

>** Changed in: mailman/2.1
> Status: Fix Committed => Confirmed
>
>** Changed in: mailman/3.0
> Status: New => Confirmed

Bernard,

While I am glad you've found some enthusiasm for contributing to Mailman,
please stop changing our bug statuses out from underneath us. You're just
making our work harder this way.

We would welcome you becoming more involved in Mailman, but it's important to
understand our work flow first. Introduce yourself on the mailman-developers
mailing list, and let us guide you on how to best participate in the project.

Thanks,
-Barry

Abhilash Raj (raj-abhilash1) wrote :

This bug has been moved to the new gitlab repo here: https://gitlab.com/mailman/mailman/issues/23

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers