Search results for "sapiro" - lists.mailman3.org

[MM3-users] Re: upgrading in FreeBSD 13.1-p7: problem with aiosmtpd and lmtp runner

by Mark Sapiro

On 4/2/23 03:57, Guillermo Hernandez (Oldno7) via Mailman-users wrote: > > I'm NOT blaming any of the parts involved... Sure, most probably is my > fault. But the last upgrade shows that the process that fail is involved > with mailman upgrade. The last server was working smoothly and it has > higher traffic than the first I tried. It cannot be that I missed that > something was not working for weeks (since the last upgrade of the OS) It depends on what you did. Mailman's lmtp runner would only encounter this issue at startup, so unless you restarted Mailman or rebooted the server, lmtp runner would have continued without issue even if there was an underlying OS problem. Also, I don't think the problem is with Mailman per se. The underlying issue is in the Python library socket module. Try the following in a Python 3 shell ``` $ python3 Python 3.9.16 (main, Dec 11 2022, 12:49:23) [GCC 9.4.0] on linux Type "help", "copyright", "credits" or "license" for more information. >>> from socket import AF_INET6, SOCK_STREAM, socket as makesock >>> sock = makesock(AF_INET6, SOCK_STREAM) >>> sock.bind(("::1", 0)) >>> sock.close() ``` This is essentially what aiosmtpd does and I expect that `sock = makesock(AF_INET6, SOCK_STREAM)` will throw the `OSError: [Errno 43] Protocol not supported` exception. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 6 months

[MM3-users] Re: hyperkitty threads by month question

by Mark Sapiro

On 7/26/24 20:53, Bryan Fields wrote: > mailmanweb=> DELETE FROM hyperkitty_thread WHERE id = 35670; > ERROR: update or delete on table "hyperkitty_thread" violates foreign > key constraint > "hyperkitty_email_thread_id_038c9aee_fk_hyperkitty_thread_id" on table > "hyperkitty_email" > DETAIL: Key (id)=(35670) is still referenced from table > "hyperkitty_email". > mailmanweb=> DELETE FROM hyperkitty_email WHERE id = 150555; > ERROR: update or delete on table "hyperkitty_email" violates foreign > key constraint > "hyperkitty_thread_starting_email_id_fa7c55f5_fk_hyperkitt" on table > "hyperkitty_thread" > DETAIL: Key (id)=(150555) is still referenced from table > "hyperkitty_thread". Well, that's a catch 22, you can't delete the email because it's referenced by the thread and you can't delete the thread because it's referenced by the email. You could always update those entries to remove the references, but deleting and reimporting is probably better. > I'll attempt to clean this up tomorrow an clean it up/re-import. > > Is there a quick/easy way to drop the entire archive from the db or must I > delete the entire list? If you can get to https://nanog-mm3.keekles.org/archives/list/nanog@nanog-mm3.keekles.org/ as a Django staff user or superuser, there is a Delete Archive button to delete the entire archive. Even if you can't get there, you may be able to get to the confirmation page at https://nanog-mm3.keekles.org/archives/list/nanog@nanog-mm3.keekles.org/del… -- 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

[MM3-users] Re: exim4 + mailman3 lmtp failure

by Mark Sapiro

On 5/6/20 12:52 PM, Thomas Drillich wrote: > lines from exim4/mainlog > 2020-05-06 21:48:08.506 [5776] 1jWQ1Y-0001VA-2A <= th(a)drillich.com H=mo4-p00-ob.smtp.rzone.de [85.215.255.20]:20961 I=[85.25.8.21]:25 P=esmtps L- X=TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256 CV=no S=7313 M8S=0 DKIM=drillich.com RT=0.146s id=bb5a020a-bcc3-81a2-b5ab-6d89eaf5b28d(a)drillich.com from <th(a)drillich.com> for seebruecke(a)listen.td3.eu > 2020-05-06 21:48:08.517 [5776] SMTP connection from mo4-p00-ob.smtp.rzone.de [85.215.255.20]:20961 I=[85.25.8.21]:25 closed by QUIT > 2020-05-06 21:48:08.787 [5777] 1jWQ1Y-0001VA-2A ** seebruecke(a)listen.td3.eu F=<th(a)drillich.com> P=<th(a)drillich.com> R=mailman3_router T=mailman3_transport: all hosts for 'listen.td3.eu' have been failing for a long time (and retry time not reached) It's not clear to me from the log what is happening. It all happens within a fraction of a second, so there don't seem to be any time outs involved. It seems the first two entries are the delivery of the message from th(a)drillich.com to exim for seebruecke(a)listen.td3.eu. I'm guessing here because I don't know that much about exim, but it looks like exim is trying to connect to listen.td3.eu rather than localhost to deliver the message and most likely, port 8024 is not open to the outside which is correct. I think you need to add hosts_override = true to your transport definition to tell exim to use `hosts = localhost` rather than the host part of the email address. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 5 months

[MM3-users] Re: About to Install MM3 -- Seeking clarification

by Mark Sapiro

On 10/19/22 21:23, Stephen J. Turnbull wrote: > Onyeibo Oku writes: > > > Mailman starts well from virtual environment though, ... but systemd > > doesn't replicate that success. > > systemd doesn't know anything about venv. If it's possible to source > (not call as a command!) the venv bin/activate script via systemd, > that should fix it. If not, we'll have to figure out what it is that > the venv provides that the current systemd config does not. I would > guess that after sourcing the venv's bin/activate Our suggested systemd script at https://docs.mailman3.org/en/latest/install/virtualenv.html#starting-mailma… has ExecStart=/opt/mailman/venv/bin/mailman start ExecReload=/opt/mailman/venv/bin/mailman restart ExecStop=/opt/mailman/venv/bin/mailman stop /opt/mailman/venv/bin/mailman should work whether or not a venv is active. Judging from the traceback, Onyeibo Oku's /opt/mailman/venv/bin/mailman is quite different from mine which is just ``` #!/opt/mailman/venv/bin/python3 # EASY-INSTALL-ENTRY-SCRIPT: 'mailman==3.3.5','console_scripts','mailman' __requires__ = 'mailman==3.3.5' import re import sys from pkg_resources import load_entry_point if __name__ == '__main__': sys.argv[0] = re.sub(r'(-script\.pyw?|\.exe)?$', '', sys.argv[0]) sys.exit( load_entry_point('mailman==3.3.5', 'console_scripts', 'mailman')() ) ``` What is yours? and can you start mailman as the mailman user with ``` /opt/mailman/venv/bin/mailman start ``` without activating the venv? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years

[MM3-users] Re: How to remove a message with an invalid Message-Id?

by Mark Sapiro

On 6/14/23 15:12, McGuire, Tommy M. (MSFC-IS61)[EAST2] via Mailman-users wrote: > I have a fun problem: apparently a message sent to a mailing list has an invalid Message-Id (I think), which is causing the message parse to fail while attempting to archive the message. Unfortunately, the message seems to be trapped somewhere and resulting in error logging every few minutes. Is there any way to find and remove the message? > > Literally, the only thing I've been able to find out about it is that the Message-Id contains the text "[83c48dddbea7492e873224a5ae1c04be-JFBVALKQOJXWILKNK4YVA7CBPJ2XEZKEMV3E64DTPRCW2YLJNR6EK6DPKNWXI4A=(a)microsoft.com]>". This is https://gitlab.com/mailman/mailman/-/issues/1065 which is fixed for the next release by https://gitlab.com/mailman/mailman/-/merge_requests/1099 You will find the message queued at Mailman's var/archives/hyperkitty/spool/ directory. You can examine the pickled message object with `mailman qfile` and you can simply remove the file. If you want to "fix" it and archive it, A `mailman shell` interaction like this will do it ``` >>> import pickle >>> with open('/path/to/.pck/file', 'rb') as fp: ... msg = pickle.load(fp) ... msgdata = pickle.load(fp) ... >>> msg.replace_header('Message-ID', '<83c48dddbea7492e873224a5ae1c04be-JFBVALKQOJXWILKNK4YVA7CBPJ2XEZKEMV3E64DTPRCW2YLJNR6EK6DPKNWXI4A=(a)microsoft.com>') >>> with open('/path/to/.pck/file', 'wb') as fp: ... pickle.dump(msg, fp) ... pickle.dump(msgdata, fp) ... >>> ``` -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 4 months

[MM3-users] Re: Moving mm3 -> mm3 to different host

by Mark Sapiro

On 10/19/23 02:38, Axel Rau wrote: > Hi all, > > There are lots of threads for mm2 -> mm3 moves, but only one > thread mm3 -> mm3. Some time ago, I found a post from Mark, explaining > the steps, but I can't find it again. > > I have created a working mm3 installation on the new host with both > mailman and mail-web dbs imported. > hyperkitty archive seems to in the db. > > What are the next steps to complete the transfer? > > - rsyncing messages, lists and templates to new host You may want to add archives/prototype to that. Also note that the contents of the messages/ directory should correspond to the entries in the message table in the mailman db. > - Setting up DNS CNAMES to the new server > - Adapting exim to accept mails to the aliased domain > > - Can I keep the old listname, with the old domain name? As long as mail to the list at that domain gets delivered to the new server. Note that in DNS if the domain has an MX record it must point to a domain with and A record and if there is no MX record, there must be an A record. CNAMEs won't do for mail delivery. > -What else has to be done ? I think that's it. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years

[MM3-users] Re: share directories between postfix and mailman 3

by Mark Sapiro

On 1/23/24 12:30, Thomas Schachtner via Mailman-users wrote: > > > Mark Sapiro wrote: >> >> Why do you think Mailman needs the contents of the postfix >> configuration file.. I don't think so. > I thought so, as mailman does not start if there's not > /etc/postfix/main.cf file is there. > > The following messages are logged: > Jan 23 21:20:35 mailman mailman3[491404]: RuntimeError: command failure: > /usr/sbin/postmap /var/lib/mailman3/data/postfix_lmtp, 1, Operation not > permitted > Jan 23 21:20:35 mailman mailman3[491404]: command failure: > /usr/sbin/postmap /var/lib/mailman3/data/postfix_domains, 1, Operation > not permitted Mailman itself is not looking for Postfix main.cf, but when Pustfix is the MTA, it invokes the postmap command to create the .db files for postfix_lmtp and postfix_domains. Apparently postmap fails if there is not a Postfix main.cf. You can avoid this by using regexp tables instead of hash tables. See <https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/mta.h…>. >>> This seemed to work pretty fine, as all files and directories seemed >>> to be available, but when starting mailman 3, the following error >>> message was shown: >>> FileExistsError: A race condition might have happened. >>> /var/lib/mailman3 actually exists and is not a directory. >>> >>> Any idea why this message is shown? >> >> Possibly because the uid and gid of /var/lib/mailman3 on the postfix >> machine do not map to the appropriate Mailman uid and gid on the >> mailman machine. > You refer to the uid and gid of the "list" user? They are both 38 (uid > and gid) on both machines. > Then that isn't the reason. I don't know then why Mailman would complain that /var/lib/mailman3 actually exists and is not a directory. This message comes from mailman.utilities.filesystem.makedirs(). The code is at <https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/utilities/file…>. makedirs() calls first_inexistent_directory() which checks if the directory exists with os.path.isdir() which apparently says it isn't a directory which makes no sense unless there is an actual race condition and you are creating the /var/lib/mailman3 directory on the mailman machine at the same time as you are starting mailman. BTW, you say you are doing sshfs root@postfix.example.com:/var/lib/mailman3 /var/lib/mailman3 on the mailman machine. Presumably on the mailman machine /var/lib/mailman3 has lots of content. How does that work? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 8 months

[MM3-users] Re: "Approved:" header from mailman2 times

by Mark Sapiro

On 04/09/2018 03:59 PM, Abhilash Raj wrote: > On Mon, Apr 9, 2018, at 3:00 PM, Dmitry Makovey wrote: >> Hi, >> >> is there any equivalent to "Approved" header that was present in MM2 in >> MM3 land? Google is not very helpful in that. > > It does exist in Mailman 3 as a carry-over from Mailman 2, but AFAIK it is broken. I don't think it is broken, but it requires setting the moderator_password attribute for the list which can be set visa REST but I think not by mailmanclient. > Also, I have been thinking of not having this as a feature in Mailman 3, mostly because of the issue of having shared passwords. No one should be sending out passwords anyway through plain emails anyway. > Agreed. This is a shared password. and would be sent in plain text as a header or body line. It would be nice though to have some feature to enable, for example, spoof proof posting to a one-way (announce only) list. One thought on how to do this would be to have a list attribute that says posts from 'authenticated' owners and moderators can be auto approved and authentication could be by PGP signing the post. This would require Mailman to have the ability to verify a PGP signature from an owner or moderator which is not currently the case. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

8 years, 6 months

[MM3-users] Re: Mailman3 / Exim4: Router fails

by Mark Sapiro

On 5/22/23 12:42, ceo(a)sartrack.nz wrote: > I found the problem with Exim4. > The Exim4 config file should contain this: > > MM3_LISTCHK=MM3_HOME/lists/${local_part}.${domain} > and NOT > MM3_LISTCHK=MM3_HOME/lists/${local_part}@${domain} > > Somewhere the documentation is wrong. The documentation at https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/mta.h… has MM3_LISTCHK=MM3_HOME/lists/${local_part}.${domain} Where did you see MM3_LISTCHK=MM3_HOME/lists/${local_part}@${domain} > But I now have the next problem: > I send an email to a new mailing list called templist(a)sartrack.nz (I imported my old list members). > in /var/log/mailman3 I get an error regarding this; > The (final) error states: > PermissionError: [Errno 13] Permission denied: '/var/lib/mailman3/lists/templist.sartrack.nz/digest.mmdf' > > The file digest.mmdf does not exist there at all. Because Mailman was trying to create it and couldn't. I suspect you ran `mailman create` as root and the /var/lib/mailman3/lists/templist.sartrack.nz/ got created with user:group as root:root rather than the mailman user and group. Recent Mailman versions won't run the `mailman` command as root without a --run-as-root option for this reason. How are you installing Mailman? > The mailing server does not send out any emails for "templist" This is a separate issue from the above error, but it might also be a permissions error. What other errors do you see in /var/log/mailman3/mailman.log? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 4 months

[MM3-users] Re: Installing mailman 3

by Mark Sapiro

On 07/23/2017 08:16 AM, Rafael Mora wrote: > This is the content of my /var/log: > > > [root@localhost log]# pwd > /var/log > [root@localhost log]# ls > anaconda grubby messages-20170716 spooler-20170710 > audit grubby_prune_debug messages-20170723 spooler-20170716 > boot.log httpd mysqld.log spooler-20170723 > btmp lastlog php-fpm tallylog > btmp-20170701 letsencrypt ppp tuned > chrony maillog rhsm wtmp > cron maillog-20170702 samba xferlog > cron-20170702 maillog-20170710 secure xferlog-20170702 > cron-20170710 maillog-20170716 secure-20170702 xferlog-20170710 > cron-20170716 maillog-20170723 secure-20170710 xferlog-20170716 > cron-20170723 mailman secure-20170716 xferlog-20170723 > dmesg messages secure-20170723 yum.log > dmesg.old messages-20170702 spooler > firewalld messages-20170710 spooler-20170702 Your current postfix log is /var/log/maillog. The files like /var/log/maillog-20170702, etc are older versions rotated by logrotate. On 07/23/2017 08:14 AM, Rafael Mora wrote: > content of the file maillog-20170723 (I didn't find mail.log in /var/log): > > [root@localhost log]# cat maillog-20170723 You want to be looking at /var/log/maillog for current messages. ... > Jul 21 16:10:47 localhost postfix/qmgr[2116]: error: open database > /var/lib/mailman/var/data/postfix_domains.db: No such file or directory Is this where these files are? You should have at least postfix_domains, postfix_domains.db, postfix_lmtp and postfix_lmtp.db in the /var/lib/mailman/var/data/ directory. It this the case? > output command 'postconf -n': > ... > transport_maps = hash:/var/libmailman/var/data/postfix_lmtp This is missing a / transport_maps = hash:/var/lib/mailman/var/data/postfix_lmtp -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

9 years, 2 months

Search results for query "sapiro"