Mailman 3 July 2016 - Mailman-Users

searchable archive options for cpanel server
by Jason Fayre 14 Jul '16

14 Jul '16

Hi, I really wish I didn't need to ask this, but alas, I do. We have a server running cPanel that hosts around 200 mailing lists. We really want to have searchable archives. If I install the mailman htdig patches, cPanel won't support us. Other than not using cPanel, what are other folks doing:? I know we have the option of using mailarchive.org, but we would like to keep the archives internal if possible. Any suggestions would be appreciated!

3 2

Re: [Mailman-Users] MailMan won't send list emails
by Caesar Samsi 13 Jul '16

13 Jul '16

[Adding information] Postfix /etc/postfix/main.cf configuration: virtual_alias_maps = mysql:/etc/postfix/mysql_virtual_alias_maps.cf, mysql:/etc/postfix/mysql_virtual_alias_domainaliases_maps.cf, hash:/var/lib/mailman/data/virtual-mailman alias_maps = hash:/etc/aliases, hash:/var/lib/mailman/data/aliases relay_domains = mail.samsi.us mailman_destination_recipient_limit = 1 transport_maps = hash:/etc/postfix/transport smtpd_reject_unlisted_sender = no /var/lib/mailman/data/virtual-mailman: test(a)yugi.us test /etc/aliases: # /etc/aliases mailer-daemon: postmaster postmaster: root nobody: root hostmaster: root usenet: root news: root webmaster: root www: root ftp: root abuse: root noc: root security: root clamav: root monit: root /var/lib/mailman/data/aliases: # This file is generated by Mailman, and is kept in sync with the # binary hash file aliases.db. YOU SHOULD NOT MANUALLY EDIT THIS FILE # unless you know what you're doing, and can keep the two files properly # in sync. If you screw it up, you're on your own. # The ultimate loop stopper address mailman-loop: /var/lib/mailman/data/owner-bounces.mbox # STANZA START: mailman # CREATED: Tue Jul 12 12:31:00 2016 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" # STANZA END: mailman # STANZA START: test # CREATED: Tue Jul 12 12:31:00 2016 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" # STANZA END: test /etc/postfix/transport: mail.samsi.us mailman: /etc/postfix/master.cf mailman unix - n n - - pipe flags=FR user=list argv=/usr/lib/mailman/bin/postfix-to-mailman.py ${nexthop} ${user} > On Jul 12, 2016, at 1:10 PM, Caesar Samsi <mailinglist(a)samsi.us> wrote: > > [resending, sent it before confirmation was completed earlier] > > Hi there, > > I’ve been working on this for 1 day and getting frustrated. > > Everything appears to be setup correctly (lists can be created, list emails are received, I can see emails received in the list mailbox. > > MailMan sends out notification emails to owners and subscribers. Confirmation email is sent out and processed via web page. > > The only thing left is sending out received emails. > > I don’t know where to begin troubleshooting this. > > Thanks, Caesar. >

2 3

Chinese characters spam filter?
by Greg Lindsay 13 Jul '16

13 Jul '16

Hi, I am running Mailman v 2.1.20 & have been trying to filter out Chinese spam messages with no luck. A few typical subjects are below: Subject: 为什么总让客户不满意，如何才能提升业绩 Subject: 没1有1业1绩，怎1么1办？ Subject: 带问题来，带方案走；如何缩短生产周期 Under Privacy options/Spam filters I have created header filters such as the three below. These aren't working. I was under the impression that [abcd] will discard all mail with a, b, c, or d in the subject line. I've tried including a hundred characters and a single character, but neither works. ^Subject:\*[如何解决企业关务管理风险跨境电商国家政策综解读及创新模式非财务人员如何进行财务管理掌握最规范的薪酬设计方法企业相关法律风险控制及用工管理如何加强企业反舞弊及内审如何把准经销商的赢利模式？如何评估供应商及优化采购运作流程如何掌握车间管理的精髓] ^Subject:\?utf-8\?B\?[56] ^Subject:\*[发杜营全及正了先] What am I doing wrong here? Is there something about the character encoding that prevents this filter from working? Thanks, -Greg

4 12

Re: [Mailman-Users] Mailman-Users Digest, Vol 149, Issue 16
by Gines Granados Bayona 13 Jul '16

13 Jul '16

Hello, well to everybody, thank you very much Mark Sapiro mark(a)msapiro.net, i do the steps and it has worked effectively, but It weirdest other error has occurred, I now send email that is outside the local network on Internet but lan I can not send email giving errors like that attached, what do I lacked configure now? Thank you very much ******-request(a)*****.net Mailing list subscription confirmation notice for mailing list Rancid We have received a request from 172.23.9.193 for subscription of your email address, "ginesgb(a)gmail.com", to the sistemas.rancid(a)******.net 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:// *****.*****.net/mailman/confirm/******/852fac84b3c566cec81644cc46c6b62d95f82bbc Or include the following line -- and only the following line -- in a message to ****************-request(a)*****.****.net: confirm 852fac84b3c566cec81644cc46c6b62d95f82bbc 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). ************************************ Jul 13 12:43:29 2016 (8111) All recipients refused: {'ginesgb(a)******.net': (550, '5.1.1 <ginesgb(a)******.net>: Recipient address rejected: User unknown in local recipient table')}, msgid: <mailman.0.1468406608.8166.*****(a)****.net> Jul 13 12:43:29 2016 (8111) delivery to ginesgb(a)******.net failed with code 550: 5.1.1 <ginesgb(a)******.net>: Recipient address rejected: User unknown in local recipient table 2016-07-12 21:22 GMT+02:00 <mailman-users-request(a)python.org>: > Send Mailman-Users mailing list submissions to > mailman-users(a)python.org > > To subscribe or unsubscribe via the World Wide Web, visit > https://mail.python.org/mailman/listinfo/mailman-users > or, via email, send a message with subject or body 'help' to > mailman-users-request(a)python.org > > You can reach the person managing the list at > mailman-users-owner(a)python.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of Mailman-Users digest..." > > Today's Topics: > > 1. Error unknown virtual host mailman (Gines Granados Bayona) > 2. Re: How to actively read the list online? (Stephen J. Turnbull) > 3. Re: How to actively read the list online? (Stephen J. Turnbull) > 4. Re: Error unknown virtual host mailman (Mark Sapiro) > 5. Re: How to actively read the list online? (jdd) > 6. Re: Chinese characters spam filter? (Mark Sapiro) > 7. Re: Filtering out Digest replies (Mark Sapiro) > > > ---------- Mensaje reenviado ---------- > From: Gines Granados Bayona <ginesgb(a)gmail.com> > To: mailman-users(a)python.org > Cc: > Date: Tue, 12 Jul 2016 13:10:38 +0200 > Subject: [Mailman-Users] Error unknown virtual host mailman > Hello everyone, I'm new in mailman and just made an installation of zero > mailman, with potsfix on centos 6. I have an error when trying to create a > new list in which shows me: > Error: Unknown virtual host... *** *** *** *** > I do not know what parameter settings I could make wrong, or should change > and though I've read several forums, I see that the fix are settings are > different , do We can indicate that parameter must change? > > Greetings and thank you > > -- > Este mensaje se dirige exclusivamente a su destinatario. Puede contener > información confidencial sometida a secreto profesional o cuya divulgación > este prohibida, en virtud de la legislación vigente. No esta permitida su > divulgación, copia o distribución a terceros sin la autorización previa y > por escrito del remitente. Si ha recibido este mensaje por error, le > rogamos nos lo comunique inmediatamente por esta misma vía y proceda a su > destrucción. > > > This e-mail is intended exclusively for the individual or entity to which > it is addressed > and may contain confidential or legally privileged information, which may > not be disclosed under current legislation. Any form of disclosure, copying > or distribution of this e-mail is strictly prohibited, save with written > authorisation . If you have received this message in error, please notify > the sender immediately by e-mail and delete all copies of the message. > > > > ---------- Mensaje reenviado ---------- > From: "Stephen J. Turnbull" <stephen(a)xemacs.org> > To: jdd <jdd(a)dodin.org> > Cc: mailman-users(a)python.org > Date: Wed, 13 Jul 2016 02:14:18 +0900 > Subject: Re: [Mailman-Users] How to actively read the list online? > jdd writes: > > > but couldn't gmane be a solution? > > > > http://gmane.org/ > > It would be better than pipermail, though, I think I prefer HyperKitty > to GMane. > > But for forum users, I don't think it would be close enough. > Specifically, I don't think GMane serves whole threads as a single > page; you have to click on next post. I don't know whether there's an > autorefresh on the header, either. It won't be a lot like the > experience with many forums (eg, Discourse). > > > > ---------- Mensaje reenviado ---------- > From: "Stephen J. Turnbull" <stephen(a)xemacs.org> > To: Lucio Chiappetti <lucio(a)lambrate.inaf.it> > Cc: Mailman list <mailman-users(a)python.org> > Date: Wed, 13 Jul 2016 02:17:32 +0900 > Subject: Re: [Mailman-Users] How to actively read the list online? > Lucio Chiappetti writes: > > > Personally (coming from Usenet, and used to read Usenet forums, i.e. > > newsgroups, via a MAIL client) I sort-of hate forums, > > Then you're definitely welcome here! :-) > > > Anyhow, getting a self-refreshing html page is just a matter of adding a > > <meta http-equiv=refresh content=nnn> tag to the <head> > > Sure, but if the page itself is static (as in a conventional mailing > list archive), that won't help. The archive host has to be prepared > to feed *new* pages, not refresh the old one, when accessed. > > > > > ---------- Mensaje reenviado ---------- > From: Mark Sapiro <mark(a)msapiro.net> > To: mailman-users(a)python.org > Cc: > Date: Tue, 12 Jul 2016 10:25:32 -0700 > Subject: Re: [Mailman-Users] Error unknown virtual host mailman > On 07/12/2016 04:10 AM, Gines Granados Bayona wrote: > > Hello everyone, I'm new in mailman and just made an installation of zero > > mailman, with potsfix on centos 6. I have an error when trying to create > a > > new list in which shows me: > > Error: Unknown virtual host... *** *** *** *** > > > It appears you are trying to create the list via the web create UI as > that is the only thing which issues the exact "Unknown virtual host" > error message. > > That error basically says that the host name in the URL that you went > to, e.g. http://host_name/mailman/create, does not exist in Mailman's > VIRTUAL_HOSTS dictionary which is created by add_virtualhost directives > in Defaults.py and mm_cfg.py. > > I'm guessing from your '*** *** *** ***' that you actually used an IP > address when visiting that page, possibly an 'internal network' one. You > don't want to create the list with such an address for its web host. > > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > > > > ---------- Mensaje reenviado ---------- > From: jdd <jdd(a)dodin.org> > To: > Cc: mailman-users(a)python.org > Date: Tue, 12 Jul 2016 19:38:33 +0200 > Subject: Re: [Mailman-Users] How to actively read the list online? > Le 12/07/2016 à 19:14, Stephen J. Turnbull a écrit : > > It would be better than pipermail, though, I think I prefer HyperKitty >> to GMane. >> > > sure, if you have mailman 3 suite :-) > > siome forums also have mialing list gateway, for example: > > https://doc.tiki.org/Forum+and+Mailing+List+Synchronization > > jdd > > > > > ---------- Mensaje reenviado ---------- > From: Mark Sapiro <mark(a)msapiro.net> > To: "Stephen J. Turnbull" <stephen(a)xemacs.org> > Cc: mailman-users(a)python.org > Date: Tue, 12 Jul 2016 11:47:48 -0700 > Subject: Re: [Mailman-Users] Chinese characters spam filter? > On 07/12/2016 12:03 AM, Stephen J. Turnbull wrote: > > Mark Sapiro writes: > > > On 7/8/16 6:04 PM, Yasuhito FUTATSUKI wrote: > > > > > > > > How about using 'backslashreplace' instead of 'replace' to encode to > > > > list's preferred language in Mailman/Handlers/SpamDetect.py ? > > > > I see you've already done this, but ... > > > > I would consider xmlrefreplace as well. xmlrefs are something most > > people (users/moderators) have seen, backslash they're not going to > > recognize unless they're programmers. > > > I have now switched to xmlcharrefreplace instead of backslashreplace as > I agree this will be easier to explain and understand. I was uncertain > about this at first because I didn't know that xmlcharrefreplace > wouldn't use entity names in some cases, but it appears that it only > uses numeric references. > > > > At an earlier stage, you could also just do a trial re-encoding with > > the list preferred codec, set errors = 'strict', catch the Exception, > > and re-raise as a Hold (or Discard, according to per-list policy). > > (Then discard the output.) I would prefer this solution, I think, as > > creating regexps turns out to be an issue for many list owners. > > > > People would have to learn not to use emoji in headers, of course, or > > suffer moderation delays or even discards. > > > I think this will have too many undesired effects. Not just emoji, but > accented latin or CJK characters, etc. in display names would I think be > real problems, even on English language lists. > > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > > > > ---------- Mensaje reenviado ---------- > From: Mark Sapiro <mark(a)msapiro.net> > To: mailman-users(a)python.org > Cc: > Date: Tue, 12 Jul 2016 12:22:04 -0700 > Subject: Re: [Mailman-Users] Filtering out Digest replies > On 07/12/2016 07:24 AM, Jim Popovitch wrote: > > On Tue, Jul 12, 2016 at 3:04 AM, Stephen J. Turnbull <stephen(a)xemacs.org> > wrote: > >> is something you should look at before deciding to stay with a product > >> after end-of-line. > > > > Doesn't this list traffic and interest prove that mm2x is nowhere near > > end of life? I mean the interest is here, should that be actively > > discouraged? > > > It depends on how you define "end of life". Granted there will be MM 2.1 > lists in use for a very long time. There may still even be Mailman 2.0 > lists in active use. > > The real question is not how long there will be users, but how long will > Mailman 2.1 be actively supported and maintained, and whether it makes > sense for new installations to use a package with little or no further > development in sight vs. one with an active and growing development and > support community. > > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > > > ------------------------------------------------------ > Mailman-Users mailing list > Mailman-Users(a)python.org > https://mail.python.org/mailman/listinfo/mailman-users > Mailman FAQ: http://wiki.list.org/x/AgA3 > Searchable Archives: > http://www.mail-archive.com/mailman-users%40python.org/ > -- Este mensaje se dirige exclusivamente a su destinatario. Puede contener información confidencial sometida a secreto profesional o cuya divulgación este prohibida, en virtud de la legislación vigente. No esta permitida su divulgación, copia o distribución a terceros sin la autorización previa y por escrito del remitente. Si ha recibido este mensaje por error, le rogamos nos lo comunique inmediatamente por esta misma vía y proceda a su destrucción. This e-mail is intended exclusively for the individual or entity to which it is addressed and may contain confidential or legally privileged information, which may not be disclosed under current legislation. Any form of disclosure, copying or distribution of this e-mail is strictly prohibited, save with written authorisation . If you have received this message in error, please notify the sender immediately by e-mail and delete all copies of the message.

2 1

Filtering out Digest replies
by Jim Popovitch 13 Jul '16

13 Jul '16

I've been inspired by something I read somewhere else. I have long thought that mailing lists should be configured to reject messages with a Subject of "Re: [the subject format for the list's digest messages]". Maybe a scan of the message content for a copy of the digest prologue would be a good idea as well. and now I want to implement something like this. Will this generic Spam filter work: Subject: Re: \[.*\] .* Digest, Vol [0-9]+, Issue [0-9]+ Tia, -Jim P.

8 14

How to actively read the list online?
by Richard Johnson 13 Jul '16

13 Jul '16

Hi! I'm hoping there's a quick answer to this. I looked but can't find it online. As of yesterday, I'm now running a mailing list for an interest group of about 50 people. I've run many other lists in the past, all using mailman, and never encountered the unique situation I'm seeing here. We moved the list of participants from a Yahoo Group. Some people were receiving individual messages and some were receiving digests. Those are fine. The people who are a problem are the ones who were *not* receiving any messages, but were instead reading the list online! They're used to seeing the entire list of messages on a web page and having it update automatically (I think). I haven't ever read a Yahoo Group list online, so I'm not sure. Is there any way to setup a web page which would automatically update to show the most recent messages in the archive? I have an archive setup and it receives a copy of the messages fairly quickly, but it doesn't update automatically and also anyone looking at it would need to update their URL at least every month, since the messages are organized by month. Anyone have something? Any help is much appreciated! /raj

5 10

MailMan won't send list emails
by Caesar Samsi 12 Jul '16

12 Jul '16

Hi there, I’ve been working on this for 1 day and getting frustrated. Everything appears to be setup correctly (lists can be created, list emails are received, I can see emails received in the list mailbox. MailMan sends out notification emails to owners and subscribers. Confirmation email is sent out and processed via web page. The only thing left is sending out received emails. I don’t know where to begin troubleshooting this. Thanks, Caesar.

1 0

Error unknown virtual host mailman
by Gines Granados Bayona 12 Jul '16

12 Jul '16

Hello everyone, I'm new in mailman and just made an installation of zero mailman, with potsfix on centos 6. I have an error when trying to create a new list in which shows me: Error: Unknown virtual host... *** *** *** *** I do not know what parameter settings I could make wrong, or should change and though I've read several forums, I see that the fix are settings are different , do We can indicate that parameter must change? Greetings and thank you -- Este mensaje se dirige exclusivamente a su destinatario. Puede contener información confidencial sometida a secreto profesional o cuya divulgación este prohibida, en virtud de la legislación vigente. No esta permitida su divulgación, copia o distribución a terceros sin la autorización previa y por escrito del remitente. Si ha recibido este mensaje por error, le rogamos nos lo comunique inmediatamente por esta misma vía y proceda a su destrucción. This e-mail is intended exclusively for the individual or entity to which it is addressed and may contain confidential or legally privileged information, which may not be disclosed under current legislation. Any form of disclosure, copying or distribution of this e-mail is strictly prohibited, save with written authorisation . If you have received this message in error, please notify the sender immediately by e-mail and delete all copies of the message.

2 1

Mailman 2 + Postfix + virtual domains + lists subdomain
by Jérôme 11 Jul '16

11 Jul '16

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 11 Jul '16

11 Jul '16

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