Mailman 3 October 2015 - Mailman-Users

duplicates
by Marco Stoecker 28 Oct '15

28 Oct '15

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, I have Mailman up and running. I just sent an e-mail to 5 lists and the e-mail came duplicated to the recipients. I checked the header and the only difference is the following: 1. Header: X-Spam-Status: No, score=-1.5 required=5.0 tests=BAYES_00 autolearn=unavailable version=3.3.1 2. Header: X-Spam-Status: No, score=-1.5 required=5.0 tests=BAYES_00 autolearn=ham version=3.3.1 How can a avoid duplicates in future? What is the reason? BR Marco -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Icedove - http://www.enigmail.net/ iQIcBAEBAgAGBQJVCfIsAAoJEC1y3OsA+e10t2MP/0lS3W8F000CYn4MQ1M7Zfqj lzJskw5ysngsspQOCZ9kjBuHmh/TGHusZB90wkapMdAwlbuAypQKB6T7L6nwhKy4 xRkCxKJ6hZybb8g5pvatPnODbFfJE96kOAD9d6B1r5hv56FTE+/TG/50/kCQC4do 9AxsoBUD0hNcSwwTjazMGwGZ4NqDDVLXsrauCR02jB+VdqiZgGrGVnQUS6KRHKB+ fOc3VDxh/jbizRCkh8NFQfwW039QnLQyo+HM/pnYQyDcmsfyPg80/TMoyZLhR6PN NK3AZi+BykM8l7SfyWjmkltHERxYe3ouupQ0wPbWbOY/RCQ0gUUWb28CGZ3HChV6 eypbvPwnXk45WXvQuyhFsU7/KvWVBcb3MNezEm6Q/h5gQyI9FVmEABzjzsvkXxBg j9WhfiatL3ZN1cpCvb1RPxkP4hZ5YHf1fy9QqgXahLl+nuXSQu7IyKR0vJOXdq00 riB3Su7BWPV/lhaXXV6N9PA2TjjJ69tQ8oOfuB4UTJ19Wme1Zwo6J1pWkjY/xZsL izz9BrJeMZas2WqyBwHy2/mibyBMmG6nOW1F+FfqXSb/G/GZSA/yMg/5hb0GMgEc Fbihuiq2TW/TgkPkF+Bx6o+XtKAMA8yVAxrkOEo6YLbD28aga9uAKlai2ypiFQll 6aCeU5gwScRf5mlvnaay =Fkgv -----END PGP SIGNATURE-----

3 30

undo auto-discard
by Julia Lawall 28 Oct '15

28 Oct '15

I accidentally set someone to auto-discard. How do I undo that? julia

2 1

Confirmation by reply not working
by Keith Seyffarth 27 Oct '15

27 Oct '15

Hello, I'm having problems with the confirmation by reply working. When a user is invited to the list, or when a user subscribes on the web for, or when a user subscribes by emailing -join@, they are sent the confirmation email. If they replay to the email or create a new message and send ONLY the confirmation code as instructed, nothing happens. However, if they try again with the same confirmation code, they will get a response back that the confirmation code is no loger valid. This appears to indicate that mailman is receiving the email and processing it, but not actually subscribing them to the list. This is happening after moving to CentOS 7 using PLESK 12.5... Any ideas on what could be going on?

2 6

trying to understand Relay access denied (in reply to RCPT TO command)
by Ricardo Kleemann 27 Oct '15

27 Oct '15

Hi, I have some lists that have message delivery bounces returned and I can’t quite understand what’s going on. I’m using Postfix on the mailman server. In sending messages to either gmail or yahoo recipients, it seems to only work when the receiving end relays from a certain server, but errors when relaying through a different one. Not sure how to better explain so I’ll copy the examples here. The recipient addresses are people in Brazil, and the error cases are when mail is being relayed through there successful deliveries to yahoo and gmail, the relay shows a yahoo and gmail server respectively: Oct 23 13:18:07 localhost postfix/smtp[6101]: 0B0B344071: to=<xxxxxxx(a)yahoo.com>, relay=mta6.am0.yahoodns.net[98.138.112.35]:25, delay=1.4, delays=0.01/0.19/0.15/1, dsn=2.0.0, status=sent (250 ok dirdel) Oct 23 13:18:30 localhost postfix/smtp[6099]: AC6FC44166: to=< xxxxxxx(a)yahoo.com>, relay=mta5.am0.yahoodns.net[98.138.112.33]:25, delay=22, delays=0.01/21/0.16/1, dsn=2.0.0, status=sent (250 ok dirdel 2/0) Oct 24 06:18:54 localhost postfix/smtp[8152]: 61EF744176: to=< xxxxxxx(a)yahoo.com>, relay=mta5.am0.yahoodns.net[98.136.216.25]:25, conn_use=5, delay=19, delays=0.01/16/0.02/2.9, dsn=2.0.0, status=sent (250 ok dirdel 2/0) Oct 23 13:18:07 localhost postfix/smtp[6077]: 08E0F44070: to=<xxxxx(a)gmail.com>, relay=gmail-smtp-in.l.google.com[74.125.20.26]:25, delay=1, delays=0.01/0.61/0.05/0.33, dsn=2.0.0, status=sent (250 2.0.0 OK 1445631542 dl5si20130969pbb.108 - gsmtp) Oct 23 13:19:04 localhost postfix/smtp[6052]: 27EFF4448E: to=<xxxxx(a)gmail.com>, relay=gmail-smtp-in.l.google.com[74.125.20.26]:25, conn_use=57, delay=51, delays=0.01/50/0.03/0.39, dsn=2.0.0, status=sent (250 2.0.0 OK 1445631599 is2si31916407pbc.241 - gsmtp) Oct 23 13:26:59 localhost postfix/smtp[8446]: 220BF44B92: to=<xxxxx(a)gmail.com>, relay=gmail-smtp-in.l.google.com[74.125.28.26]:25, conn_use=4, delay=249, delays=0.01/248/0.06/0.43, dsn=2.0.0, status=sent (250 2.0.0 OK 1445632074 9si17275085ion.14 - gsmtp) Bad delivery attempts to same recipients at yahoo and gmail, but this time it’s relaying through a server in Brazil: Oct 24 06:27:26 localhost postfix/smtp[11544]: B7064449E0: to=< xxxxxxx(a)yahoo.com>, relay=mx2.ibest.com.br[177.153.23.241]:25, conn_use=17, delay=501, delays=0.03/501/0.2/0.21, dsn=5.7.1, status=bounced (host mx2.ibest.com.br[177.153.23.241] said: 554 5.7.1 < xxxxxxx(a)yahoo.com>: Relay access denied (in reply to RCPT TO command)) Oct 23 13:26:45 localhost postfix/smtp[8446]: 2039444A28: to=<xxxxx(a)gmail.com>, relay=mx2.ibest.com.br[177.153.23.241]:25, conn_use=9, delay=498, delays=0.01/497/0.25/0.21, dsn=5.7.1, status=bounced (host mx2.ibest.com.br[177.153.23.241] said: 554 5.7.1 <xxxxx(a)gmail.com>: Relay access denied (in reply to RCPT TO command) Oct 24 06:27:22 localhost postfix/smtp[8165]: 334874492E: to=<xxxxx(a)gmail.com>, relay=mx2.ibest.com.br[177.153.23.241]:25, conn_use=2, delay=497, delays=0.03/497/0.2/0.22, dsn=5.7.1, status=bounced (host mx2.ibest.com.br[177.153.23.241] said: 554 5.7.1 <xxxxx(a)gmail.com>: Relay access denied (in reply to RCPT TO command)) Oct 24 06:27:26 localhost postfix/smtp[11417]: AFCF644249: to=<xxxxx(a)gmail.com>, relay=mx2.ibest.com.br[177.153.23.241]:25, conn_use=3, delay=501, delays=0.03/501/0.21/0.24, dsn=5.7.1, status=bounced (host mx2.ibest.com.br[177.153.23.241] said: 554 5.7.1 <xxxxx(a)gmail.com>: Relay access denied (in reply to RCPT TO command)) In all failure scenarios, the relaying server (for both yahoo and gmail recipients) was the same. But what exactly is the relay error? Is it complaining that my own server isn’t properly configured for relay, or is it a problem on mx2.ibest.com.br <http://mx2.ibest.com.br/>? The info for my server and mailman is as follows: Server: relay1.americasnet.com <http://relay1.americasnet.com/> The lists address use either relay1.americasnet.com <http://relay1.americasnet.com/> or listas.americasnet.com <http://listas.americasnet.com/>. Both of these have MX and SPF records properly configured to point to relay1.americasnet.com <http://relay1.americasnet.com/>. So I don’t understand why would any server be bouncing back with a relay error. Does anyone have any ideas to help me out? thanks Ricardo

3 2

Mailman only deliveres inside server
by kapuzino＠web.de 25 Oct '15

25 Oct '15

Hello I'm using Mailman 2.1.18 as a customer of hosting. Mailman had worked fine primarily. After a server-update it deliveres messages only to email-adresses hostet on the same server (my own adresses connected to two different tld's). Using my own adresses everything is going well. External adresses only can write to the list. They don't get any mail an any request answers. A simple forwarding-list to the same adresses - established in plesk-panel - is doing its job. The system is a linux debian 3.16.7. Mailman was installed via Plesk. It uses Postfix und Dovecot. My hoster is a small one, I have a cheap account and I'm the only mailman user. So I want to help him solving. The hoster-guy is not familiar to mailman. He changed the server two times, reinstalled mailman 2.1.5 and then 2.1.18. Now he is out of idea. Is this a known problem ? A simple restriction server-setting ? Is any further information needed ? (phpinfo ?) If any Error logs are required, I have to ask the hoster. hoping for help regards Kapuzino

3 2

Welcome to the "Sathynz" mailing list (fwd)
by Thomas Gramstad 21 Oct '15

21 Oct '15

These are spammers, using a Mailman installation to add all e-mail addresses they can find. Can something be done about that? Thomas Gramstad ---------- Forwarded message ---------- Date: Tue, 20 Oct 2015 17:20:58 -0700 From: sathynz-request(a)sathy.co.nz To: sigar(a)ifi.uio.no Subject: Welcome to the "Sathynz" mailing list Welcome to the Sathynz(a)sathy.co.nz mailing list! To post to this list, send your message to: sathynz(a)sathy.co.nz General information about the mailing list is at: http://sathy.co.nz/mailman/listinfo/sathynz_sathy.co.nz If you ever want to unsubscribe or change your options (eg, switch to or from digest mode, change your password, etc.), visit your subscription page at: http://sathy.co.nz/mailman/options/sathynz_sathy.co.nz/sigar%40ifi.uio.no You can also make such adjustments via email by sending a message to: Sathynz-request(a)sathy.co.nz with the word `help' in the subject or body (don't include the quotes), and you will get back a message with instructions. You must know your password to change your options (including changing the password, itself) or to unsubscribe without confirmation. It is: waidpimo Normally, Mailman will remind you of your sathy.co.nz mailing list passwords once every month, although you can disable this if you prefer. This reminder will also include instructions on how to unsubscribe or change your account options. There is also a button on your options page that will email your current password to you.

2 1

Some subscriber's e-mail adresses contains line break unicode character 
by Henrik Rasmussen 21 Oct '15

21 Oct '15

In some occasions, a few subscribers of different lists contains the character  in the mail-address, like me(a)example.com<mailto:me@example.com> preventing them from receiving any mails from Mailman. The Unicode is always the same on affected subscribers. As what I've read it is a zero space line break unicode character. So far the only think I found was about HTML pages containing the character and a single post explains something about the character being added to a page through the Office 365 Public Website editor. But since subscribing to a Mailman list does not involve an editor, I assume that the character could have been added by a webbased mail client. >From what I've learned, the issue is associated with a random number of subscribers on different lists, having different admins in most cases - I currently have the issue on two lists having the same admin though, but two different subscribers. I don't know whether the subscribers have subscribed through mail or through the Mailman web interface, but since the problem is random, I assume that the Mailman web interface is not associated. I guess that it must be some kind of common web based MUA they have used, like Gmail or Hotmail or similar. What could course this and how can I prevent it? Yours faithfully Henrik Rasmussen

5 9

Spam/DKIM issues
by Marc Bourgeois 19 Oct '15

19 Oct '15

Hi to everyone, I'm trying to build a few mailing list with mailman. I've got some trouble with spam/dkim (In the past it was working out-of-the-box ! -without dkim) I'm running a Debian 7.9 server, with postfix. When I'm sending email from a system user, I can see in mail header : dkim=pass header.i=(a)example.xyz I'm experiencing some difficulties to understand how mailman process outgoing mail with a valid DKIM header. When a mailing list user send a mail through my list, sometimes header are filled with a X-Google-DKIM-Signature (depend on sender, gmail/google app domain...) but no sign of my original DKIM-Signature I've tried using REMOVE_DKIM_HEADERS yes or no, with no success Some opendkim issues can be found in mail.log: opendkim[1507]: 19D41278A1A5: no signing table match for 'kemkem42(a)gmail.com ' Whats this ? Is there a link to my problem ? Can someone help me with this ? My conf files below main.cf #mtpd_banner = $myhostname ESMTP $mail_name (Debian/GNU) biff = no # appending .domain is the MUA's job. append_dot_mydomain = no # Uncomment the next line to generate "delayed mail" warnings #delay_warning_time = 4h # TLS parameters smtpd_tls_cert_file=/etc/ssl/certs/ssl-cert-snakeoil.pem smtpd_tls_key_file=/etc/ssl/private/ssl-cert-snakeoil.key smtpd_use_tls=yes smtpd_tls_session_cache_database = btree:${queue_directory}/smtpd_scache smtp_tls_session_cache_database = btree:${queue_directory}/smtp_scache # See /usr/share/doc/postfix/TLS_README.gz in the postfix-doc package for # information on enabling SSL in the smtp client. myhostname = example.xyz alias_database = hash:/etc/aliases alias_maps = hash:/var/lib/mailman/data/aliases myorigin = example.xyz mydestination = example.xyz, localhost.localdomain, localhost #mynetworks = 127.0.0.0/8 mynetworks = 127.0.0.0/8 [::ffff:127.0.0.0]/104 [::1]/128 mailbox_command = procmail -a "$EXTENSION" mailbox_size_limit = 0 recipient_delimiter = + inet_interfaces = all relay_domains = example.xyz, localhost.localdomain, localhost #secu smtpd_helo_required = yes strict_rfc821_envelopes = yes smtpd_sender_restrictions = permit_mynetworks, reject_unknown_sender_domain, warn_if_reject reject_unverified_sender smtpd_recipient_restrictions = permit_mynetworks, reject_non_fqdn_hostname, reject_non_fqdn_sender, reject_non_fqdn_recipient, reject_unauth_destination, reject_invalid_hostname smtpd_client_restrictions = reject_unknown_client, permit_mynetworks milter_protocol = 2 milter_default_action = accept smtpd_milters = inet:localhost:12301 non_smtpd_milters = inet:localhost:12301 inet_protocols = all master.cf # # Postfix master process configuration file. For details on the format # of the file, see the master(5) manual page (command: "man 5 master"). # # Do not forget to execute "postfix reload" after editing this file. # # ========================================================================== # service type private unpriv chroot wakeup maxproc command + args # (yes) (yes) (yes) (never) (100) # ========================================================================== smtp inet n - - - - smtpd #submission inet n - - - - smtpd # -o smtpd_tls_security_level=encrypt # -o smtpd_sasl_auth_enable=yes # -o smtpd_client_restrictions=permit_sasl_authenticated,reject # -o milter_macro_daemon_name=ORIGINATING #smtps inet n - - - - smtpd # -o smtpd_tls_wrappermode=yes # -o smtpd_sasl_auth_enable=yes # -o smtpd_client_restrictions=permit_sasl_authenticated,reject # -o milter_macro_daemon_name=ORIGINATING #628 inet n - - - - qmqpd pickup fifo n - - 60 1 pickup cleanup unix n - - - 0 cleanup qmgr fifo n - n 300 1 qmgr #qmgr fifo n - - 300 1 oqmgr tlsmgr unix - - - 1000? 1 tlsmgr rewrite unix - - - - - trivial-rewrite bounce unix - - - - 0 bounce defer unix - - - - 0 bounce trace unix - - - - 0 bounce verify unix - - - - 1 verify flush unix n - - 1000? 0 flush proxymap unix - - n - - proxymap proxywrite unix - - n - 1 proxymap smtp unix - - - - - smtp # When relaying mail as backup MX, disable fallback_relay to avoid MX loops relay unix - - - - - smtp -o smtp_fallback_relay= # -o smtp_helo_timeout=5 -o smtp_connect_timeout=5 showq unix n - - - - showq error unix - - - - - error retry unix - - - - - error discard unix - - - - - discard local unix - n n - - local virtual unix - n n - - virtual lmtp unix - - - - - lmtp anvil unix - - - - 1 anvil scache unix - - - - 1 scache # # ==================================================================== # Interfaces to non-Postfix software. Be sure to examine the manual # pages of the non-Postfix software to find out what options it wants. # # Many of the following services use the Postfix pipe(8) delivery # agent. See the pipe(8) man page for information about ${recipient} # and other message envelope options. # ==================================================================== # # maildrop. See the Postfix MAILDROP_README file for details. # Also specify in main.cf: maildrop_destination_recipient_limit=1 # maildrop unix - n n - - pipe flags=DRhu user=vmail argv=/usr/bin/maildrop -d ${recipient} # # ==================================================================== # # Recent Cyrus versions can use the existing "lmtp" master.cf entry. # # Specify in cyrus.conf: # lmtp cmd="lmtpd -a" listen="localhost:lmtp" proto=tcp4 # # Specify in main.cf one or more of the following: # mailbox_transport = lmtp:inet:localhost # virtual_transport = lmtp:inet:localhost # # ==================================================================== # # Cyrus 2.1.5 (Amos Gouaux) # Also specify in main.cf: cyrus_destination_recipient_limit=1 # #cyrus unix - n n - - pipe # user=cyrus argv=/cyrus/bin/deliver -e -r ${sender} -m ${extension} ${user} # # ==================================================================== # Old example of delivery via Cyrus. # #old-cyrus unix - n n - - pipe # flags=R user=cyrus argv=/cyrus/bin/deliver -e -m ${extension} ${user} # # ==================================================================== # # See the Postfix UUCP_README file for configuration details. # uucp unix - n n - - pipe flags=Fqhu user=uucp argv=uux -r -n -z -a$sender - $nexthop!rmail ($recipient) # # Other external delivery methods. # ifmail unix - n n - - pipe flags=F user=ftn argv=/usr/lib/ifmail/ifmail -r $nexthop ($recipient) bsmtp unix - n n - - pipe flags=Fq. user=bsmtp argv=/usr/lib/bsmtp/bsmtp -t$nexthop -f$sender $recipient scalemail-backend unix - n n - 2 pipe flags=R user=scalemail argv=/usr/lib/scalemail/bin/scalemail-store ${nexthop} ${user} ${extension} mailman unix - n n - - pipe flags=FR user=list argv=/usr/lib/mailman/bin/postfix-to-mailman.py ${nexthop} ${user} mm_cfg.py """This is the module which takes your site-specific settings. >From a raw distribution it should be copied to mm_cfg.py. If you already have an mm_cfg.py, be careful to add in only the new settings you want. The complete set of distributed defaults, with annotation, are in ./Defaults. In mm_cfg, override only those you want to change, after the from Defaults import * line (see below). Note that these are just default settings - many can be overridden via the admin and user interfaces on a per-list or per-user basis. Note also that some of the settings are resolved against the active list setting by using the value as a format string against the list-instance-object's dictionary - see the distributed value of DEFAULT_MSG_FOOTER for an example.""" ####################################################### # Here's where we get the distributed defaults. # from Defaults import * ############################################################## # Put YOUR site-specific configuration below, in mm_cfg.py . # # See Defaults.py for explanations of the values. # #------------------------------------------------------------- # The name of the list Mailman uses to send password reminders # and similar. Don't change if you want mailman-owner to be # a valid local part. MAILMAN_SITE_LIST = 'mailman' #------------------------------------------------------------- # If you change these, you have to configure your http server # accordingly (Alias and ScriptAlias directives in most httpds) DEFAULT_URL_PATTERN = 'http://%s/cgi-bin/mailman/' PRIVATE_ARCHIVE_URL = '/cgi-bin/mailman/private' IMAGE_LOGOS = '/images/mailman/' #------------------------------------------------------------- # Default domain for email addresses of newly created MLs DEFAULT_EMAIL_HOST = 'endymion.xyz' #------------------------------------------------------------- # Default host for web interface of newly created MLs DEFAULT_URL_HOST = 'endymion.xyz' #------------------------------------------------------------- # Required when setting any of its arguments. add_virtualhost(DEFAULT_URL_HOST, DEFAULT_EMAIL_HOST) #------------------------------------------------------------- # The default language for this server. DEFAULT_SERVER_LANGUAGE = 'en' #------------------------------------------------------------- # Iirc this was used in pre 2.1, leave it for now USE_ENVELOPE_SENDER = 0 # Still used? #------------------------------------------------------------- # Unset send_reminders on newly created lists DEFAULT_SEND_REMINDERS = 0 #------------------------------------------------------------- # Uncomment this if you configured your MTA such that it # automatically recognizes newly created lists. # (see /usr/share/doc/mailman/README.Exim4.Debian or # /usr/share/mailman/postfix-to-mailman.py) # MTA=None # Misnomer, suppresses alias output on newlist #------------------------------------------------------------- # Uncomment if you use Postfix virtual domains (but not # postfix-to-mailman.py), but be sure to see # /usr/share/doc/mailman/README.Debian first. # MTA='Postfix' #------------------------------------------------------------- # Uncomment if you want to filter mail with SpamAssassin. For # more information please visit this website: # http://www.jamesh.id.au/articles/mailman-spamassassin/ # GLOBAL_PIPELINE.insert(1, 'SpamAssassin') # Note - if you're looking for something that is imported from mm_cfg, but you # didn't find it above, it's probably in /usr/lib/mailman/Mailman/Defaults.py. REMOVE_DKIM_HEADERS = No Thanks for reading Marc @obscur_moirage <https://twitter.com/obscur_moirage> | marc-bourgeois.net | dev.kprod.net | g+ <https://plus.google.com/111579343717579702540>

3 3

best way to transfer members from one list to another?
by Adam Morris 18 Oct '15

18 Oct '15

Hi all, I am looking at transferring all members from one list to another list. What is the easiest way to get the addresses to do this? -- Adam Morris email: adam(a)damorris.com

2 1

Additional questions about ban_list
by Chris Nulk 16 Oct '15

16 Oct '15

Hello all, I have been loosely following the discussion regarding regex in the ban_list attribute. I now find myself being asked to create a list which will most likely use the ban_list attribute. So, I have a few questions. 1. The ban_list attribute is to help prevent unwanted people from subscribing to a list, however, I want to restrict who can subscribe to the list and ban anyone else. I have the regex for who I want to allow to subscribe but there isn't an allow_list attribute. Is there an easy way of allowing a regex to control who is able to subscribe? Or, is there a way to easily invert the regex logic and use it in ban_list? As an example (not the real regex), say I want to only allow @gmail.com to subscribe to the list but no one else. 2. An additional requirement is to restrict a subgroup of the addresses from subscribing. In short, I want to allow all @gmail.com addresses to subscribe except for a known subgroup. Now the known subgroup is in a Mailman list. So, can I use a Mailman list in the ban_list attribute similar to using a list in *_these_members attributes? Or, would I have to modify the code to allow using a Mailman list in the ban_list attribute? Thank you for your consideration, Chris

3 9