Search results for "2021" - Mailman-users

Re: postfix malformed address with confirm replies

by Stephen Willey Mats Mats

> On Feb 26, 2021, at 16:08:35 PST, Mark Sapiro <mark(a)msapiro.net> wrote: > > >>> The mail system >>> >>> <matsmats-mm3-test1-confirm+d6f77a2572ef55a8b2c4ca0d77de8493fbb55856(a)mm3.aca-aws.s.uw.edu>: >>> host 172.19.199.2[172.19.199.2] said: 553 5.1.3 Error: malformed address >>> (in reply to RCPT TO command) >>> Reporting-MTA: dns; ip-172-31-18-222.us-west-2.compute.internal >>> X-Postfix-Queue-ID: E144B8BC3C5 >>> X-Postfix-Sender: rfc822; stephen.s.w.matsmats(a)gmail.com >>> Arrival-Date: Fri, 26 Feb 2021 14:08:54 -0800 (PST) >>> >>> Final-Recipient: rfc822; matsmats-mm3-test1-confirm+d6f77a2572ef55a8b2c4ca0d77de8493fbb55856(a)mm3.aca-aws.s.uw.edu >>> Original-Recipient: rfc822;matsmats-mm3-test1-confirm+d6f77a2572ef55a8b2c4ca0d77de8493fbb55856(a)mm3.aca-aws.s.uw.edu >>> Action: failed >>> Status: 5.1.3 >>> Remote-MTA: dns; 172.19.199.2 >>> Diagnostic-Code: smtp; 553 5.1.3 Error: malformed address > > I have no idea why Postfix is saying > `matsmats-mm3-test1-confirm+d6f77a2572ef55a8b2c4ca0d77de8493fbb55856(a)mm3.aca-aws.s.uw.edu` > is a malformed address, but this is a Postfix issue, not Mailman. > > Can you successfully post to `matsmats-mm3-test1 > @mm3.aca-aws.s.uw.edu` how about a `help` command to > `matsmats-mm3-test1-request(a)mm3.aca-aws.s.uw.edu` > Yep, all day long. A ‘help’ command succeeded. As did sending the confirm command to the -request address. oh, and looking further at the postfix logs the message was accepted by postfix but the error pops-up when postfix tries to pass it on. Feb 26 14:08:54 ip-172-31-18-222 postfix/smtpd[5933]: connect from mail-pj1-f50.google.com[209.85.216.50] Feb 26 14:08:54 ip-172-31-18-222 postfix/smtpd[5933]: E144B8BC3C5: client=mail-pj1-f50.google.com[209.85.216.50] Feb 26 14:08:54 ip-172-31-18-222 postfix/cleanup[5966]: E144B8BC3C5: message-id=<9B650420-A50D-4E25-8B5B-C696C388B7DA(a)selby.com> Feb 26 14:08:54 ip-172-31-18-222 postfix/qmgr[3214]: E144B8BC3C5: from=<stephen.s.w.matsmats(a)gmail.com>, size=4575, nrcpt=1 (queue active) Feb 26 14:08:54 ip-172-31-18-222 postfix/smtpd[5933]: disconnect from mail-pj1-f50.google.com[209.85.216.50] Feb 26 14:08:54 ip-172-31-18-222 postfix/lmtp[5967]: E144B8BC3C5: to=<matsmats-mm3-test1-confirm+d6f77a2572ef55a8b2c4ca0d77de8493fbb55856(a)mm3.aca-aws.s.uw.edu>, relay=172.19.199.2[172.19.199.2]:8024, delay=0.08, delays=0.05/0.01/0/0.01, dsn=5.1.3, status=bounced (host 172.19.199.2[172.19.199.2] said: 553 5.1.3 Error: malformed address (in reply to RCPT TO command)) Feb 26 14:08:54 ip-172-31-18-222 postfix/cleanup[5966]: F0C468BC3C6: message-id=<20210226220854.F0C468BC3C6(a)ip-172-31-18-222.us-west-2.compute.internal> Feb 26 14:08:54 ip-172-31-18-222 postfix/qmgr[3214]: F0C468BC3C6: from=<>, size=6993, nrcpt=1 (queue active) Feb 26 14:08:54 ip-172-31-18-222 postfix/bounce[5968]: E144B8BC3C5: sender non-delivery notification: F0C468BC3C6 Feb 26 14:08:54 ip-172-31-18-222 postfix/qmgr[3214]: E144B8BC3C5: removed The mailman smtp.log show that the message came in but not much else. the mailman.log (and bounce.log) don’t show anything for that time. Feb 26 22:08:54 2021 (27) Available AUTH mechanisms: LOGIN(builtin) PLAIN(builtin) Feb 26 22:08:54 2021 (27) Peer: ('172.19.199.1', 51934) Feb 26 22:08:54 2021 (27) ('172.19.199.1', 51934) handling connection Feb 26 22:08:54 2021 (27) ('172.19.199.1', 51934) >> b'LHLO ip-172-31-18-222.us-west-2.compute.internal' Feb 26 22:08:54 2021 (27) ('172.19.199.1', 51934) >> b'MAIL FROM:<stephen.s.w.matsmats(a)gmail.com> SIZE=4575' Feb 26 22:08:54 2021 (27) ('172.19.199.1', 51934) sender: stephen.s.w.matsmats(a)gmail.com Feb 26 22:08:54 2021 (27) ('172.19.199.1', 51934) >> b'RCPT TO:<matsmats-mm3-test1-confirm+d6f77a2572ef55a8b2c4ca0d77de8493fbb55856(a)mm3.aca-aws.s.uw.edu>' Feb 26 22:08:54 2021 (27) ('172.19.199.1', 51934) >> b'RSET' Feb 26 22:08:54 2021 (27) ('172.19.199.1', 51934) >> b'QUIT' Feb 26 22:08:54 2021 (27) ('172.19.199.1', 51934) connection lost Feb 26 22:08:54 2021 (27) ('172.19.199.1', 51934) Connection lost during _handle_client() I’ve also reproduced this another address that is on an exchange server which is maybe a more vanilla example. steve > -- > 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)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/

4 years, 4 months

Re: REST API http://.../3.1/users/../preferred_address returns 404 for GET and POST

by Mark Sapiro

On 4/13/23 13:21, Eric Vyncke wrote: > Humm after some more investigations, it seems that my mailman3 installation via debian packages is completely mixed up :-( This would explain the issue if the REST API is using 3.2.2 code and postorius is expecting 3.3.5... > > drwxr-xr-x 29 root root 4096 Nov 18 2021 /usr/lib/python3/dist-packages/mailman > drwxr-xr-x 2 root root 4096 Nov 18 2021 /usr/lib/python3/dist-packages/mailman-3.2.2.egg-info > drwxr-xr-x 8 root root 4096 Nov 18 2021 /usr/lib/python3/dist-packages/mailmanclient > drwxr-xr-x 2 root root 4096 Nov 18 2021 /usr/lib/python3/dist-packages/mailmanclient-3.2.2.egg-info > drwxr-xr-x 4 root root 4096 Apr 13 14:29 /usr/lib/python3/dist-packages/mailman_hyperkitty > drwxr-xr-x 2 root root 4096 Apr 13 14:28 /usr/lib/python3/dist-packages/mailman_hyperkitty-1.1.0.egg-info > drwxr-sr-x 30 root staff 4096 Apr 13 09:32 /usr/local/lib/python3.8/dist-packages/mailman > drwxr-sr-x 2 root staff 4096 Nov 18 2021 /usr/local/lib/python3.8/dist-packages/mailman-3.3.5.dist-info > drwxr-sr-x 9 root staff 4096 Nov 18 2021 /usr/local/lib/python3.8/dist-packages/mailmanclient > drwxr-sr-x 2 root staff 4096 Nov 18 2021 /usr/local/lib/python3.8/dist-packages/mailmanclient-3.3.3.dist-info > drwxr-sr-x 4 root staff 4096 Apr 12 20:47 /usr/local/lib/python3.8/dist-packages/mailman_web > drwxr-sr-x 2 root staff 4096 Nov 18 2021 /usr/local/lib/python3.8/dist-packages/mailman_web-0.0.5.dist-info Yes, that would be the problem if the Python running Mailman core was using libraries in /usr/lib/python3/dist-packages/ and the Python running Django was using libraries in /usr/local/lib/python3.8/dist-packages/. The ability to get/set preferred_address via REST was added to Mailman core 3.3.0 and is not in 3.2.2. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 2 months

Re: [EXTERNAL] [Mailman-Users] Re: Help with 'The message has no valid senders'

by Mark Sapiro

On 5/19/21 10:37 AM, McGuire, Tommy M. (MSFC-IS90)[EAST2] wrote: > > Here are (what I think are :-)) the anonymized relevant parts of the smtp.log. > > May 19 08:52:29 2021 (126270) _handle_client readline: b'MAIL FROM:<aaaaaaaaaa.a.aaaaa-1(a)nasa.gov> SIZE=11726\r\n' > May 19 08:52:29 2021 (126270) ('127.0.0.1', 52130) >> b'MAIL FROM:<aaaaaaaaaa.a.aaaaa-1(a)nasa.gov> SIZE=11726' > May 19 08:52:29 2021 (126270) ('127.0.0.1', 52130) sender: aaaaaaaaaa.a.aaaaa-1(a)nasa.gov > May 19 08:52:29 2021 (126270) ('127.0.0.1', 52130) << b'250 OK' > ... > May 19 08:52:29 2021 (126270) DATA readline: b'From: "Aaaaa, Aaaaaaaaaa A. (location)[employer,\r\n' > May 19 08:52:29 2021 (126270) DATA readline: b' Inc.]" <aaaaaaaaaa.a.aaaaa-1(a)nasa.gov>\r\n' That all looks good. I don't understand what's wrong. Can you apply the attached patch to mailman/rules/no_senders.py and see what you get in Mailman's debug.log. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 1 month

Re: can't get mail into mailman3 in docker

by Mark Sapiro

On 8/6/21 11:28 AM, bob B wrote: > I see nothing for today when the error happens > in /opt/mailman/var/logs/smtp.log > > But the log has a bunch of these, but these stopped around the 4th > > Aug 04 19:46:04 2021 (28) Available AUTH mechanisms: LOGIN(builtin) PLAIN(builtin) > Aug 04 19:46:04 2021 (28) Peer: ('127.0.0.1', 33912) > Aug 04 19:46:04 2021 (28) ('127.0.0.1', 33912) handling connection > Aug 04 19:46:04 2021 (28) ('127.0.0.1', 33912) EOF received > Aug 04 19:46:04 2021 (28) ('127.0.0.1', 33912) Connection lost during _handle_client() > Aug 04 19:46:04 2021 (28) ('127.0.0.1', 33912) connection lost These are normal messages from the startup of Mailman's lmtp runner. If you correlate these with mailman.log, you'll probably see the server starting at these times. The fact that there is nothing in this log correlating with the Postfix message 2021-08-06T09:08:41.974225-04:00 dockerhost postfix/lmtp[109783]: D630B3083ED0: to=<test(a)mailman-docker.###.####>, relay=localhost[127.0.0.1]:8024, delay=0.11, delays=0.05/0.02/0.04/0, dsn=4.4.2, status=deferred (lost connection with localhost[127.0.0.1] while receiving the initial server greeting) seems to say that Postfix isn't really connecting to Mailman's lmtp and this is consistent with netstat -l not showing something listening on port 8024. I note you have lmtp_host: localhost in the [mta] section in mailman-extra.cfg. Try changing that to lmtp_host: 127.0.0.1 -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 10 months

Re: mailman3 exim4 and debian 1 problem fconnection lost

by Mark Sapiro

On 5/6/21 12:03 AM, roberto Burceni wrote: > [Mailman-Users] mailman3 and exim4 problem in debian bullseye > Good evening, > I'm configuring mailman3 with exim4 on a debian 11. > I followed the official documentation on mailman for exim. It seems to > be all rights, but I have a problem: > when I send a message to a new lists in exim logs I see that exim uses > correctly mailman router and transport. > Unfortunately in smtp.log in mailman3 log folder I have the following > error: > May 04 16:51:01 2021 (2337) ('127.0.0.1', 34746) sender: > servizioinformatico(a)uicbs.it > May 04 16:51:01 2021 (2337) ('127.0.0.1', 34746) Data: b'RCPT TO: > <listtest-unsubscribe(a)uicbs.it>' > > May 04 16:51:01 2021 (2337) ('127.0.0.1', 34746) recip: > listtest-unsubscribe(a)uicbs.it > May 04 16:51:01 2021 (2337) ('127.0.0.1', 34746) Data: b'DATA' > May 04 16:51:02 2021 (2337) ('127.0.0.1', 34746) Data: b'QUIT' > May 04 16:51:02 2021 (2337) ('127.0.0.1', 34746) connection lost > May 04 16:51:02 2021 (2337) Connection lost during _handle_client() > > This causes that messages are not sent from mailman to users. Have you > an idea of the problem? The connection lost messages are normal and not an error and not the cause of the message not being delivered to the list members. > I have no other errors in other log files What other log messages are there that might relate to this? Is mailman core running? Are there any entries in mailman's queues? Is the message Archived? Without more information, I can't say why the message isn't delivered. I can only say for certain the the smtp.log messages you show above are not related to the issue. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 2 months

Out runner not sending emails, stuck on recvFrom.

by 01ste02＠gmail.com

My mta is logging a connection, which times out every three minutes. The strace for the out runner shows the following: fstat(20, {st_mode=S_IFREG|0660, st_size=3063808, ...}) = 0 stat("/var/lib/mailman3/data/mailman.db", {st_mode=S_IFREG|0660, st_size=3063808, ...}) = 0 pread64(20, "SQLite format 3\0\20\0\1\1\0@ \0\0\1\32\0\0\2\354"..., 100, 0) = 100 fcntl(20, F_SETLK, {l_type=F_RDLCK, l_whence=SEEK_SET, l_start=1073741824, l_len=1}) = 0 fcntl(20, F_SETLK, {l_type=F_RDLCK, l_whence=SEEK_SET, l_start=1073741826, l_len=510}) = 0 fcntl(20, F_SETLK, {l_type=F_UNLCK, l_whence=SEEK_SET, l_start=1073741824, l_len=1}) = 0 stat("/var/lib/mailman3/data/mailman.db-journal", 0x7fff3e9a8120) = -1 ENOENT (No such file or directory) stat("/var/lib/mailman3/data/mailman.db-wal", 0x7fff3e9a8120) = -1 ENOENT (No such file or directory) fstat(20, {st_mode=S_IFREG|0660, st_size=3063808, ...}) = 0 pread64(20, "SQLite format 3\0\20\0\1\1\0@ \0\0\1\32\0\0\2\354"..., 4096, 0) = 4096 pread64(20, "\r\0\0\0\26\2\7\0\17\212\17E\16\372\16\230\16Y\f\220\n\240\n-\t\273\tI\10\300\10o"..., 4096, 106496) = 4096 pread64(20, "\0\0\0\0changes BOOLEAN, \n\tadministr"..., 4096, 32768) = 4096 pread64(20, "\r\v\234\0\23\0\333\0\r0\n\253\n5\t\240\10\201\7\370\6\324\6e\5\340\5\4\4\206\4\24"..., 4096, 114688) = 4096 pread64(20, "\r\0\330\0\24\0\231\0\v\266\vE\n\351\t\352\t\261\10f\7\305\0073\5,\4\305\4n\3\370"..., 4096, 208896) = 4096 fcntl(20, F_SETLK, {l_type=F_UNLCK, l_whence=SEEK_SET, l_start=0, l_len=0}) = 0 fcntl(20, F_SETLK, {l_type=F_RDLCK, l_whence=SEEK_SET, l_start=1073741824, l_len=1}) = 0 fcntl(20, F_SETLK, {l_type=F_RDLCK, l_whence=SEEK_SET, l_start=1073741826, l_len=510}) = 0 fcntl(20, F_SETLK, {l_type=F_UNLCK, l_whence=SEEK_SET, l_start=1073741824, l_len=1}) = 0 stat("/var/lib/mailman3/data/mailman.db-journal", 0x7fff3e9a92f0) = -1 ENOENT (No such file or directory) pread64(20, "\0\0\1\32\0\0\2\354\0\0\0\0\0\0\0\0", 16, 24) = 16 stat("/var/lib/mailman3/data/mailman.db-wal", 0x7fff3e9a92f0) = -1 ENOENT (No such file or directory) fstat(20, {st_mode=S_IFREG|0660, st_size=3063808, ...}) = 0 pread64(20, "\n\0\0\0\20\16\270\0\17\325\17N\17\304\179\17\262\17%\17\237\17\357\17\207\17\17\17w\16\371"..., 4096, 36864) = 4096 pread64(20, "\5\0\0\0\3\17\361\0\0\0\2\301\17\373\17\366\17\361\0\0\0\0\0\0\0\0\0\0\0\0\0\0"..., 4096, 28672) = 4096 pread64(20, "\r\0\0\0\4\0020\0\0020\f\274\10a\5H\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"..., 4096, 270336) = 4096 fcntl(20, F_SETLK, {l_type=F_UNLCK, l_whence=SEEK_SET, l_start=0, l_len=0}) = 0 fcntl(20, F_SETLK, {l_type=F_RDLCK, l_whence=SEEK_SET, l_start=1073741824, l_len=1}) = 0 fcntl(20, F_SETLK, {l_type=F_RDLCK, l_whence=SEEK_SET, l_start=1073741826, l_len=510}) = 0 fcntl(20, F_SETLK, {l_type=F_UNLCK, l_whence=SEEK_SET, l_start=1073741824, l_len=1}) = 0 stat("/var/lib/mailman3/data/mailman.db-journal", 0x7fff3e9a9390) = -1 ENOENT (No such file or directory) pread64(20, "\0\0\1\32\0\0\2\354\0\0\0\0\0\0\0\0", 16, 24) = 16 stat("/var/lib/mailman3/data/mailman.db-wal", 0x7fff3e9a9390) = -1 ENOENT (No such file or directory) fstat(20, {st_mode=S_IFREG|0660, st_size=3063808, ...}) = 0 pread64(20, "\2\r \0\31\fL\24\0\0\2\25\f\306\rO\17?\r\354\16-\ro\r\302\r\6\16d\r\211"..., 4096, 192512) = 4096 pread64(20, "\n\2\241\0\177\1k\1\17<\16\236\1\360\2\206\16\203\16h\16J\16.\1k\16\17\r\360\r\327"..., 4096, 1032192) = 4096 fcntl(20, F_SETLK, {l_type=F_UNLCK, l_whence=SEEK_SET, l_start=0, l_len=0}) = 0 clock_gettime(CLOCK_REALTIME, {tv_sec=1634752684, tv_nsec=599142985}) = 0 clock_gettime(CLOCK_REALTIME, {tv_sec=1634752684, tv_nsec=599473757}) = 0 getpid() = 1262375 write(17, "Oct 20 19:58:04 2021 (1262375) U"..., 101) = 101 clock_gettime(CLOCK_REALTIME, {tv_sec=1634752684, tv_nsec=600257524}) = 0 clock_gettime(CLOCK_REALTIME, {tv_sec=1634752684, tv_nsec=601667144}) = 0 getpid() = 1262375 write(17, "Oct 20 19:58:04 2021 (1262375) C"..., 59) = 59 socket(AF_INET, SOCK_STREAM|SOCK_CLOEXEC, IPPROTO_TCP) = 21 connect(21, {sa_family=AF_INET, sin_port=htons(465), sin_addr=inet_addr("127.0.0.1")}, 16) = 0 recvfrom(21, And the mailman smtp-log shows: Oct 20 19:58:04 2021 (1262375) <163474270655.1243104.7078333516263200191@xxx> delivery to xxx@xxx failed with code 444, Connection unexpectedly closed Oct 20 19:58:04 2021 (1262375) Using agent: <mailman.mta.bulk.BulkDelivery object at 0x7f219bf93310> Oct 20 19:58:04 2021 (1262375) Connecting to 127.0.0.1:465 when it times out. The debug log also shows this: Oct 20 18:42:46 2021 (1262296) [OutgoingRunner] doing periodic Oct 20 18:42:46 2021 (1262296) [OutgoingRunner] committing transaction Oct 20 18:42:46 2021 (1262296) [OutgoingRunner] checking short circuit Oct 20 18:42:46 2021 (1262296) [OutgoingRunner] short circuiting Oct 20 18:42:46 2021 (1262296) [OutgoingRunner] ending oneloop: 29 I have no clue as to what is going on. Has anyone experienced this before?

3 years, 8 months

Re: can't get mail into mailman3 in docker

by matthew＠alberti.us

I use the docker-mailman setup. Below is the partial contents of my mailman-extra.cfg. I think by default, you would use the Docker assigned private network IP addresses for communicating with the containers. In my setup, 172.19.199.1 is the host (where postfix is) and 172.19.199.2 is mailman-core... # EMAIL SERVER / MTA CONFIGURATION [mta] incoming: mailman.mta.postfix.LMTP outgoing: mailman.mta.deliver.deliver lmtp_host: 172.19.199.2 lmtp_port: 8024 smtp_host: 172.19.199.1 smtp_port: 25 configuration: /etc/postfix-mailman.cfg This is all really going to depend on your particular setup. I'm late to the thread; but let me know if that improves the situation. - Matt Alberti -----Original Message----- From: Mark Sapiro <mark(a)msapiro.net> Sent: Saturday, August 7, 2021 2:04 AM To: mailman-users(a)mailman3.org Subject: [MM3-users] Re: can't get mail into mailman3 in docker On 8/6/21 11:28 AM, bob B wrote: > I see nothing for today when the error happens in > /opt/mailman/var/logs/smtp.log > > But the log has a bunch of these, but these stopped around the 4th > > Aug 04 19:46:04 2021 (28) Available AUTH mechanisms: LOGIN(builtin) > PLAIN(builtin) Aug 04 19:46:04 2021 (28) Peer: ('127.0.0.1', 33912) > Aug 04 19:46:04 2021 (28) ('127.0.0.1', 33912) handling connection Aug > 04 19:46:04 2021 (28) ('127.0.0.1', 33912) EOF received Aug 04 > 19:46:04 2021 (28) ('127.0.0.1', 33912) Connection lost during > _handle_client() Aug 04 19:46:04 2021 (28) ('127.0.0.1', 33912) > connection lost These are normal messages from the startup of Mailman's lmtp runner. If you correlate these with mailman.log, you'll probably see the server starting at these times. The fact that there is nothing in this log correlating with the Postfix message 2021-08-06T09:08:41.974225-04:00 dockerhost postfix/lmtp[109783]: D630B3083ED0: to=<test(a)mailman-docker.###.####>, relay=localhost[127.0.0.1]:8024, delay=0.11, delays=0.05/0.02/0.04/0, dsn=4.4.2, status=deferred (lost connection with localhost[127.0.0.1] while receiving the initial server greeting) seems to say that Postfix isn't really connecting to Mailman's lmtp and this is consistent with netstat -l not showing something listening on port 8024. I note you have lmtp_host: localhost in the [mta] section in mailman-extra.cfg. Try changing that to lmtp_host: 127.0.0.1 -- 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)mailman3.org To unsubscribe send an email to mailman-users-leave(a)mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/

3 years, 10 months

Re: can't get mail into mailman3 in docker

by matthew＠alberti.us

Sorry for the double-tap. Apparently https://github.com/maxking/docker-mailman/pull/441 changed the behavior that I said was the default. We might need to see your docker-compose.yaml, with sensitive info removed, to know more about your setup. - Matt Alberti -----Original Message----- From: matthew(a)alberti.us <matthew(a)alberti.us> Sent: Saturday, August 7, 2021 8:21 PM To: mailman-users(a)mailman3.org Subject: [MM3-users] Re: can't get mail into mailman3 in docker I use the docker-mailman setup. Below is the partial contents of my mailman-extra.cfg. I think by default, you would use the Docker assigned private network IP addresses for communicating with the containers. In my setup, 172.19.199.1 is the host (where postfix is) and 172.19.199.2 is mailman-core... # EMAIL SERVER / MTA CONFIGURATION [mta] incoming: mailman.mta.postfix.LMTP outgoing: mailman.mta.deliver.deliver lmtp_host: 172.19.199.2 lmtp_port: 8024 smtp_host: 172.19.199.1 smtp_port: 25 configuration: /etc/postfix-mailman.cfg This is all really going to depend on your particular setup. I'm late to the thread; but let me know if that improves the situation. - Matt Alberti -----Original Message----- From: Mark Sapiro <mark(a)msapiro.net> Sent: Saturday, August 7, 2021 2:04 AM To: mailman-users(a)mailman3.org Subject: [MM3-users] Re: can't get mail into mailman3 in docker On 8/6/21 11:28 AM, bob B wrote: > I see nothing for today when the error happens in > /opt/mailman/var/logs/smtp.log > > But the log has a bunch of these, but these stopped around the 4th > > Aug 04 19:46:04 2021 (28) Available AUTH mechanisms: LOGIN(builtin) > PLAIN(builtin) Aug 04 19:46:04 2021 (28) Peer: ('127.0.0.1', 33912) > Aug 04 19:46:04 2021 (28) ('127.0.0.1', 33912) handling connection Aug > 04 19:46:04 2021 (28) ('127.0.0.1', 33912) EOF received Aug 04 > 19:46:04 2021 (28) ('127.0.0.1', 33912) Connection lost during > _handle_client() Aug 04 19:46:04 2021 (28) ('127.0.0.1', 33912) > connection lost These are normal messages from the startup of Mailman's lmtp runner. If you correlate these with mailman.log, you'll probably see the server starting at these times. The fact that there is nothing in this log correlating with the Postfix message 2021-08-06T09:08:41.974225-04:00 dockerhost postfix/lmtp[109783]: D630B3083ED0: to=<test(a)mailman-docker.###.####>, relay=localhost[127.0.0.1]:8024, delay=0.11, delays=0.05/0.02/0.04/0, dsn=4.4.2, status=deferred (lost connection with localhost[127.0.0.1] while receiving the initial server greeting) seems to say that Postfix isn't really connecting to Mailman's lmtp and this is consistent with netstat -l not showing something listening on port 8024. I note you have lmtp_host: localhost in the [mta] section in mailman-extra.cfg. Try changing that to lmtp_host: 127.0.0.1 -- 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)mailman3.org To unsubscribe send an email to mailman-users-leave(a)mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ _______________________________________________ Mailman-users mailing list -- mailman-users(a)mailman3.org To unsubscribe send an email to mailman-users-leave(a)mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/

3 years, 10 months

Re: Postorius no connection to REST API

by Richard Rosner

WARNING 2021-08-20 11:49:22,941 3975 django.request Not Found: /mailman3 WARNING 2021-08-20 11:49:22,941 3975 django.request Not Found: /mailman3 WARNING 2021-08-20 11:49:22,954 3975 django.request Not Found: /mailman3 WARNING 2021-08-20 11:49:22,954 3975 django.request Not Found: /mailman3 [pid: 3975|app: 0|req: 17/16] 127.0.0.1 () {56 vars in 1208 bytes} [Fri Aug 20 11:49:10 2021] GET /mailman3 => generated 5651 bytes in 13321 msecs \ (HTTP/1.1 404) 5 headers in 170 bytes (1 switches on core 0) [pid: 3975|app: 0|req: 17/17] 127.0.0.1 () {56 vars in 1208 bytes} [Fri Aug 20 11:49:07 2021] GET /mailman3 => generated 5651 bytes in 16373 msecs \ (HTTP/1.1 404) 5 headers in 170 bytes (1 switches on core 1) WARNING 2021-08-20 11:49:32,820 3975 django.request Not Found: /accounts WARNING 2021-08-20 11:49:32,820 3975 django.request Not Found: /accounts [pid: 3975|app: 0|req: 18/18] 127.0.0.1 () {56 vars in 1208 bytes} [Fri Aug 20 11:49:32 2021] GET /accounts => generated 5651 bytes in 251 msecs (H\ TTP/1.1 404) 5 headers in 170 bytes (1 switches on core 0) WARNING 2021-08-20 11:49:43,517 3975 django.request Not Found: /archives WARNING 2021-08-20 11:49:43,517 3975 django.request Not Found: /archives [pid: 3975|app: 0|req: 19/19] 127.0.0.1 () {56 vars in 1208 bytes} [Fri Aug 20 11:49:43 2021] GET /archives => generated 5651 bytes in 99 msecs (HT\ TP/1.1 404) 5 headers in 170 bytes (1 switches on core 1) The proxy pass config is <IfModule mod_proxy_uwsgi.c> ProxyPass /mailman3/favicon.ico ! ProxyPass /mailman3/static ! Proxypass "/mailman3" "http://127.0.0.1:8000/mailman3" ProxyPass "/postorius" "http://127.0.0.1:8000/postorius" ProxyPass "/hyperkitty" "http://127.0.0.1:8000/hyperkitty" ProxyPass "/accounts" "http://127.0.0.1:8000/accounts" ProxyPass "/django" "http://127.0.0.1:8000/django" ProxyPass "/user-profile" "http://127.0.0.1:8000/user-profile" ProxyPass "/archives" "http://127.0.0.1:8000/archives" </IfModule>

3 years, 10 months

Re: trying to clean up the "held messages" mess

by Bjoern Franke

Hi, > > What exceptions? Note that there is a lot of cleanup in the as yet > unreleased core 3.3.5. You might consider installing that. To do so, in > your virtualenv as the Mailman user do the exception was: 2021-05-27 21:56:25 [FALCON] [ERROR] GET /3.1/lists/nordwest(a)lists.ffnw.de/held?count=10&page=1 => Traceback (most recent call last): File "falcon/app.py", line 361, in falcon.app.App.__call__ File "/opt/mailman/mm/venv/lib/python3.7/site-packages/mailman/rest/post_moderation.py", line 174, in on_get resource = self._make_collection(request) File "/opt/mailman/mm/venv/lib/python3.7/site-packages/mailman/rest/helpers.py", line 182, in _make_collection entries = [as_dict(resource) for resource in collection] File "/opt/mailman/mm/venv/lib/python3.7/site-packages/mailman/rest/helpers.py", line 182, in <listcomp> entries = [as_dict(resource) for resource in collection] File "/opt/mailman/mm/venv/lib/python3.7/site-packages/mailman/rest/post_moderation.py", line 165, in _resource_as_dict assert resource is not None, resource AssertionError: None > ``` > pip install --upgrade git+https://gitlab.com/mailman/mailman > ``` Thanks, I've upgraded to 3.3.5b1. > > The exceptions you see are because entries are missing from the pended, > pendedkeyvalue and/or message tables. > The exceptions are gone after the upgrade and May 28 18:48:57 2021 (18041) task runner started. May 28 18:48:57 2021 (18041) Task runner evicted 70 expired pendings May 28 18:49:11 2021 (18041) Task runner deleted 77 orphaned workflows May 28 18:49:11 2021 (18041) Task runner deleted 76 orphaned requests May 28 18:49:25 2021 (18041) Task runner deleted 71 orphaned messages May 28 18:49:25 2021 (18041) Task runner evicted expired cache entries But since the upgrade from 3.2.1 to 3.3.x the list owners are spammed with ---- some.listmember(a)domain.tld's subscription has been disabled on nordwest(a)lists.ffnw.de due to their bounce score exceeding the mailing list's bounce_score_threshold. The triggering DSN if available is attached. --- and list members get corresponding notifications, but it seems Postfix did not create any bounces for them. I did not find any related bug report yet, but maybe I missed something. Best Regards Bjoern

4 years, 1 month

Mailman-users search results for query "2021"