Package: mailman3
Version: 3.2.0-4~bpo9+1
Severity: grave
I'm finding it difficult to use the "domain" feature of Mailman 3. From
what I understand, it allows you to have two distinct mailing lists
named "test" on (say) t...@example.com and t...@example.net.
Here I'm specifically using the feature to host my mailing lists on
lists.anarc.at instead of plain anarc.at. Yet I don't know what I'm
doing wrong, but all outgoing email comes from t...@anarc.at instead of
t...@lists.anarc.at. This makes replies obviously fail as the LTMP maps
don't have that domain:
# grep ^[^#] /var/spool/postfix/mailman3/postfix_domains
# /var/spool/postfix/mailman3/postfix_lmtp
/var/spool/postfix/mailman3/postfix_domains:lists.anarc.at lists.anarc.at
/var/spool/postfix/mailman3/postfix_lmtp:
/var/spool/postfix/mailman3/postfix_lmtp:t...@lists.anarc.at
lmtp:[127.0.0.1]:8024
/var/spool/postfix/mailman3/postfix_lmtp:test-boun...@lists.anarc.at
lmtp:[127.0.0.1]:8024
/var/spool/postfix/mailman3/postfix_lmtp:test-conf...@lists.anarc.at
lmtp:[127.0.0.1]:8024
/var/spool/postfix/mailman3/postfix_lmtp:test-j...@lists.anarc.at
lmtp:[127.0.0.1]:8024
/var/spool/postfix/mailman3/postfix_lmtp:test-le...@lists.anarc.at
lmtp:[127.0.0.1]:8024
/var/spool/postfix/mailman3/postfix_lmtp:test-ow...@lists.anarc.at
lmtp:[127.0.0.1]:8024
/var/spool/postfix/mailman3/postfix_lmtp:test-requ...@lists.anarc.at
lmtp:[127.0.0.1]:8024
/var/spool/postfix/mailman3/postfix_lmtp:test-subscr...@lists.anarc.at
lmtp:[127.0.0.1]:8024
/var/spool/postfix/mailman3/postfix_lmtp:test-unsubscr...@lists.anarc.at
lmtp:[127.0.0.1]:8024
I've tried various things to fix this: I recreated the "domain" in the
Posterious interface. I have changed the "mailname" when running
dpkg-reconfigure mailman3-web, restarting it, which gave me this diff:
--- a/mailman3/mailman-web.py
+++ b/mailman3/mailman-web.py
@@ -130,7 +130,7 @@ USE_TZ = True
# Set default domain for email addresses.
-EMAILNAME = 'localhost.local'
+EMAILNAME = 'anarc.at'
# If you enable internal authentication, this is the address that the emails
# will appear to be coming from. Make sure you set a valid domain name,
Still, "mass subscribe" emails come out as "t...@anarc.at", even though
the footer clearly reads:
To unsubscribe send an email to test-le...@lists.anarc.at
When I write an email there, I get a reply saying to reply to:
test-confirm+14ea1ffec9434c30b983e1d5ab071b4988af4...@anarc.at
... which is still wrong and will (obviously) bounce.
What's going on here?
Here's a log of an admin mass-subscribing a user:
==> /var/log/mailman3/web/mailman-web.log <==
[pid: 2680|app: 0|req: 5/5] 192.168.0.7 () {82 vars in 1587 bytes} [Sat Feb 2
01:22:11 2019] POST
/mailman3/postorius/lists/test.lists.anarc.at/mass_subscribe/ => generated 9458
bytes in 468 msecs (HTTP/2.0 200) 6 headers in 317 bytes (3 switches on core 0)
==> /var/log/mail.log <==
Feb 1 20:22:12 marcos postfix/smtpd[4889]: connect from localhost[127.0.0.1]
Feb 1 20:22:12 marcos postfix/smtpd[4889]: DD2E510E1D8:
client=localhost[127.0.0.1]
Feb 1 20:22:12 marcos postfix/cleanup[5789]: DD2E510E1D8:
message-id=<154907053190.742.3083806269187387...@marcos.anarc.at>
==> /var/log/mailman3/smtp.log <==
Feb 01 20:22:12 2019 (746)
<154907053190.742.3083806269187387...@marcos.anarc.at> smtp to
t...@lists.anarc.at for 1 recips, completed in 0.03175711631774902 seconds
==> /var/log/mail.log <==
Feb 1 20:22:12 marcos postfix/qmgr[31811]: DD2E510E1D8:
from=<test-boun...@anarc.at>, size=581, nrcpt=1 (queue active)
Feb 1 20:22:12 marcos postfix/smtpd[5791]: connect from localhost[127.0.0.1]
==> /var/log/mailman3/smtp.log <==
Feb 01 20:22:12 2019 (746)
<154907053190.742.3083806269187387...@marcos.anarc.at> post to
t...@lists.anarc.at from test-requ...@lists.anarc.at, 362 bytes
==> /var/log/mail.log <==
Feb 1 20:22:12 marcos postfix/smtpd[4889]: disconnect from
localhost[127.0.0.1] ehlo=1 mail=1 rcpt=1 data=1 commands=4
Feb 1 20:22:12 marcos postfix/smtpd[5791]: EAED510E1DA:
client=localhost[127.0.0.1]
Feb 1 20:22:13 marcos spampd[24505]: processing message
<154907053190.742.3083806269187387...@marcos.anarc.at> for
<anar...@example.net> ORCPT=rfc822;anar...@example.net
Feb 1 20:22:14 marcos spampd[24505]: clean message
<154907053190.742.3083806269187387...@marcos.anarc.at> (-1.31/5.00) from
<test-boun...@anarc.at> for <anar...@example.net>
ORCPT=rfc822;anar...@example.net in 1.10s, 1087 bytes.
Feb 1 20:22:14 marcos postfix/cleanup[5789]: EAED510E1DA:
message-id=<154907053190.742.3083806269187387...@marcos.anarc.at>
Feb 1 20:22:14 marcos postfix/qmgr[31811]: EAED510E1DA:
from=<test-boun...@anarc.at>, size=1583, nrcpt=1 (queue active)
Feb 1 20:22:14 marcos postfix/smtp[5799]: DD2E510E1D8:
to=<anar...@example.net>, relay=127.0.0.1[127.0.0.1]:10025], delay=1.2,
delays=0.02/0/0.03/1.2, dsn=2.0.0, status=sent (250 2.0.0 Ok: queued as
EAED510E1DA)
Feb 1 20:22:14 marcos postfix/smtpd[5791]: disconnect from
localhost[127.0.0.1] ehlo=1 mail=1 rcpt=1 data=1 quit=1 commands=5
Feb 1 20:22:14 marcos postfix/qmgr[31811]: DD2E510E1D8: removed
Feb 1 20:22:15 marcos postfix/smtp[5790]: EAED510E1DA:
to=<anar...@example.net>, relay=mx1.example.net[...]:25], delay=2.6,
delays=1.2/0/0.82/0.66, dsn=2.0.0, status=sent (250 2.0.0 Ok: queued as
C47C11A042F)
Feb 1 20:22:15 marcos postfix/qmgr[31811]: EAED510E1DA: removed
Notice how the smtp.log still thinks it's for te...@lists.anarc.at but then
goes creating an email from test-boun...@anarc.at?
What's up with that? Did I misconfigure something?
I'm using postfix, hyperkitty, posterious and I don't know what else.
Let me know if you n eed more info.
-- System Information:
Debian Release: 9.7
APT prefers stable
APT policy: (500, 'stable'), (1, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.9.0-8-amd64 (SMP w/2 CPU cores)
Locale: LANG=fr_CA.UTF-8, LC_CTYPE=fr_CA.UTF-8 (charmap=UTF-8),
LANGUAGE=fr_CA.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages mailman3 depends on:
ii dbconfig-sqlite3 2.0.11~bpo9+1
ii debconf [debconf-2.0] 1.5.61
ii logrotate 3.11.0-0.1
ii lsb-base 9.20161125
ii python3 3.5.3-1
ii python3-aiosmtpd 1.1-6~bpo9+1
ii python3-alembic 0.8.8-2
ii python3-click 6.6-1
ii python3-dnspython 1.15.0-1
ii python3-falcon 1.0.0-2
ii python3-flufl.bounce 2.3-4
ii python3-flufl.i18n 2.0.1-1~bpo9+1
ii python3-flufl.lock 3.2-1~bpo9+1
ii python3-lazr.config 2.1-1
ii python3-passlib 1.7.0-2
ii python3-psycopg2 2.6.2-1
ii python3-public 0.5-1
ii python3-pymysql 0.7.10-1
ii python3-requests 2.12.4-1
ii python3-sqlalchemy 1.2.8+ds1-1~bpo9+1
ii python3-zope.component 4.3.0-1
ii python3-zope.configuration 4.0.3-3
ii python3-zope.event 4.2.0-1
ii python3-zope.interface 4.3.2-1
ii ucf 3.0036
Versions of packages mailman3 recommends:
ii postfix [mail-transport-agent] 3.1.8-0+deb9u1
Versions of packages mailman3 suggests:
ii chromium [www-browser] 71.0.3578.80-1~deb9u1
ii epiphany-browser [www-browser] 3.22.7-1
ii firefox-esr [www-browser] 60.5.0esr-1~deb9u1
ii lynx [www-browser] 2.8.9dev11-1
pn mailman3-doc <none>
ii mariadb-server-10.1 [virtual-mysql-server] 10.1.37-0+deb9u1
ii w3m [www-browser] 0.5.3-34+deb9u1
-- debconf information:
* mailman3/mysql/admin-user: debian-sys-maint
mailman3/remove-error: abort
mailman3/dbconfig-remove: true
mailman3/missing-db-package-error: abort
mailman3/db/dbname: mailman3
mailman3/remote/newhost:
mailman3/remote/host: localhost
mailman3/mysql/method: Unix socket
mailman3/internal/skip-preseed: false
mailman3/purge: false
mailman3/pgsql/changeconf: false
* mailman3/config_hyperkitty: true
mailman3/db/app-user: mailman3@localhost
mailman3/pgsql/authmethod-admin: ident
mailman3/passwords-do-not-match:
mailman3/dbconfig-upgrade: true
mailman3/pgsql/authmethod-user: password
mailman3/upgrade-error: abort
* mailman3/init_service_failed:
mailman3/pgsql/admin-user: postgres
mailman3/pgsql/manualconf:
mailman3/upgrade-backup: true
* mailman3/database-type: mysql
mailman3/remote/port: 3306
* mailman3/dbconfig-reinstall: false
mailman3/install-error: abort
mailman3/pgsql/method: TCP/IP
mailman3/db/basepath: /var/lib/mailman3/data
* mailman3/dbconfig-install: true
mailman3/pgsql/no-empty-passwords:
mailman3/internal/reconfiguring: false
