Mailman 3 July 2015 - Mailman-Users

Mapping member options from Mailman 2 to 3
by Daniel Miller 13 Jul '15

13 Jul '15

Hello, I'm trying to migrate an existing list from Mailman 2 to Mailman 3, and I wanted to know more about user preferences and member options. Here is the mapping I have so far: Mailman 2: Mailman 3 realname: {address, user}.display_name password: user.password language: preferences.preferred_language delivery.status: preferences.delivery_status delivery.delivery: prefererences.delivery_mode noremind: ??? nodupes: ~preferences.receive_list_copy notmetoo: ~preferences.receive_own_postings hide: preferences.hide_address ack: preferences.acknowledge_posts mod: ??? nomail: ??? nmtopics: ??? topics: ??? Do the missing (???) options have any corresponding attribute in Mailman 3, and are these accessible through mailman.client? I am particularly interested in the moderation flag, but any other information you may have would be useful. I am not entirely clear on whether an Address or Membership can exist without an associated User, and if I copy our existing roster as address-only memberships whether our subscribers will be able to update their preferences. Thanks! Dan

3 2

best configuration for usenet group relay
by Danil Smirnov 12 Jul '15

12 Jul '15

Hi all! I need an advice from people who have experience in Usenet group gateway into the Mailman 2 mailing list (when this is a main purpose of the mailling list). AFAIK, there are no limitation on senders email in the Usenet. One can put there any crap he wants. But I doubt that it's appropriate for modern mail servers/services. So we probably need to configure list as anonymous to prevent using this fake emails in messages, but it would be great to somehow keep users' identification strings. What do you suggest? Danil

2 1

Wrong perms?(fwd) Cron <mailman@patronus> /usr/lib/mailman/cron/nightly_gzip
by Steve Matzura 11 Jul '15

11 Jul '15

After solving my cron confusions, I get these messages daily: Subject: Cron <mailman@{mynode}> /usr/lib/mailman/cron/checkdbs ... IOError: [Errno 13] Permission denied: '/var/lock/mailman/mailman.lock.{mynode}.{mydomain.com}.7552.0' Subject: Cron <mailman@{mynode}> /usr/lib/mailman/cron/disabled ... IOError: [Errno 13] Permission denied: '/var/lock/mailman/mailman.lock.{mynode}.{mydomain.com}.7837.0' When I looked for this file, it wasn't even there. Subject: Cron <mailman@{mynode}> /usr/lib/mailman/cron/senddigests ... IOError: [Errno 13] Permission denied: '/var/lib/mailman/lists/mailman/config.pck' This file is owned by root and is in the mailman group. check_perms reports no problems found.

2 3

MM3/HyperKitty and importing Malman2 lists
by Isaac Bennetch 10 Jul '15

10 Jul '15

Hi, Thanks for the good work bringing us Mailman3. I'm doing a new install, which is intended to import data from a different server which had been running Mailman2. I've used the mailman-bundler to install and have a few questions. At this point, I'm still using the SQLite backend but have hopes of using MySQL (I know MySQL better than PostgreSQL, and the manual seems to imply that sticking with SQLite may not be ideal). I'm currently attempting to import the old mbox into Hyperkitty[0], which I think I've adapted in to > ./bin/django-admin hyperkitty-import --pythonpath eggs/HyperKitty-1.0.1-py2.7.egg/hyperkitty/ -l testing(a)example.org /home/mailman/old-list.mbox Which doesn't say much (full output below[1]), but didn't fully work. Out of approximately 18300 messages, only six are visible to me through the "Mailing-List Archives" web page, and one of them has a very strange date. It is the second message of the mbox, from 9 Apr 2001, but appears in the web page with approximately the date/time of the import: 9 July 2015 7:27 p.m. Additionally, the remaining five messages are all the most recent -- with the exception of the most recent message not appearing at all. Additionally, if I use the Search box to search for a word that I know appears in (at least) one message, I get no results found. I feel I'm missing something here, any idea what it could be? Furthermore, I haven't found any substantial documentation on importing a subscriber list from Mailman2; is there anything that will allow me to transfer subscribers, their digest preference, and so on without requiring them all to resubscribe manually? Thanks in advance, ~isaac 0 - https://hyperkitty.readthedocs.org/en/latest/development.html 1 - > Importing from mbox file /home/mailman/old-list.mbox to testing(a)example.org > /No 'Message-Id' header in email from None about None > -No 'Message-Id' header in email from None about None > \No 'Message-Id' header in email from None about None > |No 'Message-Id' header in email from None about None > /No 'Message-Id' header in email from None about None > -No 'Message-Id' header in email from None about None > \No 'Message-Id' header in email from None about None > |No 'Message-Id' header in email from None about None > /No 'Message-Id' header in email from None about None > -No 'Message-Id' header in email from None about None > \No 'Message-Id' header in email from None about None > |No 'Message-Id' header in email from None about None > Computing thread structure > Synchronizing properties with Mailman > /usr/local/src/mailman-bundler/eggs/Django-1.7.8-py2.7.egg/django/db/models/fields/__init__.py:1282: RuntimeWarning: DateTimeField MailingList.created_at received a naive datetime (2015-07-04 14:30:22.803087) while time zone support is active. > RuntimeWarning) > > WARNING /usr/local/src/mailman-bundler/eggs/Django-1.7.8-py2.7.egg/django/db/models/fields/__init__.py:1282: RuntimeWarning: DateTimeField MailingList.created_at received a naive datetime (2015-07-04 14:30:22.803087) while time zone support is active. > RuntimeWarning) > > The full-text search index will be updated every minute. Run the 'manage.py runjob update_index' command to update it now.

2 1

Re: [Mailman-Users] Header filtering regex issue
by Mark Sapiro 09 Jul '15

09 Jul '15

On 07/07/2015 12:41 PM, Sibi John wrote: > None whatsoever !! which is what boggles my mind ! In reply to: > -----Original Message----- > From: Mailman-Users On Behalf Of Mark Sapiro > Sent: July 07, 2015 2:40 PM > To: mailman-users(a)python.org > Subject: Re: [Mailman-Users] Header filtering regex issue > > On 07/07/2015 04:43 AM, Sibi John wrote: >> >> In my spam filter rules, this is the regex that I have and it matches perfectly. >> >> From: .+(a)(?!(xxx|yyy)\.com).+ >> >> >> For some reason, it discards all email and I cannot seem to figure out what I am doing wrong. Any suggestions ? > > > The regexp should work. It might match some desired addresses like user(a)sub.xxx.com and not match some undesired ones like user(a)xxx.com.au, but it should work for the obvious cases. > > Do you have any other header_filter_rules? If so, what are they? Actually, there is a problem with your regexp. header_filter_rules regexps are searched (re.search, not re.match) in multiline mode case insensitively. This your regexp will match 'from:' in other places in the headers. Try ^From: .+(a)(?!(xxx|yyy)\.com).+ to match only a true 'From: header. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 1

Learning to use withlist
by Steve Matzura 08 Jul '15

08 Jul '15

What's the best section of the standard documentation or the wiki to consult in order to learn how to correctly use withlist?

6 9

Re: [Mailman-Users] merging 2 mailing lists
by Laura Creighton 07 Jul '15

07 Jul '15

In a message of Tue, 07 Jul 2015 10:55:52 -0400, "Bill Cole" writes: >> ??? There's been major discussion about this on both lists, and >> everybody thinks it's a wonderful idea. Not a single objection. > >I am sorry. By way of explanation, it was late and I skimmed with tired >eyes, missing the key point that these are traditional discussion lists >rather than unidirectional broadcast lists. Well, actually, I didn't make it clear. The real situation is that the recipe-list ( 2 of them) each have a reply-to: setting for recipe-discussion (to translate from the Swedish to the English). So it's on the discuss side that all the agreement happened. At any rate, the movement to a new list name went well -- and over this evening the merging of archiving will happen. Thank you everybody. tack så mycket! Laura

1 0

Header filtering regex issue
by Sibi John 07 Jul '15

07 Jul '15

Guys, I am not sure what I am doing wrong here with the header filter especially since I know this used to work in the past. For one of my mailing lists, I would like to automatically discard any emails that do not from the two domains xxx and yyy listed below. The regex matches any other email address. In my spam filter rules, this is the regex that I have and it matches perfectly. From: .+(a)(?!(xxx|yyy)\.com)<mailto:.+@(?!(xxx|yyy)\.com)>.+ For some reason, it discards all email and I cannot seem to figure out what I am doing wrong. Any suggestions ?

2 1

Re: [Mailman-Users] merging 2 mailing lists
by Laura Creighton 07 Jul '15

07 Jul '15

In a message of Tue, 07 Jul 2015 00:33:00 -0400, "Bill Cole" writes: >On 6 Jul 2015, at 9:26, Laura Creighton wrote: > >> 2 somebodies I know want to merge their mailing lists. > >Have they bothered asking each and every subscriber and received an >affirmative reply? No? Imagine my shock... > >The correct answer to this is "No, you can't. You don't have subscriber >permission to do so." > >Unless you think having all of the IPs of the list service provider >*correctly* blacklisted in many places is a good thing. ??? There's been major discussion about this on both lists, and everybody thinks it's a wonderful idea. Not a single objection. And for the life of me, I cannot imagine why there would be. Recipes developed by members of the Stockholm region support group for families with kidney disease are perfectly edible by Värmland families in the same position, and vice versa. Why on earth shouldn't they be able to combine their lists if they want to? Laura

2 1

Re: [Mailman-Users] Nightly Messages Show Problems
by Steve Matzura 07 Jul '15

07 Jul '15

This should have gone to the list instead of where it went. On Sat, 04 Jul 2015 07:45:07 -0700, Mark Shapiro <mark(a)msapiro.net> wrote: >These occur because you have installed a crontab which has been >formatted as a system crontab and intended to be installed in a place >like /etc/cron.d/mailman as a user contab somewhere in /var/spool/cron. Interesting. I followed the directions at http://www.gnu.org/software/mailman/mailman-install/node41.html which say: If your version of crontab supports the -u option, you must be root to do this next step. Add $prefix/cron/crontab.in as a crontab entry by executing these commands: % cd $prefix/cron % crontab -u mailman crontab.in >System crontabs have an extra field between the days/times and the >command which is the user to run as. In this case, that user (mailman) >is interpreted as part of the command because the crontab is installed >for a user. Should I remove the mailman ones and install it as root instead? >The four are all permissions issues. Since check_perms thinks the >permissions are OK, the issue could be that the user as which the crons >are running is not in the 'mailman' group, or it could be a SELinux or >other policy manager issue. mailman is not a group in root's passwd record. Sounds like the crontab.in needs editing to remove the mailman username from it? >It seems there are at least two mailman crontabs. One is a user crontab >in /var/spool/cron/mailman (or maybe /var/spool/cron/crontabs/mailman or >??) that is not formatted as a user crontab and is responsible for the >/bin/sh: mailman: command not found messages. The other is probably in >/etc/cron.d/mailman and is the one giving the permission exceptions. > >What are the contents of these crontabs? You only want one of these. >Which may be important if there are SELinux issues, but otherwise, it >doesn't matter as long as the one is correct. The two in /etc/cron.d and /var/spool/cron are identical. Here's the contents with the comment lines removed: MAILTO=sm(a)noisynotes.com 0 8 * * * mailman /usr/lib/mailman/cron/checkdbs 0 9 * * * mailman /usr/lib/mailman/cron/disabled 0 12 * * * mailman /usr/lib/mailman/cron/senddigests 0 5 1 * * mailman /usr/lib/mailman/cron/mailpasswds 27 3 * * * mailman /usr/lib/mailman/cron/nightly_gzip 30 4 * * * mailman /usr/lib/mailman/cron/cull_bad_shunt

2 7