Mailman 3 May 2016 - Mailman-Users

Meaning of "Postfix SMTP server: errors from dd11328.otherdomain.tld[ip.ip.ip.ip]"
by Kala Balik May 10, 2016

May 10, 2016

Dear List-Members, today we ran our first mailing over our new Mailman instance. We received a few bounces and the following email which left me clueless. Please, what is this message trying to tell me? Is this us sending out, or is this someone trying to answer to our mailing (and failing to log in via TLS)? I checked my /var/log/mail logs - to no avail. Thanks for your answers! Cordially, KB Transcript of session follows. Out: 220 lists.domain.tld ESMTP Postfix (Ubuntu) In: EHLO dd11328.otherdomain.tld Out: 250-lists.domain.tld Out: 250-PIPELINING Out: 250-SIZE 10240000 Out: 250-VRFY Out: 250-ETRN Out: 250-STARTTLS Out: 250-ENHANCEDSTATUSCODES Out: 250-8BITMIME Out: 250 DSN In: STARTTLS Out: 454 4.7.0 TLS not available due to local problem In: MAIL FROM:<> SIZE=236 Out: 250 2.1.0 Ok In: RCPT TO:<list-bounces(a)lists.domain.tld> ORCPT=rfc822;list-bounces(a)lists.domain.tld Out: 250 2.1.5 Ok In: RSET Out: 250 2.0.0 Ok In: QUIT Out: 221 2.0.0 Bye For other details, see the local mail logfile

2 2

nodupes doesn't seem to be working with aliases
by Curtis Villamizar May 8, 2016

May 8, 2016

I'm not sure if this counts as suppressable dupes. All users have nodupes set. bin/export.py | grep nodupes | wc -l 183 bin/export.py | grep nodupes | grep -v True | wc -l 0 I have a postfix virtual-alias of the form: a b, c, d c e, f d g, h g i, j h k, l If I send mail to a set of mailing lists then dupes get suppressed but not if I send to an alias that expands to the same set of mailing lists. Mailman gets two copies from postfix but the message-id is the same for both. There is a to= and orig_to= in maillog but the messages should be otherwise identical including the timestamps. Is there a way to suppress dupes in this situation? I have 5 such aliases for convenience but if I can't suppress dupes its an annoyance since some people are on multiple mailing lists. For some reason I thought this used to work (but might have imagined it). I'd rather not send a bunch of cross posted test messages, though if more info is needed I can create some new "just for test" mailing lists and aliases (on a just for test server if need be). Curtis

2 2

Re: [Mailman-Users] disable DMARC_ORGANIZATIONAL_DOMAIN_DATA_URL in mailman 2.1
by Mark Sapiro May 8, 2016

May 8, 2016

On 05/05/2016 02:39 PM, Curtis Villamizar wrote: > In message <572AA1F6.8090807(a)msapiro.net> > Mark Sapiro writes: > >> As for as why it's a 554: 5.7.1 hard fail, That's the status your MTA is >> giving to this condition. If you think this should be a 4xx status, you >> may be able to configure that in your MTA. > > I think this might have been due to a connect to port 25 rather than > running sendmail. Connect to port 25 would only work if using TLS > (after STARTTLS) and then passing SASL auth. This host acts as an MDA > and as a MSA for mailman using a dual-stack "smarthost" relay but not > as an MX/MTA (MX points to two DS MTA and the MTA relays to it). > > If that is the case it was a config problem in mailman. I'm still > working on backing up and restoring a complete mailman config. (That > could be another topic). I would strongly suggest you not use DELIVERY_MODULE = 'Sendmail' If you need TLS and SASL, use DELIVERY_MODULE = 'SMTPDirect' in conjunction with the patch at <https://bugs.launchpad.net/mailman/+bug/558281>. I have now (finally) applied a version of this patch at <http://bazaar.launchpad.net/~mailman-coders/mailman/2.1/revision/1649>. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 1

dnspython not found error
by David Newman May 7, 2016

May 7, 2016

Had to reinstall the Mailman port (not pkg) on a FreeBSD 10.3-RELEASE system after updating some ports due to security vulnerabilities. Several other packages also required rebuild to point to new shared objects. The Mailman build failed, saying 'dnspython not found' even though that port is installed: root@mail:/usr/ports/mail/mailman # pkg info | grep dnspython py27-dnspython-1.12.0 DNS toolkit for Python I've attached the config log, and pasted below the list of installed ports. How to get Mailman working again? Thanks! dn root@mail:/usr/ports/mail/mailman # /usr/local/sbin/pkg-static info -g -Ea | cut -d ' ' -f 1 altermime-0.3.11.a1 amavisd-new-2.10.1_1,1 ap24-mod_wsgi3-3.5 apache24-2.4.20_1 apr-1.5.2.1.5.4 arc-5.21p arj-3.10.22_4 aspell-0.60.6.1_5 autoconf-2.69 autoconf-wrapper-20131203 automake-1.15_1 automake-wrapper-20131203 awstats-7.4,1 bacula-client-7.4.0_2 bash-static-4.3.42_1 bison-2.7.1,1 ca_root_nss-3.22.2 cabextract-1.6 cclient-2007f_2,1 clamav-0.99.1 cmake-3.5.2 cmake-modules-3.5.2 compat9x-amd64-9.3.903000.20160128 curl-7.47.0 cyrus-sasl-2.1.26_12 db5-5.3.28_3 dialog4ports-0.1.5_2 dovecot-pigeonhole-0.4.14 dovecot2-2.2.24 expat-2.1.0_3 fakeroot-1.20.2 file-5.25 freeze-2.5_2 gdbm-1.11_2 gettext-runtime-0.19.7 gettext-tools-0.19.7 gmake-4.1_2 gmake-lite-4.1_1 gnupg1-1.4.20 help2man-1.43.3_1 icu-55.1 indexinfo-0.2.4 json-c-0.12_2 jsoncpp-0.6.0.r2_2 lha-1.14i_6 libarchive-3.1.2_6,1 libcheck-0.10.0 libedit-3.1.20150325_2 libffi-3.2.1 libgcrypt-1.7.0 libgpg-error-1.22 libiconv-1.14_9 libidn-1.31 libltdl-2.4.6 libmcrypt-2.5.8_3 libressl-2.3.4 libssh2-1.7.0,2 libtool-2.4.6 libxml2-2.9.3 libxslt-1.1.28_8 logrotate-3.9.2 logwatch-7.4.0_1 lzo2-2.09 lzop-1.03 m4-1.4.17_1,1 mod_php55-5.5.35 mysql56-client-5.6.30 mysql56-server-5.6.30 nomarch-1.4 oniguruma5-5.9.6_1 p0f-3.09b p5-Archive-Zip-1.57 p5-Authen-SASL-2.16_1 p5-BerkeleyDB-0.55_1 p5-CPAN-Meta-2.150005 p5-Cache-FastMmap-1.43 p5-Canary-Stability-2011 p5-Config-IniFiles-2.88 p5-Convert-BinHex-1.125 p5-Convert-TNEF-0.18_1 p5-Convert-UUlib-1.50,1 p5-Crypt-CBC-2.33_1 p5-Crypt-DES-2.07_1 p5-Crypt-OpenSSL-Bignum-0.06 p5-Crypt-OpenSSL-RSA-0.28_1 p5-Crypt-OpenSSL-Random-0.11 p5-DBD-SQLite-1.50 p5-DBD-mysql-4.033 p5-DBI-1.636 p5-Digest-HMAC-1.03_1 p5-Digest-SHA1-2.13_1 p5-Encode-Detect-1.01_1 p5-Exporter-Tiny-0.042_1 p5-GSSAPI-0.28_1 p5-HTML-Parser-3.72 p5-HTML-Tagset-3.20_1 p5-HTTP-Date-6.02_1 p5-IO-Multiplex-1.13_1 p5-IO-Socket-INET6-2.72_1 p5-IO-Socket-IP-0.37 p5-IO-Socket-SSL-2.025 p5-IO-stringy-2.111 p5-Locale-gettext-1.06 p5-MIME-Base64-3.15 p5-MIME-Tools-5.507,2 p5-Mail-DKIM-0.40_2 p5-Mail-Tools-2.14 p5-Module-Build-0.4218 p5-Mozilla-CA-20160104 p5-Net-CIDR-0.18 p5-Net-DNS-1.05_1,1 p5-Net-IP-1.26_1 p5-Net-LibIDN-0.12_4 p5-Net-SNMP-6.0.1_1 p5-Net-SSLeay-1.74 p5-Net-Server-2.008_1 p5-Net-XWhois-0.90_5 p5-NetAddr-IP-4.078 p5-Socket-2.021 p5-Socket6-0.27 p5-TimeDate-2.30_2,1 p5-URI-1.71 p5-Unix-Syslog-1.1_1 p7zip-15.14 pcre-8.38_1 pecl-intl-3.0.0_2 perl5-5.20.3_12 php55-5.5.35 php55-bz2-5.5.35 php55-ctype-5.5.35 php55-dom-5.5.35 php55-filter-5.5.35 php55-gettext-5.5.35 php55-hash-5.5.35 php55-iconv-5.5.35 php55-imap-5.5.35 php55-json-5.5.35 php55-mbstring-5.5.35 php55-mcrypt-5.5.35 php55-mysql-5.5.35 php55-mysqli-5.5.35 php55-openssl-5.5.35 php55-pdo-5.5.35 php55-pdo_mysql-5.5.35 php55-pspell-5.5.35 php55-session-5.5.35 php55-simplexml-5.5.35 php55-xml-5.5.35 php55-zip-5.5.35 php55-zlib-5.5.35 pkg-1.7.2 pkgconf-0.9.12_1 popt-1.16_1 portmaster-3.17.9_2 postfix-3.1.0,1 py27-Babel-2.3.3 py27-Jinja2-2.8 py27-MarkupSafe-0.23 py27-MySQLdb-1.2.5 py27-alabaster-0.7.6 py27-bcrypt-0.4_2 py27-beautifulsoup-4.4.1 py27-cffi-1.5.0 py27-dnspython-1.12.0 py27-docutils-0.12 py27-enum34-1.0.4 py27-funcsigs-0.4 py27-idna-2.0 py27-ipaddress-1.0.16 py27-lxml-3.5.0 py27-mock-1.3.0_1 py27-netifaces-0.10.4 py27-pbr-1.8.1 py27-pip-8.0.2 py27-pyasn1-0.1.9 py27-pycparser-2.10 py27-pygments-2.1.3 py27-pystemmer-1.3.0_1 py27-pytz-2016.1,1 py27-setuptools27-20.0 py27-six-1.10.0 py27-snowballstemmer-1.2.0_1 py27-sphinx-1.3.1_2 py27-sphinx_rtd_theme-0.1.9 py27-sqlalchemy-0.7.10_2 py27-werkzeug-0.11.9 py27-zope.event-4.1.0 python2-2_3 python27-2.7.11_2 rar-5.3.0,3 re2c-0.14.3 ripole-0.2.2 roundcube-1.1.4_1,1 rpm2cpio-1.4_2 rsync-3.1.2_3 scons-2.5.0 spamassassin-3.4.1_6 sshguard-1.6.4_1 sudo-1.8.16 tinycdb-0.78_2 tnef-1.4.11 unarj-2.65_2 unrar-5.31,5 unzoo-4.4_2 vim-lite-7.4.1743 webpy-0.37 zoo-2.10.1_3

4 4

Problems using Postfix with Mailman
by Christopher Adams May 6, 2016

May 6, 2016

Hello all, I previously posted a message about a server "migration" of Mailman to a new CentOS 7 server. It actually is a rebuild and I will be trying to restore list info from backup. Anyway, I have Mailman installed and can access web pages and create lists. I am using Postfix as the MTA and I restored the main.cf file from the old server. I have indicated MTA ="Postfix" in mm_cfg.py, which I also moved over frrom old server backup. I restarted Postfix and Mailman. Now, when I post to a list, I get a variety of errors. In my own mailbox, I get this: mymailmanserver.com #<mymailmanserver.com#5.1.1 SMTP; 550 5.1.1 < osltest(a)mymailmanserver.com <osltest(a)listsmart.osl.state.or.us>>: Recipient address rejected: User unknown in local recipient table> #SMTP# In the maillog file, I get NOQUEUE: reject RCPT from localhost [::1] 454 4.71 <my.address(a)mydomain.com>: Relay access denied; from=< mylist-bounces(a)mymailmanserver.com> In the Mailman smtp-failure log file, I get: "Relay access denied" >From all that I have read, it must be a Postfix configuration problem, but since I just moved the old main.cf to the new server, I am perplexed. Posts to the Postfix-Users list has not been productive. If anyone uses Mailman and Postfix, maybe you can share your experiences. Many thanks. -- Christopher Adams adamsca(a)gmail.com

3 3

Re: [Mailman-Users] resend - mailman 2.1.21 - dmarc check problem
by Curtis Villamizar May 5, 2016

May 5, 2016

Mark, Sorry for the duplicate. In message <572AA8E4.9070405(a)msapiro.net> Mark Sapiro writes: > On 05/04/2016 09:27 AM, Curtis Villamizar wrote: > > I'm resending this with a new subject. The last email just > > disappeared (no bounce). Maybe having > > DMARC_ORGANIZATIONAL_DOMAIN_DATA_URL in the subject tripped an all > > caps in subject test. (Or the moderator is slacking?) > > > A moderator (me) approved your post and cleared your mod bit > approximately 2 hours before you posted this. My reply to that post is > at <https://mail.python.org/pipermail/mailman-users/2016-May/080772.html>. > > I don't know why you didn't receive it. It was successfully sent per > > May 4 10:36:04 mail postfix/smtp[22778]: 3r0LDW0F1DzFqP0: > to=<curtis(a)ipv6.occnc.com>, > relay=mta2-em1.orleans.occnc.com[50.252.223.140]:25, delay=42, > delays=0.08/0/31/11, dsn=2.0.0, status=sent (250 2.0.0 Ok: queued as > 316BF9DDA) > > (time stamp is UTC - 0400) Odd that is says 10:36. The URL in the archive says Wed May 4 21:29:26 EDT 2016 which matches mail headers. > Maybe the ALL CAPS filtered it at your end. I got the reply. I just didn't get any "held by moderator" so wasn't sure if my first mail went into a black hole. Did one get sent? Mail crossed. Your mail was sent (according to mail headers) at: Date: Wed, 4 May 2016 18:29:26 -0700 My duplicate was sent on: Date: Wed, 04 May 2016 12:27:24 -0400 which is 15:27 in -0700 land. My duplicate was sent 3 hours before your reply. In any case, sorry for the duplicate. If this was a "first time only" moderator action, then it can't happen again. Either way I appologize for being impatient. Curtis > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan

2 1

Re: [Mailman-Users] disable DMARC_ORGANIZATIONAL_DOMAIN_DATA_URL in mailman 2.1
by Mark Sapiro May 5, 2016

May 5, 2016

On 05/05/2016 02:39 PM, Curtis Villamizar wrote: > > And BTW - the server was given an IPv4 address before going to > production use but the IPv4 is only needed for apache, not for the > email setup. The IPv4 may be dropped entirely in the future since I > don't use the web interface anymore. Recipients are populated from a > database - which is one thing that has always worked fine. If your email address for @python.org email lists is on a server that only accepts connects at an IPv6 address, you will stop getting all list mail. The current cloud server for mail.python.org is blocked from sending to port 25 at IPv6 addresses. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 1

disable DMARC_ORGANIZATIONAL_DOMAIN_DATA_URL in mailman 2.1
by Curtis Villamizar May 5, 2016

May 5, 2016

By default DMARC_ORGANIZATIONAL_DOMAIN_DATA_URL is set to https://publicsuffix.org/list/public_suffix_list.dat I have mailman set up on an IPv6 only host and publicsuffix.org has no IPv6 address. A near identical configuration is set up on a dual stack host. Any email to the IPv6 only host fails with an entry in logs/error of the form "Unable to retrieve data from https://publicsuffix.org/list/public_suffix_list.dat: <urlopen error [Errno 43] Protocol not supported>" In the mean time I would like to disable the use of DMARC_ORGANIZATIONAL_DOMAIN_DATA_URL by setting it empty. To do this it seems that I would need the following change: --- Mailman/Utils.py.orig 2016-04-09 04:08:56.000000000 -0400 +++ Mailman/Utils.py 2016-05-03 14:37:12.683904000 -0400 @@ -1205,6 +1205,8 @@ Domain which may be the same as the input.""" global s_dict if not s_dict: - get_suffixes(mm_cfg.DMARC_ORGANIZATIONAL_DOMAIN_DATA_URL) + if mm_cfg.DMARC_ORGANIZATIONAL_DOMAIN_DATA_URL: + get_suffixes(mm_cfg.DMARC_ORGANIZATIONAL_DOMAIN_DATA_URL) hits = [] d = domain.lower().split('.') This works for .com, .org, .net, etc but not for things like co.uk, etc (which in my case is not an issue). A second question is why does failing to access publicsuffix.org result in a hard fail rather than a soft fail? The change I made just skips over get_suffixes and leaves s_dict empty. It seems that get_suffixes does do a try and except which logs and returns, but then the mail gets rejected and the reason is not clear to me. In logs/smtp-failure there is a message of the form "failed with code 554: 5.7.1 <fqdn[ipv6addr]>: Client host rejected: Access denied". Curtis

2 2

Re: [Mailman-Users] Order of operation - config files
by Beu, Ed (DOA) May 4, 2016

May 4, 2016

Hi, I got it working... <comments below> From: Beu, Ed (DOA) Sent: Wednesday, May 04, 2016 8:49 AM To: 'mailman-users(a)python.org' <mailman-users(a)python.org> Subject: Order of operation - config files Hello, We have a test installation of Mailman 2.1.20 (CSW) running on Solaris 10. Production version will be running on CentOS. Since most of our lists are 'Announcement' type lists, I have put the following in the mm_cfg.py file: DEFAULT_DEFAULT_MEMBER_MODERATION = Yes >>> The double DEFAULT_DEFAULT on this variable appears to be the only doubled default in the Defaults.py file. And, using it in the same manner in the MM_CFG.py file appears to be the only way to get it to work when creating a new list. For the occasional 'discussion' list I have created a config file (discuss.config) to import into the new list to change 'Member Moderation' to No, but it does not take effect. For example, I'm using this command: .../bin> ./newlist -q testdiscuss ed.beu(a)alaska.gov<mailto:ed.beu@alaska.gov> 12345678;./config_list -i discuss.config testdiscuss >>> I change the entry in the MM_CFG.py file to: DEFAULT_DEFAULT_MEMBER_MODERATION = 1 (1 rather than Yes) >>> used the following statement in my discuss.config file - and it's working now default_member_moderation = 0 Is it not possible to override the mm_cfg.py file entries with a config_list -i command? >>> apparently the config_list -i does run after mm_cfg.py!! Thanks in advance for any assistance! ~Ed Ed Beu , Systems Programmer Enterprise Technology Services Department of Administration 619 E Shipcreek Ave., Ste 232 Anchorage, AK 99501-1677 [ETSLogo]---------------------------------------- *Desk:(907)269-6790 ?Fax: (907)269-6719 * ed.beu(a)alaska.gov<mailto:ed.beu@alaska.gov> " http://www.doa.alaska.gov/ets/ ----------------------------------------

2 1

resend - mailman 2.1.21 - dmarc check problem
by Curtis Villamizar May 4, 2016

May 4, 2016

I'm resending this with a new subject. The last email just disappeared (no bounce). Maybe having DMARC_ORGANIZATIONAL_DOMAIN_DATA_URL in the subject tripped an all caps in subject test. (Or the moderator is slacking?) By default DMARC_ORGANIZATIONAL_DOMAIN_DATA_URL is set to https://publicsuffix.org/list/public_suffix_list.dat I have mailman set up on an IPv6 only host and publicsuffix.org has no IPv6 address. A near identical configuration is set up on a dual stack host. Any email to the IPv6 only host fails with an entry in logs/error of the form "Unable to retrieve data from https://publicsuffix.org/list/public_suffix_list.dat: <urlopen error [Errno 43] Protocol not supported>" It doesn't look as if publicsuffix.org will be getting an IPv6 address any time soon. The alternative github.com also doesn't have an IPv6 address. In the mean time I would like to disable the use of DMARC_ORGANIZATIONAL_DOMAIN_DATA_URL by setting it empty. To do this it seems that I would need the following change: - --- Mailman/Utils.py.orig 2016-04-09 04:08:56.000000000 -0400 +++ Mailman/Utils.py 2016-05-03 14:37:12.683904000 -0400 @@ -1205,6 +1205,8 @@ Domain which may be the same as the input.""" global s_dict if not s_dict: - get_suffixes(mm_cfg.DMARC_ORGANIZATIONAL_DOMAIN_DATA_URL) + if mm_cfg.DMARC_ORGANIZATIONAL_DOMAIN_DATA_URL: + get_suffixes(mm_cfg.DMARC_ORGANIZATIONAL_DOMAIN_DATA_URL) hits = [] d = domain.lower().split('.') In mm_sfg.py I just set "DMARC_ORGANIZATIONAL_DOMAIN_DATA_URL = ''". This works for .com, .org, .net, etc but not for things like co.uk, etc (which in my case is not an issue). A second question is why does failing to access publicsuffix.org result in a hard fail rather than a soft fail? The change I made just skips over get_suffixes and leaves s_dict empty. It seems that get_suffixes does do a "try and except" which logs and returns, but then the mail gets rejected and the reason is not clear to me by just reading the code. In logs/smtp-failure there is a message of the form "failed with code 554: 5.7.1 <fqdn[ipv6addr]>: Client host rejected: Access denied". Skipping get_suffixes throws no error and leaves s_dict empty. At most an error in get_suffixes should put the email in shunt but that seems to be in error handling upstream. Curtis

2 1