[Mailman-Users] Invitation or subscription on behalf list-owner
Hi there, I just set up mailman 2.14 integrate with postfix 2.8.2 under Ubuntu 11.04 for may small community to replace my old ecartis (aka listar). The one that I still struggling is how to send invitation or new member subscription or password reminder on behalf listname-ow...@domain.com so that when list owner invite or add new member which have no valid address will known at first place. Is there a way to to change invitation or adding new member on behalf listname-ow...@domain.com? From postfix log and mailman bounce log I see as below. Sep 4 16:20:31 dip13 amavis[9116]: (09116-11) Passed CLEAN, LOCAL [127.0.0.1] [127.0.0.1] mylist-boun...@list.dutaint.com - syafril.hermans...@yahoo.com, Message-ID: mailman.0.1315128025.13728.myl...@list.dutaint.com, mail_id: aJ$ Sep 4 16:20:31 dip13 postfix/smtp[13733]: 692F919C22B7: to=syafril.hermans...@yahoo.com, relay=127.0.0.1[127.0.0.1]:10024, delay=5.4, delays=0.04/0.03/0.01/5.4, dsn=2.0.0, status=sent (250 2.0.0 from MTA([127.0.0.1]:10025): 250 2.0.0 $ Sep 4 16:20:31 dip13 postfix/qmgr[6484]: 692F919C22B7: removed Sep 4 16:20:34 dip13 postfix/smtp[13742]: C95D619C2387: to=syafril.hermans...@yahoo.com, relay=b.mx.mail.yahoo.com[74.6.136.65]:25, delay=2.5, delays=0.01/0.02/0.68/1.8, dsn=5.0.0, status=bounced (host b.mx.mail.yahoo.com[74.6.136.65]$ Sep 4 16:20:34 dip13 postfix/cleanup[13732]: 530D419C2392: message-id=20110904092034.530d419c2...@dip13.dutaint.com Sep 4 16:20:34 dip13 postfix/qmgr[6484]: 530D419C2392: from=, size=3613, nrcpt=1 (queue active) Sep 4 16:20:34 dip13 postfix/bounce[13749]: C95D619C2387: sender non-delivery notification: 530D419C2392 Sep 4 16:20:34 dip13 postfix/qmgr[6484]: C95D619C2387: removed and mailman bounce log Sep 04 16:48:08 2011 (4903) mylist: syafril.hermans...@yahoo.com bounce score: 1.0 -- syafril --- Syafril Hermansyah -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
[Mailman-Users] Installed, now stumped
With some slight edits to the configure script, I've successfully installed mailman on my Hostmonster user account. Not knowing where to go from there, I went into the cgi-bin dir and ran 'admin' from my shell account. This error showed up in the log: admin(19369): File /home1/ancestr2/local/mailman/scripts/driver, line 106, admin(19369): if not request_method.lower() in ['get', 'post', 'head']: admin(19369): AttributeError: 'NoneType' object has no attribute 'lower' I commented out the offending lines (for the hell of it) and the script ran. I think I need to be pointed to a doc that tells me how to implement the front-end. What public directory do I need and what do I put into it? Thanks! Michael -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Installed, now stumped
I'd understand if mailman cannot be run from a user account. Hostmonster does provide it, but does not allow shell access to the archive. I need that for back-up purposes and to integrate my old archive with the new--and just because I'd expect that kind of access. How do I do this? * Find a way to run mailman as a machine user? * Find instructions to give to Hostmonster to allow archive permissions? * Find another provider? * Find another list server that will give me direct access? I've had no success with the latter. Thanks for any help. I'd love to get my list back up and running! -Michael With some slight edits to the configure script, I've successfully installed mailman on my Hostmonster user account. Not knowing where to go from there, I went into the cgi-bin dir and ran 'admin' from my shell account. This error showed up in the log: admin(19369): File /home1/ancestr2/local/mailman/scripts/driver, line 106, admin(19369): if not request_method.lower() in ['get', 'post', 'head']: admin(19369): AttributeError: 'NoneType' object has no attribute 'lower' I commented out the offending lines (for the hell of it) and the script ran. I think I need to be pointed to a doc that tells me how to implement the front-end. What public directory do I need and what do I put into it? Thanks! Michael -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Installed, now stumped
On Sat, 3 Sep 2011, Michael Cooley wrote: With some slight edits to the configure script, I've successfully installed mailman on my Hostmonster user account. Not knowing where to go from there, I went into the cgi-bin dir and ran 'admin' from my shell account. This error showed up in the log: admin(19369): File /home1/ancestr2/local/mailman/scripts/driver, line 106, admin(19369): if not request_method.lower() in ['get', 'post', 'head']: admin(19369): AttributeError: 'NoneType' object has no attribute 'lower' I commented out the offending lines (for the hell of it) and the script ran. This is not how you're meant to run admin. It's meant to be called from the web. The lines above show that the script is looking to see whichHTTP request method was used, and it's crashing because no request method was used. I think I need to be pointed to a doc that tells me how to implement the front-end. What public directory do I need and what do I put into it? You should look at the installation manual. You can read/download it from http://list.org/./site.html If your host is a webhost rather than a VPS (virtual server), you may find yourself running into difficulties, particularly with integrating Mailman with the mail transport agent. I don't know anything about Hostmonster but others here probably do. If this is your problem, you're going to have problems with all mailing list software in thie regard. Geoff. -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Installed, now stumped
On 9/3/2011 2:58 PM, Michael Cooley wrote: I'd understand if mailman cannot be run from a user account. Hostmonster does provide it, but does not allow shell access to the archive. I need that for back-up purposes and to integrate my old archive with the new--and just because I'd expect that kind of access. Hostmonster may be willing to seed your new archive with your old archive if you can provide a *nix mbox format file containing the archive. You can access your list's archive mbox file by first logging in to the archive with a URL like http://www.example.com/mailman/private/LISTNAME or however that looks for hostmonster and then retrieving http://www.example.com/mailman/private/LISTNAME.mbox/LISTNAME.mbox. You use the 'private' archive URL for this even if the archive is public. Another way to provide backup is to subscribe an address to the list and just backup the mail received at that address or, if your archive is public, use one or more services like http://www.mail-archive.com. How do I do this? * Find a way to run mailman as a machine user? You can't. You have to be an admin of the machine or a VPS in order to install and run a fully functioning Mailman. * Find instructions to give to Hostmonster to allow archive permissions? They won't because this would allow access to all the archives for all their customer's lists. * Find another provider? See http://wiki.list.org/display/COM/Mailman+hosting+services for suggestions. * Find another list server that will give me direct access? No Mailman host that hosts more than one customer's lists will give you this access because it's global. -- Mark Sapiro m...@msapiro.netThe highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Invitation or subscription on behalf list-owner
On 9/4/2011 3:19 AM, Syafril Hermansyah wrote: The one that I still struggling is how to send invitation or new member subscription or password reminder on behalf listname-ow...@domain.com so that when list owner invite or add new member which have no valid address will known at first place. Is there a way to to change invitation or adding new member on behalf listname-ow...@domain.com? Mailman is designed to send all mail with envelope from LISTNAME-bounces@... so that Mailman can process bounces. If you prefer that all bounces be processed manually by the list owner, and you control the MTA that delivers to Mailman, you could arrange aliases or whatever so that mail to -bounces addresses is delivered as if addressed to -owner. If you want only some bounces to be handled manually by the list owner, you would have to modify the source code that generates those messages. -- Mark Sapiro m...@msapiro.netThe highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Installed, now stumped
Thanks for the replies, guys. I had a mailman account several years ago with another provider that did provide direct access to the archive, hence my confusion on the matter. I like the idea of creating a user for back up. I can pipe the incoming it to hypermail or some other such thing. I've also resurrected a simple distribution script I wrote several years but I'm not sure that I want to go down that road. The archive is only in mbox/*nix format but that's okay for now. In any case, thanks for the clarification and suggestions! -Michael On 9/3/2011 2:58 PM, Michael Cooley wrote: I'd understand if mailman cannot be run from a user account. Hostmonster does provide it, but does not allow shell access to the archive. I need that for back-up purposes and to integrate my old archive with the new--and just because I'd expect that kind of access. Hostmonster may be willing to seed your new archive with your old archive if you can provide a *nix mbox format file containing the archive. You can access your list's archive mbox file by first logging in to the archive with a URL like http://www.example.com/mailman/private/LISTNAME or however that looks for hostmonster and then retrieving http://www.example.com/mailman/private/LISTNAME.mbox/LISTNAME.mbox. You use the 'private' archive URL for this even if the archive is public. Another way to provide backup is to subscribe an address to the list and just backup the mail received at that address or, if your archive is public, use one or more services like http://www.mail-archive.com. How do I do this? * Find a way to run mailman as a machine user? You can't. You have to be an admin of the machine or a VPS in order to install and run a fully functioning Mailman. * Find instructions to give to Hostmonster to allow archive permissions? They won't because this would allow access to all the archives for all their customer's lists. * Find another provider? See http://wiki.list.org/display/COM/Mailman+hosting+services for suggestions. * Find another list server that will give me direct access? No Mailman host that hosts more than one customer's lists will give you this access because it's global. -- Mark Sapiro m...@msapiro.netThe highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Invitation or subscription on behalf list-owner
On 09/04/2011 10:09 PM, Mark Sapiro wrote: Is there a way to to change invitation or adding new member on behalf listname-ow...@domain.com? Mailman is designed to send all mail with envelope from LISTNAME-bounces@... so that Mailman can process bounces. If you prefer that all bounces be processed manually by the list owner, and you control the MTA that delivers to Mailman, you could arrange aliases or whatever so that mail to -bounces addresses is delivered as if addressed to -owner. No, I only need (mass) invitation, adding new (mass) subscription (and password reminder) send on behalf list-ow...@domain.com while the rest I let Mailman bounce handler to handle the job. Base on my experience on old Ecartis, there are a lot of occasion the the new member address are not valid either because the person who inform him/her are not correct or the list-owner made typo. I know that sooner or later non-valid member will be automatically unsubcribe by Mailman bounce handler, but if list-owner known first they can make correction as soon as possible. This kind of features will help to make my Mailman more efficient while using my limited resources. If you want only some bounces to be handled manually by the list owner, you would have to modify the source code that generates those messages. I am not programmer, I would prefer other workaround (if any) :-) I have made/add recipient_bcc_map to handle all mail address to listname-bou...@domain.com always bcc: to listname-ow...@domain.com, but apparently this setting not working as expected when the receiver MTA reject the message on smtp level. -- syafril --- Syafril Hermansyah -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] postfix+mailman - User unknowninvirtualmailboxtable
On Sat, 3 Sep 2011 10:04:19 -0700 Mark Sapiro m...@msapiro.net wrote: joyd...@infoservices.in wrote: I have set SMTPHOST = 'localhost' at /usr/lib/mailman/Mailman/mm_cfg.py and this has solved the issue. I'm glad your group mismatch problem is solved, but I can assure you that setting SMTPHOST = 'localhost' in mm_cfg.py is not what solved it. First of all, this is no different from the Defaults.py setting and thus didn't change anything. More importantly, SMTPHOST is used by Mailman only to determine to what host to connect for SMTP to deliver outgoing mail. It has nothing at all to do with mail delivery TO Mailman. When I referred to the 'local' transport, I was refering to the Postfix module that was actually piping mail to Mailman. I.e. in a Postfix log entry for delivery to Mailman what you see as see relay= So I don't know what actually solved your problem. Perhaps you removed list aliases from /etc/aliases and neglected to run newaliases or postalias /etc/aliases until sometime later or you did something else that solved the problem, but it wasn't just setting SMTPHOST = 'localhost' in mm_cfg.py. Well.. then I am also confused to think what actually solve the issue... When I first face the gid problem, I have removed the aliases from /etc/aliases and add hash:/var/lib/mailman/data/aliases at the alias section, and not run newaliases any more as suse automatically add/remove aliases from /var/lib/mailman/data/aliases; I have come to know this from suse doc and also confirm by checking the file. Even after all those steps, I faced the gid issue. And now with SMTPHOST = 'localhost', I don't have it any more. So I am also confused what solved the issue. Though I am relaxed... the list is working :-) -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Invitation or subscription on behalf list-owner
Syafril Hermansyah wrote: On 09/04/2011 10:09 PM, Mark Sapiro wrote: Is there a way to to change invitation or adding new member on behalf listname-ow...@domain.com? [...] No, I only need (mass) invitation, adding new (mass) subscription (and password reminder) send on behalf list-ow...@domain.com while the rest I let Mailman bounce handler to handle the job. 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()) 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. Base on my experience on old Ecartis, there are a lot of occasion the the new member address are not valid either because the person who inform him/her are not correct or the list-owner made typo. I know that sooner or later non-valid member will be automatically unsubcribe by Mailman bounce handler, but if list-owner known first they can make correction as soon as possible. Understood. [...] I have made/add recipient_bcc_map to handle all mail address to listname-bou...@domain.com always bcc: to listname-ow...@domain.com, but apparently this setting not working as expected when the receiver MTA reject the message on smtp level. http://www.postfix.org/postconf.5.html says about recipient_bcc_maps: 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. 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. -- Mark Sapiro m...@msapiro.netThe highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] postfix+mailman - User unknowninvirtualmailboxtable
J. Bakshi wrote: Well.. then I am also confused to think what actually solve the issue... When I first face the gid problem, I have removed the aliases from /etc/aliases and add hash:/var/lib/mailman/data/aliases at the alias section, and not run newaliases any more as suse automatically add/remove aliases from /var/lib/mailman/data/aliases; I have come to know this from suse doc and also confirm by checking the file. It is correct that with MTA = 'Postfix' Mailman automatically runs /usr/sbin/postalias /path/to/data/aliases whenever aliases are updated,and likewise /usr/sbin/postmap /path/to/data/virtual-mailman if there are POSTFIX_STYLE_VIRTUAL_DOMAINS. However it doesn't update /etc/aliases.db. Thus, if you just removed Mailman's aliases from /etc/aliases and did not run newaliases or postalias /etc/aliases, /etc/aliases.db still had the Mailman aliases and that was the problem. Then at some point, you did update /etc/aliases.db and that is what fixed the problem. Even after all those steps, I faced the gid issue. And now with SMTPHOST = 'localhost', I don't have it any more. So I am also confused what solved the issue. Though I am relaxed... the list is working :-) As I said. I'm glad it's working, but you could remove the SMTPHOST = 'localhost' from mm_cfg.py, and it will continue to work. -- Mark Sapiro m...@msapiro.netThe highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] postfix+mailman - User unknowninvirtualmailboxtable
On Sun, 4 Sep 2011 22:30:32 -0700 Mark Sapiro m...@msapiro.net wrote: J. Bakshi wrote: Well.. then I am also confused to think what actually solve the issue... When I first face the gid problem, I have removed the aliases from /etc/aliases and add hash:/var/lib/mailman/data/aliases at the alias section, and not run newaliases any more as suse automatically add/remove aliases from /var/lib/mailman/data/aliases; I have come to know this from suse doc and also confirm by checking the file. It is correct that with MTA = 'Postfix' Mailman automatically runs /usr/sbin/postalias /path/to/data/aliases whenever aliases are updated,and likewise /usr/sbin/postmap /path/to/data/virtual-mailman if there are POSTFIX_STYLE_VIRTUAL_DOMAINS. However it doesn't update /etc/aliases.db. Thus, if you just removed Mailman's aliases from /etc/aliases and did not run newaliases or postalias /etc/aliases, /etc/aliases.db still had the Mailman aliases and that was the problem. Then at some point, you did update /etc/aliases.db and that is what fixed the problem. Even after all those steps, I faced the gid issue. And now with SMTPHOST = 'localhost', I don't have it any more. So I am also confused what solved the issue. Though I am relaxed... the list is working :-) As I said. I'm glad it's working, but you could remove the SMTPHOST = 'localhost' from mm_cfg.py, and it will continue to work. Thanks a lot for all your kind support. Without your suggestion and help, I might not be able to run the lists as soon as it is now. I appreciate your kind help to make the list active. -many many thanks -with best regards -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
