Re: [Mailman-Users] Migrating a list to a new email address
On 05/15/2015 06:51 PM, Bill Christensen wrote: > > On 5/15/15 12:21 AM, Mark Sapiro wrote: >> Privacy options... -> Subscription rules -> subscribe_policy st to >> Require approval and then discard all requests. > when you say "discard all requests", is there a way to do that > automatically? Without email notices to the owner address? Not really. If you set General Options -> admin_immed_notify to No, there will be only one summary notice per day, and not the one per request and you could modify Mailman's crontab to not run checkdbs or run it less frequently than daily, but the requests will still be there. There is no automatic discard, but it wouldn't be hard to create a script that discards all outstanding subscription requests for a list (or all lists) and run it daily just before checkdbs runs so checkdbs would have nothing to report. In fact, if you wanted to be really crude and ignore all requests for a list you could just remove the lists/listname/request.pck file. This would effectively discard all requests. You have to be carful because you don't want to do this if there are held messages because then the message files would be orphaned, but something like (adjust list, prefix and var_prefix to suit #! /bin/sh list=LISTNAME prefix=/usr/lib/mailman var_prefix=/var/lib/mailman ls $var_prefix/data/heldmsg-$list-* | xargs $prefix/bin/discard rm $var_prefix/lists/$list/request.pck would discard all held messages and then discard the remaining subscribe (and unsubscribe if unsubscribe_policy is Yes) requests. You could add this to the crontab to run just before checkdbs, or add $prefix/cron/checkdbs to the end of it and run it instead of checkdbs. That all assumes you might have other lists you want to treat normally. There are other things you can do as well, but, looking at your original post, I see I didn't fully register the situation. If your Mailman is at least 2.1.16, all you need to do is set SUBSCRIBE_FORM_SECRET = 'Some string unique to your site" in mm_cfg.py, and that attack will no longer work. Doing that requires that for the subscribe to be successful, the URL must contain a token which was generated by the listinfo subscribe form at least 5 seconds and no more than an hour before submission. The token contains a hash of the secret, the requesting IP, the list name and the time which means if a bot is going to subscribe, it has to first retrieve the listinfo page to get the token and then wait 5 seconds (which can be configured to be longer by setting SUBSCRIBE_FORM_MIN_TIME in mm_cfg.py) and then submit the request with the token. I don't think the bots have figured it out yet. -- Mark Sapiro The 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
Re: [Mailman-Users] Migrating a list to a new email address
Excellent. I didn't know about the clone_list script. On 5/15/15 12:21 AM, Mark Sapiro wrote: Privacy options... -> Subscription rules -> subscribe_policy st to Require approval and then discard all requests. when you say "discard all requests", is there a way to do that automatically? Without email notices to the owner address? -- 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] Importing from 2.1.12-18.el6 to 2.1.15-17.el7
On 05/15/2015 12:28 PM, Dean Collins wrote: > > Subscribers include m...@mydomain.com (the same domain the list is on) and > various addresses from other domains/servers (a couple of servers I run, > plus Gmail and AT&T.) > > Mail sent to myl...@mydomain.com from any subscriber gets archived -- and > distributed to m...@mydomain.com. But none of the other subscribers receive > the list mail. In order to be sure about anything, I'd need to see some logs like Mailman's smtp-failure log and the MTA logs, except I don't know anything about qmail. However, based on past experience I can say the following. 1) Mailman is delivering to the local MTA (qmail) and the mail is being delivered to local addresses but not being sent to remote domains. 2) Other locally generated mail is being sent to remote domains. When this happens it is probably an IPv4 vs. IPv6 issue. Here's one scenario. It may not be exactly this in your case, but you should be able to translate. The MTA has an idea of what addresses constitute the local network and will relay mail from those addresses to the outside. This includes say the IPv4 local host, something like 127.0.0.1, but not the IPv6 local host ::1. Mailman, by default, delivers to 'localhost'. 'localhost' in turn is defined as the IPv6 ::1 address. Thus Mailman's mail comes to the MTA from ::1 which is not in the MTA's notion of the local network, so the MTA refuses to relay the mail. This can be fixed in multiple ways. You can add the IPv6 local host to the MTA's local network. You can change /etc/hosts to associate 127.0.0.1 rather than ::1 with 'localhost'. You can set SMTPHOST in mm_cfg.py to something that will work. E.g., SMTPHOST = '127.0.0.1' Note that since I haven't seen your logs, the above scenario may be off. Perhaps it would be that Mailman is sending via the IPv4 loopback and qmail wants IPv6, but the idea is the same. -- Mark Sapiro The 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
Re: [Mailman-Users] Importing from 2.1.12-18.el6 to 2.1.15-17.el7
On 5/15/2015 3:28 PM, Dean Collins wrote: > This is Mailman 2.1.15-17, qmail, CentOS 7. > > I've got a new server and set up a test list, say, myl...@mydomain.com. > > Subscribers include m...@mydomain.com (the same domain the list is on) and > various addresses from other domains/servers (a couple of servers I run, > plus Gmail and AT&T.) > > Mail sent to myl...@mydomain.com from any subscriber gets archived -- and > distributed to m...@mydomain.com. But none of the other subscribers receive > the list mail. > > Non-list, regular mail works fine. Using m...@mydomain.com I can send to > anyone (and they receive it) and receive from anyone. > > I know less about mail than just about anything else in the world, so any > suggestions as to what might be wrong would be appreciated. Thanks! > > Dean > > What outgoing SMTP server are you trying to use? If smtp.att.yahoo.com your problem is in the postfix config, not mailman. ATT is so heavily restricted it is nearly impossible to set up. I use MailJet as my outgoing server for mailman instead. signature.asc Description: OpenPGP digital signature -- 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] Importing from 2.1.12-18.el6 to 2.1.15-17.el7
This is Mailman 2.1.15-17, qmail, CentOS 7. I've got a new server and set up a test list, say, myl...@mydomain.com. Subscribers include m...@mydomain.com (the same domain the list is on) and various addresses from other domains/servers (a couple of servers I run, plus Gmail and AT&T.) Mail sent to myl...@mydomain.com from any subscriber gets archived -- and distributed to m...@mydomain.com. But none of the other subscribers receive the list mail. Non-list, regular mail works fine. Using m...@mydomain.com I can send to anyone (and they receive it) and receive from anyone. I know less about mail than just about anything else in the world, so any suggestions as to what might be wrong would be appreciated. Thanks! Dean -- 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] Importing from 2.1.12-18.el6 to 2.1.15-17.el7
On 05/15/2015 06:53 AM, Dean Collins wrote: > Hello, everyone. Will "config_list -I" work to import settings from version > 2.1.12-18 to 2.1.15-17? Yes it will, but if you're actually moving a list as opposed to just using its settings, you can just move the lists/LISTNAME/config.pck file and that works too as long as it's an upgrade (from older Mailman to newer). Mailman detects that the config.pck is old and upgrades it automatically. Actually, some downgrades will work too, but it's trickier and depends on the exact from and to versions. -- Mark Sapiro The 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
Re: [Mailman-Users] Where are the wrong email adresses ?
On 05/14/2015 05:29 AM, Regis wrote: > > Please could you tell me where can i see and manage these wrong email > adresses ? Bounces from invalid addresses are returned to a special LISTNAME-bounces address where they are either ignored or automatically processed by Mailman according to settings in the Bounce processing admin UI. If Bounce processing -> bounce_processing is set to Yes for the list, the bounces will be processed automatically according to the remaining settings. Each bounce is logged in Mailman's bounce log and you can see the addresses there, but not the actual bounce DSN. If bounce_notify_owner_on_disable is Yes, the notice to the list owner will contain a copy of the DSN that caused the disable (i.e., increased the score to bounce_score_threshold). If you have Mailman 2.1.19 or newer, you can also set bounce_notify_owner_on_bounce_increment to Yes to receive a nitice with a copy of the DSN that incremented the score, i.e., the first bounce of the day. -- Mark Sapiro The 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
[Mailman-Users] Where are the wrong email adresses ?
Hello everybody, I have just sent my first mailing with mailman. I kwow that a lot of email adresses are wrong but, in the admin panel, i can't see them neither in the Membership Management list nor in the Bounce Processing... Please could you tell me where can i see and manage these wrong email adresses ? Thanks a lot ! -- 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] Importing from 2.1.12-18.el6 to 2.1.15-17.el7
Hello, everyone. Will "config_list -I" work to import settings from version 2.1.12-18 to 2.1.15-17? Thanks! Dean -- 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
