[Mailman-Users] Invitation or subscription on behalf list-owner

[Syafril Hermansyah]

On 09/05/2011 12:20 PM, Mark Sapiro wrote:
> You can't quite get that level of granularity withoud making more
> extensive code modifications, but you can set the envelope sender to
> listname-owner for all list welcome messages by finding the definition
> of the SendSubscribeAck() method in the Deliverer class in
> Mailman/Deliverer.py and changing the last line from
> 
>         msg.send(self, verp=mm_cfg.VERP_PERSONALIZED_DELIVERIES)
> 
> to
> 
>         msg.send(self, verp=mm_cfg.VERP_PERSONALIZED_DELIVERIES,
>                  envsender=self.GetOwnerEmail())
> 
> You can set the envelope sender to listname-owner for all invitations
> by finding the definition of the InviteNewMember() method in the
> MailList class in Mailman/MailList.py and changing the last line from
> 
>         msg.send(self)
> 
> to
> 
>         msg.send(self, envsender=self.GetOwnerEmail())

Wow, it work as expected, hura :-)
Thank you very much!

> Password reminders are trickier. In standard GNU Mailman, a user gets a
> single reminder for all subscribed lists for a given host. Thus, this
> reminder comes from the site list, not from the list(s) to which the
> user is subscribed, but normally password reminders don't bounce. If
> the address is undeliverable, the user will get delivery disabled and
> eventually unsubscribed by normal bounce processing. The only time
> this doesn't occur is if the user has set nomail and then the user's
> address goes bad. In any case, for various complicated reasons (read
> all the comments in Mailman/Queue/BounceRunner.py), bounces of
> password reminders are sent to the owner of the site list.

OK, no problem

>    Optional BCC (blind carbon-copy) address lookup tables, indexed by
>    recipient address. The BCC address (multiple results are not
>    supported) is added when mail enters from outside of Postfix.

Understood, thanks.

> I.e., if the mail is accepted by a remote MX and then bounced,
> recipient_bcc_maps will be effective as the bounce comes from outside,
> but as you observe, if the outgoing message is regected during SMTP,
> the bounce does not enter from outside of Postfix so
> recipient_bcc_maps is not consulted.
> 
> What you could do is change the alias from
> 
> LISTNAME-bounces: "|/path/to/mailman/mail/mailman bounces LISTNAME"
> 
> to
> 
> LISTNAME-bounces: "|/path/to/mailman/mail/mailman bounces LISTNAME",
>      LISTNAME-owner
> 
> If you have Mailman/Postfix integration, you could even automate this
> by setting POSTFIX_ALIAS_CMD in mm_cfg.py to point to a script that
> would edit the -bounce aliases appropriately and then invoke
> /usr/sbin/postalias.

I have manually changes either on /etc/aliases and
/var/lib/mailman/data/virtual-mailman, and now all listname-bounce
copied to list-owner <Address> as expected.
Again, thank you for your help Mark.

BTW. What is the proper format of VIRTUAL_MAILMAN_LOCAL_DOMAIN  in
mm_cfg.py (or /var/lib/mailman/Mailman/Defaults.py) when I have multiple
domain in POSTFIX_STYLE_VIRTUAL_DOMAINS?

-- 
syafril
-------
Syafril Hermansyah