Re: [Mailman-Users] Trying to get mail working
On Wed, 13 May 2015 23:19:45 +0900, Steve Turnbull wrote: Dovecot and Mailman should be mostly independent of each other, while both depend crucially on Postfix. The first thing to do is to find the log files for each application, and test that mail works for all combinations of inside and outside the system (and often outside has to be divided into your domain and the rest of the Internet), to and from. If Dovecot isn't working, you still should be able to see mail flowing in the Postfix logs, and possibly learn something about its status using the mailq tool. Next work on being able to read and perhaps submit mail via Dovecot. Finally, do the Mailman configuration. Thanks. That sounds like an excellent starting point. Testing Dovecot or Mailman in the absence of a working Postfix is going to be hard for you, I guess. It's not impossible, but it requires some knowledge of internals of each program, and a fair amount of confidence with Unix tools like pipes and netcat. Much easier to learn to read Postfix's logs to determine when the problem is with one of the (non- ;-) cooperating applications, and when it's Postfix. Tools are not a problem, but program internals? Nah, not I, said the sys admin (LOL). At least I know now what the focal point is of the three. It would help if you describe the symptoms, although perhaps the best thing we can do is direct you to a Postfix or Dovecot channel. No symptoms to report, as I've not begun testing in a serious and methodical way ... until now, because I was clueless as to where to begin. I'll work with the above and reply with more details as they are revealed if things don't work. -- Mailman-Users mailing list Mailman-Users@python.org https://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: https://mail.python.org/mailman/options/mailman-users/archive%40jab.org
[Mailman-Users] Migrating a list to a new email address
Hi all, I have a long running list with thousands of subscribers that needs to move to a new set of email addresses. The existing list is announce-only, so doesn't get a whole lot of traffic - typically at most a few outgoing emails a year. But some time back a bot started sending spam registrations via hits to the web server in the form domain name /mailman/subscribe.cgi/bwbnewsletter?email=bogus_registrant@somedomain.tldmailto:ruanwe...@hotmail.comfullname=pw=123456789pw-conf=123456789language=endigest=0email-button=Subscribe. I long ago routed real users to an alternative signup, but the spam keeps coming, unrelenting, and are now anywhere between 1k and 10k per day. I'm thinking that the best way to deal with this is to move everything, including the archives, to a newly created list on the same domain name. The alternative signup method i've set up works, so if i set the new list to Advertise this list... = NO in Privacy, I'm hoping the spammers won't figure out that the new mailman list exists. I could also set it up as a closed list if that's possible since the new registrations will be entered manually in bulk, though I don't see any settings which disallow all subscriptions. So I'd like confirmation on how to move a list to a new address under the same domain. I figure I need to: 1) take a backup copy of the oldlistname.mbox file in /archives/private 2) take a copy of the current subscriber list (already done using the list_members command) 3) create the new list, aliases, etc and associated email addresses 4) remove /archives/private/newlistname.mbox 5) rename oldlistname.mbox to newlistname.mbox 5b) do I need to replace all instances of oldlistname with newlistname everywhere they occur in the .mbox file? Would doing so cause any problems? 6) rebuild the archives 7) test the new list 8) bulk subscribe the subscriber list to newlistname 9) delete the old list Did I miss anything? Thanks in advance. -- Mailman-Users mailing list Mailman-Users@python.org https://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: https://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Migrating a list to a new email address
On 05/14/2015 09:32 PM, Bill Christensen wrote: I'm thinking that the best way to deal with this is to move everything, including the archives, to a newly created list on the same domain name. The alternative signup method i've set up works, so if i set the new list to Advertise this list... = NO in Privacy, I'm hoping the spammers won't figure out that the new mailman list exists. I could also set it up as a closed list if that's possible since the new registrations will be entered manually in bulk, though I don't see any settings which disallow all subscriptions. Privacy options... - Subscription rules - subscribe_policy st to Require approval and then discard all requests. So I'd like confirmation on how to move a list to a new address under the same domain. I figure I need to: 1) take a backup copy of the oldlistname.mbox file in /archives/private 2) take a copy of the current subscriber list (already done using the list_members command) 3) create the new list, aliases, etc and associated email addresses 4) remove /archives/private/newlistname.mbox 5) rename oldlistname.mbox to newlistname.mbox 5b) do I need to replace all instances of oldlistname with newlistname everywhere they occur in the .mbox file? Would doing so cause any problems? 5b) No. You don't need to edit the old .mbox file in any way. Of course, if there are say URLs in the bodies of messages (other than scrubbed attachment links) that point to the old list, you may want to fix those. You can do all the above (1-5) in one step with the script at http://www.msapiro.net/scripts/clone_list. See the FAQ at http://wiki.list.org/x/4030617 which mentions this and a few other methods. 6) rebuild the archives See the note in the second half of that FAQ about scrub_nondigest. Similar info is in the script's -h/--help output. The archives will be moved with the -a/--archives option to the script. The reason you may want to rebuild the archives are the more information about this list links still point to the old list name and likewise, links to scrubbed attachments if any. 7) test the new list 8) bulk subscribe the subscriber list to newlistname Already done with the -m/--members option to the list. 9) delete the old list Did I miss anything? If you have and pending requests, a digest mbox or list specific templates, you may want to move those, but the -e/--extra_files option to the script will do that. It also takes care of alias generation for the new list if you use Mailman/Postfix integration. Otherwise, you may need to update aliases manually. In short, the whole process is 1) Install the clone_list script in mailman's bin/ directory. 2) bin/clone_list -m -a -e old_list_name new_list_name (there are also options to change subject_prefix, list owner and list password, but they default to keeping current values.) 2a) maybe bin/arch --wipe new_list_name (or maybe 3a) 3) Test 4) bin/rmlist old_list_name -- 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 https://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: https://mail.python.org/mailman/options/mailman-users/archive%40jab.org
