Mailman 3 July 2016 - Mailman-Users

Mailman 2 + Postfix + virtual domains + lists subdomain
by Jérôme July 11, 2016

July 11, 2016

Hi. I'm trying to configure mailman/postfix with virtual domains. Both postfix and mailman are installed using Debian packages. Postfix works with virtual domains domain1.tld and domain2.tld. I would like Mailman to serve mailing lists on lists.domain1.tld and lists.domain2.tld. I've been reading these, of course: http://www.gnu.org/software/mailman/mailman-install/postfix-integration.html http://www.gnu.org/software/mailman/mailman-install/postfix-virtual.html AFAIU, postfix_to_mailman.py is not needed and not recommended, so I'd avoid it if possible: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=718284 It appears in the configuration, but I tried both with and without. Here are (hopefully comprehensive) config files excerpts : ------------------------------------------------------------ mailman mm_cfg.py ------------------------------------------------------------ DEFAULT_EMAIL_HOST = 'lists.domain1.tld' DEFAULT_URL_HOST = 'domain1.tld' add_virtualhost(DEFAULT_URL_HOST, DEFAULT_EMAIL_HOST) add_virtualhost ('domain2.tld', 'lists.domain2.tld') MTA = 'Postfix' POSTFIX_STYLE_VIRTUAL_DOMAINS = [ 'lists.domain1.tld', 'lists.domain2.tld', ] ------------------------------------------------------------ ------------------------------------------------------------ postfix main.cf ------------------------------------------------------------ myorigin = domain1.tld mydomain = domain1.tld myhostname = domain1.tld # System users alias_maps = hash:/etc/aliases alias_database = hash:/etc/aliases mydestination = localhost relayhost = mynetworks = 127.0.0.0/8 [::ffff:127.0.0.0]/104 [::1]/128 mailbox_size_limit = 0 recipient_delimiter = + inet_interfaces = all # Virtual users virtual_mailbox_base = /var/mail/vmail/ virtual_mailbox_domains = proxy:pgsql:/etc/postfix/virtual-domains.cf virtual_mailbox_maps = proxy:pgsql:/etc/postfix/virtual-mailbox-maps.cf virtual_uid_maps = static:113 virtual_gid_maps = static:121 virtual_alias_maps = proxy:pgsql:/etc/postfix/virtual-alias-maps.cf, hash:/var/lib/mailman/data/virtual-mailman # Dovecot dovecot_destination_recipient_limit = 1 virtual_transport = dovecot # Mailman # cf. /etc/mailman/postfix-to-mailman.py # relay_domains = lists.domain1.tld, lists.domain2.tld # relay_recipient_maps = hash:/var/lib/mailman/data/virtual-mailman # transport_maps = hash:/etc/postfix/transport mailman_destination_recipient_limit = 1 ------------------------------------------------------------ postfix master.cf ------------------------------------------------------------ mailman unix - n n - - pipe flags=FR user=list argv=/usr/lib/mailman/bin/postfix-to-mailman.py ${nexthop} ${user} ------------------------------------------------------------ ------------------------------------------------------------ postfix transport ------------------------------------------------------------ lists.domain1.tld mailman: lists.domain2.tld mailman: ------------------------------------------------------------ ------------------------------------------------------------ DNS for domain1 ------------------------------------------------------------ @ 3600 IN A xxx.xxx.xxx.xxx lists 3600 IN A xxx.xxx.xxx.xxx @ 3600 IN MX 10 domain1.tld. @ 3600 IN TXT "v=spf1 a mx -all" ------------------------------------------------------------ I created a test list 'test(a)lists.domain1.tld' using mailman's bin/newlist. ------------------------------------------------------------ mailman aliases ------------------------------------------------------------ mailman: "|/var/lib/mailman/mail/mailman post mailman" mailman-admin: "|/var/lib/mailman/mail/mailman admin mailman" mailman-bounces: "|/var/lib/mailman/mail/mailman bounces mailman" mailman-confirm: "|/var/lib/mailman/mail/mailman confirm mailman" mailman-join: "|/var/lib/mailman/mail/mailman join mailman" mailman-leave: "|/var/lib/mailman/mail/mailman leave mailman" mailman-owner: "|/var/lib/mailman/mail/mailman owner mailman" mailman-request: "|/var/lib/mailman/mail/mailman request mailman" mailman-subscribe: "|/var/lib/mailman/mail/mailman subscribe mailman" mailman-unsubscribe: "|/var/lib/mailman/mail/mailman unsubscribe mailman" test: "|/var/lib/mailman/mail/mailman post test" test-admin: "|/var/lib/mailman/mail/mailman admin test" test-bounces: "|/var/lib/mailman/mail/mailman bounces test" test-confirm: "|/var/lib/mailman/mail/mailman confirm test" test-join: "|/var/lib/mailman/mail/mailman join test" test-leave: "|/var/lib/mailman/mail/mailman leave test" test-owner: "|/var/lib/mailman/mail/mailman owner test" test-request: "|/var/lib/mailman/mail/mailman request test" test-subscribe: "|/var/lib/mailman/mail/mailman subscribe test" test-unsubscribe: "|/var/lib/mailman/mail/mailman unsubscribe test" ------------------------------------------------------------ ------------------------------------------------------------ mailman virtual-mailman ------------------------------------------------------------ mailman(a)lists.domain1.tld mailman mailman-admin(a)lists.domain1.tld mailman-admin mailman-bounces(a)lists.domain1.tld mailman-bounces mailman-confirm(a)lists.domain1.tld mailman-confirm mailman-join(a)lists.domain1.tld mailman-join mailman-leave(a)lists.domain1.tld mailman-leave mailman-owner(a)lists.domain1.tld mailman-owner mailman-request(a)lists.domain1.tld mailman-request mailman-subscribe(a)lists.domain1.tld mailman-subscribe mailman-unsubscribe(a)lists.domain1.tld mailman-unsubscribe test(a)lists.domain1.tld test test-admin(a)lists.domain1.tld test-admin test-bounces(a)lists.domain1.tld test-bounces test-confirm(a)lists.domain1.tld test-confirm test-join(a)lists.domain1.tld test-join test-leave(a)lists.domain1.tld test-leave test-owner(a)lists.domain1.tld test-owner test-request(a)lists.domain1.tld test-request test-subscribe(a)lists.domain1.tld test-subscribe test-unsubscribe(a)lists.domain1.tld test-unsubscribe ------------------------------------------------------------ Test 1: Connecting to the server's webmail and sending a mail to the test list. I get this error: <test(a)domain1.tld> (expanded from <test(a)lists.domain1.tld>): user unknown I read the FAQ (http://wiki.list.org/x/uYA9) and double checked I do have a A record for lists.domain1.tld. Test 2: Sending a mail to the test list using my mail client, the SMTP being the server itself (postfix/dovecot). The message does not even leave the mail client. I get this error: 554 5.7.1 <test(a)lists.domain1.tld>: Relay access denied Since both methods use the same SMTP, I wonder why I get this difference between both tests. I tried both commenting / uncommenting the 'transport_maps' line transport_maps = hash:/etc/postfix/transport in main.cf, which, IIUC, should activate/deactivate postfix_to_mailman.py, and it didn't make any difference. I'd appreciate any hint. I obviously lack postfix expertise and my config is likely to contain blatant issues. Unfortunately, I didn't find any step-by-step guide. The tutorials I found either have virtual domains but no subdomain, or a dedicated 'lists' subdomain but for only one domain, no multiple virtuals. And most of them use postfix_to_mailman.py which I understand should be avoided. (Also, please redirect me if this is not the right place to ask.) Thanks. -- Jérôme

2 6

command line tool to list ban_list, discard_these_nonmembers, accept_these_nonmembers, etc
by Matthew Needham July 11, 2016

July 11, 2016

Is there a succinct way to list "auxiliary" addresses that are configured in a list? By "auxiliary" I'm referring to addresses other than member, owner, or moderator, since those are easy to find with list_owners and find_members. I'm trying to practice better list hygiene, and remove all relevant address when someone leaves the organization. The best way I've currently found is use a foreach loop to grab each list's config.pck and run dumpdb against it. I then filter out the uninteresting addresses and manually scan the results for relevant addresses. I can't simply grep the output for relevant addresses, because a subscriber john.doe(a)domain.com may be allowed (or disallowed) to post from jd123(a)free-email.com. I don't mind the manual scanning, but parsing the output if dumped is time consuming. I'm guessing there's a way to grep for the relevant settings and all relevant following lines, but my regex skills have not been up to the task. I took a look at https://www.msapiro.net/scripts/non_members, but it appears to require that I know the addresses in advance, and not allow me to discover the relevant addresses. It also doesn't support ban_list, which is admittedly a rare occurrence for me, but I don't know if there are other unincluded settings I should be considering. I suppose this raises a question of other possible list hygiene best-practices. Besides removing subscriptions and removing/reassigning administrator or moderator responsibilities, when else should I be doing to clean up when someone leaves? Thanks! -- Matthew Needham mneedham(a)hdfgroup.org 217-531-6110 The HDF Group 1800 South Oak Street, Suite 203 Champaign, IL 61820

2 4

mailman and yahoo
by Manuel Goepfert July 9, 2016

July 9, 2016

Hi All, I’m facing since a few weeks if not even more some issue when a registered user using yahoo.com email address sends an email to one of the list that mailman manages. As the list is configured to send emails on behalf of the user to the members of the list, this triggers some anti spam mecanism that puts the message in the spam folders of the different recipients even worth, the email is rejected by some mail servers. The consequence is that the email addresses get at the end removed from the list because of bounces as the origin email address @yahoo.com is not legitimately sent from a yahoo email server. Looking at some documentation I found out that this was a known problem and that it was addressed in on e of the mailman version. So I upgraded to 2.1.18 that included that fix but I?m still facing this problem. Do you guys have the same issue and if yes are you able to mitigate it in any way ? I do have spf,dkim and dmark in place for the domain used to send emails. Thanks for your feedback. Kind regards, Manu

2 2

Re: [Mailman-Users] Message discarded without reason logged in vette
by Mark Sapiro July 8, 2016

July 8, 2016

On 7/8/16 9:33 AM, Hirayama, Pat wrote: > > This is the message (from just a few minutes ago, in fact): > > Jul 08 09:17:51 2016 (3892) Message discarded, msgid: <...> > > I am stumped. The sender is a non-moderated member. She is in fact, listed as a moderator. filter_content is set to no. ARCHIVE_HTML_SANITIZER does not appear to be set. dmarc_moderation_action is set to ACCEPT. header_filter_rules = []. The fact that she is listed as a moderator is irrelevant to this. Just to be sure, do 'ps -fww 3892' and verify that the process is IncomingRunner. Also note that starting with Mailman 2.1.19, the log message includes the name of the handler that raised the discard. See <https://bugs.launchpad.net/mailman/+bug/558096> and <http://bazaar.launchpad.net/~mailman-coders/mailman/2.1/revision/1502>. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 4

Re: [Mailman-Users] Message discarded without reason logged in vette
by Mark Sapiro July 8, 2016

July 8, 2016

On 7/8/16 9:00 AM, Hirayama, Pat wrote: > > WRT Content filtering -- if filter_content is set to NO, then nothing else in that section should apply, right? That is, even if there is stuff defined for pass_mime_types and filter_filename_extensions? That's correct. Note that what I wrote below applies only to the exact log entry "Message discarded, msgid: <...>". It seems that's the one you've seen, but there can be other messages such as "No command, message discarded, msgid: <...>" which is logged for messages sent to the -request address with no command or to -confirm with incorrect format. > > -----Original Message----- ... > If the message in the vette log is "Message discarded, msgid: <...>", > that message is only produced in standard Mailman by IncomingRunner when > a handler raises DiscardMessage. Again in standard Mailman, the only > Handlers that do that are: > > MimeDel > - content filtering removes the entire message and filter_action is > other than Reject > > Moderate > - a post is from a moderated member with member_moderation_action Discard > - a post is from a non-member in discard_these_nonmembers or with > generic_nonmember_action Discard > > Scrubber > - if the top level MIME type is text/html and ARCHIVE_HTML_SANITIZER = > 0 (not the default, and this only applies if scrub_nondigest is Yes) > > SpamDetect > - when a message matches KNOWN_SPAMMERS > - A post is From: a domain with DMARC p=reject (or maybe quarantine) > and dmarc_moderation_action is Discard > - a message matches header_filter_rules with Discard action or with > Reject action and the message is to -owner -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 1

Message discarded without reason logged in vette
by Hirayama, Pat July 8, 2016

July 8, 2016

So, I found a 10 year old post where Mark Sapiro described some of the reasons why "Message discarded" with only a message id and no reason happens: Examples are when nothing is left after content filtering, a post from a moderated user when action is discard, a post from a non-member in discard_these_nonmembers, a post from a non-member with generic action discard, some cases of a text/html post when ARCHIVE_HTML_SANITIZER = 0 and a post matching a header_filter_rule with discard action. I was wondering if there was a more complete list someplace? Mostly because I had this happen to one of my users 3 weeks ago, and I think that I've managed to rule out everything that Mark wrote back then. Thanks, -p -- Pat Hirayama Systems Engineer / 206.667.4856 / phirayam(a)fredhutch.org / Fred Hutch / Cures Start Here CIT | Enterprise IT Services / Advancing IT and Data Services to Accelerate the Elimination of Disease

2 2

Mailman installation does not work
by Bob Lydiate July 7, 2016

July 7, 2016

I am reinstalling Mailman after having to change servers. I am using Ubuntu 16.04, Apache, Postfix, Mailman. I have apache and postfix both working and serving mail and web. I have installed and re-installed Mailman a couple of times to try and get it working right and now have no idea what is creating the problem that stops it from working. I have several issues that I can identify, and I am sure there are several that I have missed. Problem 1 When I run 'check_perms -f' it tells me that the permissions on /var/lib/mailman/cron bad group (has:root, expected list) (fixing) this problem is repeated with 9 other scripts. When I check the actual directory '/var/lib/mailman' I find that these files are all links to '/usr/lib/*; where the correct group is set. When I try to access the web interface, I am asked if I want to open a file called 'admin' instead of opening a webpage called admin. when I run '/etc/init.d/mailman start' or the equivalent for postfix or apache, I get no errors. I did alter the config setup to have mydomain.ca rather than lists.mydomain.ca, but that is the only change I made to the config as it came through. I have checked the archives and have searched out the issues that I suspect, but have found nothing that worked to fix these issues. Bob

3 3