[Mailman-Users] Bug: couldn't subscribe to dev list by simply replying
Hi, Figured this would be the best place to report this. I just tried again to subscribe to the developers list and discovered that you couldn't confirm your subscription just by replying. The message text implies that the confirmation key should be in the subject, but the confirmation key was in the From address of the confirmation message (see below). Replying simply send me a message telling me that the subject line was being ignored. It seems the confirm code was also ignored. Not sure how it's meant to work but it's the first time I've had to resort to clicking on the URL. Oh and I notice that this is Mailman 2.1.12. :) Geoff. -- Forwarded message -- Date: Mon, 01 Feb 2010 13:04:18 +0100 From: mailman-developers-confirm+519716b18b6d4ddef39fd87d0e5abdf8c5ced...@python.o rg To: ge...@quitelikely.com Subject: Your confirmation is required to join the Mailman-Developers mailing list Mailing list subscription confirmation notice for mailing list Mailman-Developers We have received a request from ge...@quitelikely.com for subscription of your email address, ge...@quitelikely.com, to the mailman-develop...@python.org mailing list. To confirm that you want to be added to this mailing list, simply reply to this message, keeping the Subject: header intact. Or visit this web page: http://mail.python.org/mailman/confirm/mailman-developers/519716b18b6d4ddef39fd87d0e5abdf8c5ced755 Or include the following line -- and only the following line -- in a message to mailman-developers-requ...@python.org: confirm 519716b18b6d4ddef39fd87d0e5abdf8c5ced755 Note that simply sending a `reply' to this message should work from most mail readers, since that usually leaves the Subject: line in the right form (additional Re: text in the Subject: is okay). If you do not wish to be subscribed to this list, please simply disregard this message. If you think you are being maliciously subscribed to the list, or have any other questions, send them to mailman-developers-ow...@python.org. -- 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] List Locked Up...kind of
I have mailman on OSX 10.4.11 server and I set up a mailing list with 4 or 5 addresses in it to test stuff out. All seemed to work fine with adding, deleteing, sending mail and such so I imported about 50 addresses into the list from a different mail programs (via a csv file). Everything still seemed to work fine so I imported about 30,000 emails and stuff got flakey. The email lists won't send mail any more, and they won't show up in the OSX Server Admin but they do show up using the web interface. When I go to Server Admin and click the mail tab, the enable mailing lists check box is unchecked and in the bottom left of the window (to the left of the overview | logs | connections | maintenance | settings menu, I have the spinnie wheel that something is happening and that's been going on for about 12 hours. Can anyone give me ideas on how to get things so I can see them again? The activity monitor says servermgrd is using between 98 to 100% of the cpu. I kill this process or restart the machine and everything stays the same. Thanks Wayne -- 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] Password // URL in Notification Emails
Every month I get an email from MailMan list's I am currently subscribed to in this email there is a field that shows as follows: List Password // URL st...@mydomain.tld vipidimi https://mail.mydomain.tld/mailman/options/ctia/carlos%40mydomain.tld Can someone tell me if there is a way to disable the plain text email of passwords via the MailMan system? I don't think those passwords are for 'Administrative' login sessions of lists so I really don't understand their purpose. Can anyone tell me what they are used for and how can I disable them from the reminder email? Thanks for any help! -- 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] closing account
Hi, I have for quite a long time ago, closing an account. Account name was nallesresa.se. I still get mail about how to renew your password, the list is not maintained. Can you remove it completely. Thank you in advance Per-Erik -- 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] language
I run centos How to change to swedish in mailman DEFAULT_SERVER_LANGUAGE something -- 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] closing account
On Mon, 1 Feb 2010, Per-Erik Ottosson wrote: Hi, I have for quite a long time ago, closing an account. Account name was nallesresa.se. I still get mail about how to renew your password, the list is not maintained. Can you remove it completely. You need to contact the administrators of the system that is sending you these messages. This list is for discussion by Mailman administrators of how to use Mailman. It is not a support list specific to the server that is sending you the messages nor do we have any access to that site. -- Larry Stone lston...@stonejongleux.com -- 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] Bug: couldn't subscribe to dev list by simplyreplying
Geoff Shang wrote: I just tried again to subscribe to the developers list and discovered that you couldn't confirm your subscription just by replying. The message text implies that the confirmation key should be in the subject, but the confirmation key was in the From address of the confirmation message (see below). Replying simply send me a message telling me that the subject line was being ignored. It seems the confirm code was also ignored. Not sure how it's meant to work but it's the first time I've had to resort to clicking on the URL. What is supposed to happen is you reply; your MUA sends a reply to mailman-developers-confirm+519716b18b6d4ddef39fd87d0e5abdf8c5ced...@python.org This is received and posted to the command queue where it is processed by CommandRunner which parses the token from the To: address and invokes cmd_confirm to do the confirmation. There are two ways this works in general. If the site's VERP_CONFIRMATIONS setting is No (the default) the confirmation is From: listname-requ...@... with Subject: confirm token, and the reply is to the listname-requ...@... address with the confirm command possibly preceded by Re: in the Subject:. This works. If the site's VERP_CONFIRMATIONS setting is Yes as it is at python.org, the confirmation is From: listname-confirm+token@... with Subject: Your confirmation is required to join the listname mailing list, and the reply is to listname-confirm+token@... and this should work too. If you received a reply that your message Subject was ignored, either the To: address didn't match VERP_CONFIRM_REGEXP or the reply wasn't sent to the -confirm address, or the site's MTA doesn't correctly deliver mail addressed to listname-confirm+token@... . I don't think it's the third alternative in this case. If the above doesn't explain what went wrong, post the message you received in reply to your reply. -- 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] language
mattias wrote: I run centos How to change to swedish in mailman DEFAULT_SERVER_LANGUAGE something DEFAULT_SERVER_LANGUAGE = 'sv' -- 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] List Locked Up...kind of
Wayne Cook wrote: Everything still seemed to work fine so I imported about 30,000 emails and stuff got flakey. Your server is probably busy trying to deliver the 30,000 messages. Beyond that, this is an Apple OS X Server Mailman (and/or Postfix?) question and needs to be answered by someone familiar with that. I know there are people on this list who run Mailman from source on Mac OS X. I don't know if there is anyone running the OS X server Mailman who could help. -- 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] Password // URL in Notification Emails
Carlos Williams wrote: Every month I get an email from MailMan list's I am currently subscribed to in this email there is a field that shows as follows: List Password // URL st...@mydomain.tld vipidimi https://mail.mydomain.tld/mailman/options/ctia/carlos%40mydomain.tld Can someone tell me if there is a way to disable the plain text email of passwords via the MailMan system? I don't think those passwords are for 'Administrative' login sessions of lists so I really don't understand their purpose. Can anyone tell me what they are used for and how can I disable them from the reminder email? These are reminders to the list members of their list member passwords. This is the password that a list member can use to authenticate for her own user options page (at the given URL) and for private archive access and for access to the list roster if it is available to list members. The admin can use the list admin password for this, but if the admin is a list member, the list membership has its own password which is not the admin password. The reminder email can be disabled in three ways. The user can disable her individual reminder on her user options page. The list admin can disable all monthly reminders for the list regardless of user settings by setting General Options - send_reminders to No. The site admin can disable monthly reminders for all lists by removing cron/mailpasswds from Mailman's crontab. -- 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
[Mailman-Users] MTA='Manual'
I know that Exim and Mailman play nicely. Is there any problem with my setting the MTA value to manual, doing a genaliases and adding the to my aliases file to handle the aliases? Sounds silly but I would like to see the aliases and not have that be automagically hidden behind the scenes. -- Bob -- 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] MTA='Manual'
Hicks, Robert CTR wrote: I know that Exim and Mailman play nicely. Is there any problem with my setting the MTA value to manual, doing a genaliases and adding the to my aliases file to handle the aliases? Sounds silly but I would like to see the aliases and not have that be automagically hidden behind the scenes. If you wish to remove the Mailman router and transport from your Exin config and use alaises instead, you can. Also see the FAQ at http://wiki.list.org/x/joA9 for ways to automate alias generation for Sendmail which should work for Exim too. -- 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] Private archive nightmare with vhosts
Mark, I fixed the archiving for both private and public archives so no rewriting is involved. private.py does the right thing with my additional patches. I also patched the GetBaseArchiveURL() method to include the virtual host directory in the public archive URL. Finally, I had an issue which almost caused me to give up in disgust. The original patch adds a _GetURLHost() function to Mailman.Utils.py which gets the host name from the invoking URL. This got the name from the SERVER_NAME environment variable which is not the preferred place and is different from the URL host in my test environment. It should use HTTP_HOST. The bottom line for me now is I can take a 2.1.13 base distribution, patch it with the patch at http://www.msapiro.net/mm/2.1.13_vhost.patch and patch that with the vhost_extra_patch.txt patch attached to this post, and I think that list creation and the web interface work. I haven't tested posting because my testbed uses Exim, but I think it should work. Thank you sooo much! Both of these patches worked perfectly and now i have a working, fully virtual mailman installation. This is not something i would've been able to figure out of my own. The only thing it complained about is --with-mail-gid. My previous installation attempts worked fine with --with-mail-gid=list, but this time it complained that it needs --with-mail-gid=nobody, but that was an easy fix. Thanks again, Mark. I really appreciate your help and I am sure that many other users would benefit greatly from these 2 patches. - Igor -- 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] wrapper issue
I changed mailman to use an aliases file (/etc/mail/mailman-aliases) which is owned by root:mailman. I get the following, which I didn't get when the aliases where being managed by Exim itself. Group mismatch error. Mailman expected the mail wrapper script to be executed as group mailman, but the system's mail server executed the mail script as group exim. Try tweaking the mail server to run the script as group mailman, or re-run configure, providing the command line option `--with-mail-gid=exim'. So I have two options. The tweak, and the re-configure. What is the tweak? Or is it better to do the re-configure and if I do that does that wipe out anything in my current system? Alternatively, I can turn the Exim support back on but I was getting this error from one of my groups: Your message did not reach some or all of the intended recipients. Subject: Test message only Sent: 2/1/2010 9:40 AM The following recipient(s) cannot be reached: em...@address on 2/1/2010 9:42 AM The e-mail account does not exist at the organization this message was sent to. Check the e-mail address, or contact the recipient directly to find out the correct address. smtp-host #5.1.1 smtp; The email was changed but the address is valid. Bob -- 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] wrapper issue
Hicks, Robert CTR wrote: I changed mailman to use an aliases file (/etc/mail/mailman-aliases) which is owned by root:mailman. I get the following, which I didn't get when the aliases where being managed by Exim itself. Group mismatch error. Mailman expected the mail wrapper script to be executed as group mailman, but the system's mail server executed the mail script as group exim. Try tweaking the mail server to run the script as group mailman, or re-run configure, providing the command line option `--with-mail-gid=exim'. The difference is you used to deliver mail to Mailman via an Exim router and transport for Mailman. BTW, this was not delivery based on Exim managed aliases. It was programmatic delivery based on the existence of a list. Your Exim Mailman transport definition contained user= and group= directives defining the user and group that Exim should use when invoking the wrapper. In particular, this group was 'mailman'. You now are delivering via aliases. Probably you have a system_aliases router with among other things has a line like pipe_transport = address_pipe which invokes the address_pipe transport for all aliases including Mailman's which deliver to a pipe. So I have two options. The tweak, and the re-configure. What is the tweak? Or is it better to do the re-configure and if I do that does that wipe out anything in my current system? The tweak option is to add a group = mailman directive to either the system_aliases router or the address_pipe transport. The configure option if you installed from source is to run ./configure with the same options as before except adding (or changing) --with-mail-gid=exim and then run make install. If you installed a package, you need to consult your package documentation for the way to change this if it is possible. No. reconfiguring and installing shouldn't affect your current installation. Alternatively, I can turn the Exim support back on but I was getting this error from one of my groups: Going back to your original Exim configuration is IMO the best option. Your message did not reach some or all of the intended recipients. Subject: Test message only Sent:2/1/2010 9:40 AM The following recipient(s) cannot be reached: em...@address on 2/1/2010 9:42 AM The e-mail account does not exist at the organization this message was sent to. Check the e-mail address, or contact the recipient directly to find out the correct address. smtp-host #5.1.1 smtp; The email was changed but the address is valid. Now we're getting somewhere. Was this a message to a list; i.e. is em...@address the address of a Mailman list, or was this a message from Mailman to someone? If this was not a post to a list, Neither the Exim Mailman router and transport nor Mailman aliases have anything to do with it. Is the 'address' domain that of your mailman server? is the 'email' user the name of a Mailman list? Give us some information and we'll help you solve this. -- 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] Bug: couldn't subscribe to dev list by simplyreplying
On Mon, 1 Feb 2010, Mark Sapiro wrote: There are two ways this works in general. If the site's VERP_CONFIRMATIONS setting is No (the default) the confirmation is From: listname-requ...@... with Subject: confirm token, and the reply is to the listname-requ...@... address with the confirm command possibly preceded by Re: in the Subject:. This works. This is what I've seen in the past. If the site's VERP_CONFIRMATIONS setting is Yes as it is at python.org, the confirmation is From: listname-confirm+token@... with Subject: Your confirmation is required to join the listname mailing list, and the reply is to listname-confirm+token@... and this should work too. But it didn't. I don't remember having problems signing up to this list, but that was 4 months ago so I don't really remember. At any rate, the confirmation message text is incorrect for this configuration. If you received a reply that your message Subject was ignored, either Actually, to be precise, it said that it was unprocessed. the To: address didn't match VERP_CONFIRM_REGEXP or the reply wasn't sent to the -confirm address, or the site's MTA doesn't correctly deliver mail addressed to listname-confirm+token@... . I don't think it's the third alternative in this case. Well I still have the message I sent: Date: Mon, 1 Feb 2010 14:30:24 +0200 (IST) From: Geoff Shang ge...@quitelikely.com To: mailman-developers-confirm+519716b18b6d4ddef39fd87d0e5abdf8c5ced...@python. org Subject: Re: Your confirmation is required to join the Mailman-Developers mailing list If the above doesn't explain what went wrong, post the message you received in reply to your reply. Sorry, I don't still have it. But I guess I could generate one. At any rate, it's not a good advertisment. 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] wrapper issue
-Original Message- Your message did not reach some or all of the intended recipients. Subject: Test message only Sent:2/1/2010 9:40 AM The following recipient(s) cannot be reached: em...@address on 2/1/2010 9:42 AM The e-mail account does not exist at the organization this message was sent to. Check the e-mail address, or contact the recipient directly to find out the correct address. smtp-host #5.1.1 smtp; The email was changed but the address is valid. Now we're getting somewhere. Was this a message to a list; i.e. is em...@address the address of a Mailman list, or was this a message from Mailman to someone? This was a test message from me to a list that is in mailman. So it was actually to list-n...@address-domain.mil. Both the list-name and address-domain are correct in the email. I have sent the actual message to you Mark separately to see if that helps at all. If this was not a post to a list, Neither the Exim Mailman router and transport nor Mailman aliases have anything to do with it. Is the 'address' domain that of your mailman server? Yes... can successfully send test mail to other lists. is the 'email' user the name of a Mailman list? I am not sure what you mean by this? I sent it with my personal email account and I am a member of that list with that address and I sent to the list name address. Give us some information and we'll help you solve this. Anything you need. :-) -- 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] wrapper issue
Hicks, Robert CTR wrote: Your message did not reach some or all of the intended recipients. Subject:Test message only Sent: 2/1/2010 9:40 AM The following recipient(s) cannot be reached: em...@address on 2/1/2010 9:42 AM The e-mail account does not exist at the organization this message was sent to. Check the e-mail address, or contact the recipient directly to find out the correct address. smtp-host #5.1.1 smtp; The email was changed but the address is valid. Now we're getting somewhere. Was this a message to a list; i.e. is em...@address the address of a Mailman list, or was this a message from Mailman to someone? This was a test message from me to a list that is in mailman. So it was actually to list-n...@address-domain.mil. Both the list-name and address-domain are correct in the email. I have sent the actual message to you Mark separately to see if that helps at all. The list-name in the message you sent me ends in -admin. This is the problem. Your Mailman router in Exim doesn't work with list names that end with '-admin' or probably any of the other suffixes '-bounces', '-confirm', '-join', '-leave', '-owner', '-request', '-subscribe' or '-unsubscribe'. Does the router definition look like this: mailman_router: driver = accept domains = +mm_domains require_files = MAILMAN_HOME/lists/$local_part/config.pck local_part_suffix_optional local_part_suffix = -bounces : -bounces+* : \ -confirm : -confirm+* : \ -join : -leave : \ -subscribe : -unsubscribe : \ -owner : -request : -admin transport = mailman_transport If so, i think you can just delete the : -admin from the next to last line as this suffix is a deprecated synonym for the -bounces address and isn't actually used in Mailman 2.1.x. That should solve the problem for lists named *-admin, but not the others. I'm not an Exim wizard, but I'll try to come up with a more robust router definition. -- 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] Bug: couldn't subscribe to dev list bysimplyreplying
Geoff Shang wrote: On Mon, 1 Feb 2010, Mark Sapiro wrote: If the site's VERP_CONFIRMATIONS setting is Yes as it is at python.org, the confirmation is From: listname-confirm+token@... with Subject: Your confirmation is required to join the listname mailing list, and the reply is to listname-confirm+token@... and this should work too. But it didn't. I don't remember having problems signing up to this list, but that was 4 months ago so I don't really remember. It worked for me when I tried it just now. At any rate, the confirmation message text is incorrect for this configuration. Granted. We can look at changing that for MM 3. If you received a reply that your message Subject was ignored, either Actually, to be precise, it said that it was unprocessed. Which says that the message was processed by cmd_request and not by cmd_confirm. I don't know how that could have happened if you actually sent it to mailman-developers-confirm+token@python.org, and it didn't happen when I just tried it. the To: address didn't match VERP_CONFIRM_REGEXP or the reply wasn't sent to the -confirm address, or the site's MTA doesn't correctly deliver mail addressed to listname-confirm+token@... . I don't think it's the third alternative in this case. Well I still have the message I sent: Date: Mon, 1 Feb 2010 14:30:24 +0200 (IST) From: Geoff Shang ge...@quitelikely.com To: mailman-developers-confirm+519716b18b6d4ddef39fd87d0e5abdf8c5ced...@python. org Subject: Re: Your confirmation is required to join the Mailman-Developers mailing list If the above doesn't explain what went wrong, post the message you received in reply to your reply. Sorry, I don't still have it. But I guess I could generate one. At any rate, it's not a good advertisment. I just tried it twice with different subscribed addresses, once with a web generated request and once with a request mailed to mailman-developers-subscr...@python.org. In both cases, I received a confirmation email like the one you received and just pressed reply and send and both confirmations were accepted and resulted in a list welcome message -- 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] wrapper issue
On Mon, Feb 01, 2010 at 02:24:26PM -0800, Mark Sapiro wrote: The list-name in the message you sent me ends in -admin. This is the problem. I came up with a work-around for this, once, but on a box I've since decommissioned. Your Mailman router in Exim doesn't work with list names that end with '-admin' or probably any of the other suffixes '-bounces', '-confirm', '-join', '-leave', '-owner', '-request', '-subscribe' or '-unsubscribe'. Indeed, that's the case with a router like that, below Does the router definition look like this: mailman_router: driver = accept domains = +mm_domains require_files = MAILMAN_HOME/lists/$local_part/config.pck local_part_suffix_optional local_part_suffix = -bounces : -bounces+* : \ -confirm : -confirm+* : \ -join : -leave : \ -subscribe : -unsubscribe : \ -owner : -request : -admin transport = mailman_transport From memory, I think 'my' workaround may have involved adding a specific router to handle the suffices, when they appear in the local_part. It may have been something like: local_parts = foo-admin : baa-confim It may be worth testing something along the lines of local_parts = \N^.*-(admin|bounces|confirm|join|leave|owner|request|subscribe|unsubscribe)$\N It might be useful to limit the domains a bit more that +mm_domains, with such a list. (yes, that is untested -- see chapters 8 and 11 of the Exim spec). However I did it, it was most in-elegant, and took advantage of the order of routers matters, in Exim. Having got it working, I remember 'we' decided that that list was surplus to our demands. Hohum. If so, i think you can just delete the : -admin from the next to last line as this suffix is a deprecated synonym for the -bounces address and isn't actually used in Mailman 2.1.x. that's another (nice and easy) way ;) -- ``The power of accurate observation is often called cynicism by those who do not have it.'' (George Bernard Shaw) -- 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] wrapper issue
Mark Sapiro wrote: The list-name in the message you sent me ends in -admin. This is the problem. Your Mailman router in Exim doesn't work with list names that end with '-admin' or probably any of the other suffixes '-bounces', '-confirm', '-join', '-leave', '-owner', '-request', '-subscribe' or '-unsubscribe'. Does the router definition look like this: mailman_router: driver = accept domains = +mm_domains require_files = MAILMAN_HOME/lists/$local_part/config.pck local_part_suffix_optional local_part_suffix = -bounces : -bounces+* : \ -confirm : -confirm+* : \ -join : -leave : \ -subscribe : -unsubscribe : \ -owner : -request : -admin transport = mailman_transport If so, i think you can just delete the : -admin from the next to last line as this suffix is a deprecated synonym for the -bounces address and isn't actually used in Mailman 2.1.x. That should solve the problem for lists named *-admin, but not the others. I'm not an Exim wizard, but I'll try to come up with a more robust router definition. The following is not too elegant, but you can just add a second router so you have two as follows (order is important): mailman_router: driver = accept domains = +mm_domains require_files = MAILMAN_HOME/lists/$local_part/config.pck local_part_suffix_optional local_part_suffix = -bounces : -bounces+* : \ -confirm : -confirm+* : \ -join : -leave : \ -subscribe : -unsubscribe : \ -owner : -request : -admin transport = mailman_transport mailman__backup_router: driver = accept domains = +mm_domains require_files = MAILMAN_HOME/lists/$local_part/config.pck transport = mailman_transport The first router will be invoked for addresses like 'list', 'list-admin', 'list-bounces', etc where 'list' is a valid list name. Should there be a list with a name like 'xxx-admin', as long as there also is not a list named 'xxx', the first router will fail to match on list posts and the second router will match. Addresses like 'xxx-admin-bounces' etc. (even 'xxx-admin-admin') will match the first router. The only restriction is you can't have two lists, one named 'xxx' and another named 'xxx-admin' or 'xxx-bounces', etc., but that's a problem with other delivery methods too. -- 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
