- Mailman-users - lists.mailman3.org

Mailing list name with capital letters?
by mrl＠psfc.mit.edu Sept. 26, 2023

Sept. 26, 2023

How can I create a mailing list with capital letters? Right now, only the first letter can be capitalized. Some of my mailing list names in mailman 2 had capital letters. When I migrated them to mailman 3, the capital letters remained. So it should be possible to create new ones? Thanks. - Mark

3 3

Mailman 3 - Header Filter
by Thomas Lehker Sept. 25, 2023

Sept. 25, 2023

I am a Mailman neophyte and need help with filtering posts based on the subject field. We have a few list owners that want 'Out of Office' replies discarded. When using the below syntax in Postorius/Header filter the post is not discarded but ends up in 'Held Messages'. Is there any syntax I am missing or a setting in the lists that needs to be disabled/enabled to get these posts dropped? Any help is much appreciated. Header: ^subject: subject: subject Pattern: Automatic Reply 'Automatic Reply' "Automatic Reply" Action: Discard DISCLAIMER: The information contained in this message is privileged and confidential. If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please reply to the message and delete/destroy any copy of this message. Information in this message that does not relate to the official business of the firm shall be understood as neither given nor endorsed by it.

4 4

Issues with @gmail.com addresses
by Mohsen Masoudfar Sept. 25, 2023

Sept. 25, 2023

Hi, since 8/1/2023 I get complains from users with @gmail.com addresses, that they are not getting any emails. I checked the logs and I see that the emails are going out: to=<xxxx(a)gmail.com>, relay=email-smtp.us-east-1.amazonaws.com[35.169.171.20]:587, delay=0.46, delays=0.03/0.06/0.13/0.24, dsn=2.0.0, status=sent (250 Ok xxx ) But it seems the users are getting email delivered to them. I’ve advised them to check their spam, promotions, and social folders and to add the list address to their email safe-senders lists, but still no success. Is there any way to help this list members? Thanks

8 21

Strange password problem
by Eggert Ehmke Sept. 25, 2023

Sept. 25, 2023

This happened several times recently with Postorius Version 1.3.8: -I try to log in as admin -rejected because of wrong password (password is stored in browser) -used forgotten password function -reset password to the stored value from browser -login works now. Works also when logged out/in again -however, the next day this behaviour repeats. Any hints?

6 22

how to administrate mailman3 in CLI ?
by testeur Sept. 23, 2023

Sept. 23, 2023

Hello, I have installed mailman3 and i want to administrate it with rest api, i ve read https://mailman-cli.readthedocs.io/en/latest/src/mailmanclient/cli/docs/usi… and https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rest/docs/… and https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/commands/d… i tryied with mailman command, but it don't do some actions (eg. delete held messages...). i tryied mailman shell... i tryied with curl to manage it, i can see if there is a pending message with : curl --user restadmin:restpass http://localhost:8001/3.1/lists/ml@domain.tld/held/count|| python3 -m json.tool| but how to delete all held messages ? is it possible in one time ? And how to select a specific message to discard /accept / defer ? do i have to use a POST ? Regards, PatG

3 4

Message getting held due to max number of recipients and maximum message size
by Wong, Wesley Sept. 22, 2023

Sept. 22, 2023

Hi all, I am running into an issue with messages getting held for a list with the following reasons: The message is being held because: Message has more than 10 recipients The message is larger than the 40 KB maximum size Either the message will get posted to the list, or you will receive notification of the moderator's decision. Currently, the settings are set to 0 for both settings on the list so I am not sure where mailman is getting the default settings. Is this default hard coded somewhere in the Mailman core? The version of Mailman running is 3.3.6. Any help for this issue is greatly appreciate. wesley Wesley Wong Senior Systems Engineer Anderson Computing & Information Services | ACIS 310-206-2571 [ucla-logo---new_smaller] ___________________________________________ Mailman's content filtering has removed the following MIME parts from this message. Content-Type: image/png Name: image001.png Replaced multipart/alternative part with first alternative.

2 3

Hyperkitty
by Massimiliano Paragnani Sept. 21, 2023

Sept. 21, 2023

I set up the mailman3 services and lists, and we can send mail to the list successfully. However in the Archive section I couldn't see anything. My configuration: ubuntu, milman core 3.2.2, postresql, postorius 1.2.4, hyperkitty 1.3.2 This is my mailman conf result: [antispam] header_checks: [antispam] jump_chain: hold [archiver.mail_archive] class: mailman.archiving.mailarchive.MailArchive [archiver.mail_archive] clobber_date: maybe [archiver.mail_archive] clobber_skew: 1d [archiver.mail_archive] configuration: python:mailman.config.mail_archive [archiver.mail_archive] enable: no [archiver.mhonarc] class: mailman.archiving.mhonarc.MHonArc [archiver.mhonarc] clobber_date: maybe [archiver.mhonarc] clobber_skew: 1d [archiver.mhonarc] configuration: python:mailman.config.mhonarc [archiver.mhonarc] enable: no [archiver.prototype] class: mailman.archiving.prototype.Prototype [archiver.prototype] clobber_date: maybe [archiver.prototype] clobber_skew: 1d [archiver.prototype] configuration: changeme [archiver.prototype] enable: no [bounces] register_bounces_every: 15m [database] class: mailman.database.postgresql.PostgreSQLDatabase [database] debug: no [database] url: postgres://mailman3:--------------@localhost/mailman3 [devmode] enabled: no [devmode] recipient: [devmode] testing: no [devmode] wait: 60s [digests] mime_digest_keep_headers: Date From To Cc Subject Message-ID Keywords In-Reply-To References Content-Type MIME-Version Content-Transfer-Encoding Precedence Reply-To Message List-Post [digests] plain_digest_keep_headers: Message Date From Subject To Cc Message-ID Keywords Content-Type [dmarc] cache_lifetime: 7d [dmarc] org_domain_data_url: https://publicsuffix.org/list/public_suffix_list.dat [dmarc] resolver_lifetime: 5s [dmarc] resolver_timeout: 3s [language.ar] charset: utf-8 [language.ar] description: Arabic [language.ar] enabled: yes [language.ast] charset: iso-8859-1 [language.ast] description: Asturian [language.ast] enabled: yes [language.ca] charset: utf-8 [language.ca] description: Catalan [language.ca] enabled: yes [language.cs] charset: iso-8859-2 [language.cs] description: Czech [language.cs] enabled: yes [language.da] charset: iso-8859-1 [language.da] description: Danish [language.da] enabled: yes [language.de] charset: utf-8 [language.de] description: German [language.de] enabled: yes [language.el] charset: iso-8859-7 [language.el] description: Greek [language.el] enabled: yes [language.es] charset: iso-8859-1 [language.es] description: Spanish [language.es] enabled: yes [language.et] charset: iso-8859-15 [language.et] description: Estonian [language.et] enabled: yes [language.eu] charset: iso-8859-15 [language.eu] description: Euskara [language.eu] enabled: yes [language.fi] charset: iso-8859-1 [language.fi] description: Finnish [language.fi] enabled: yes [language.fr] charset: iso-8859-1 [language.fr] description: French [language.fr] enabled: yes [language.gl] charset: utf-8 [language.gl] description: Galician [language.gl] enabled: yes [language.he] charset: utf-8 [language.he] description: Hebrew [language.he] enabled: yes [language.hr] charset: iso-8859-2 [language.hr] description: Croatian [language.hr] enabled: yes [language.hu] charset: iso-8859-2 [language.hu] description: Hungarian [language.hu] enabled: yes [language.ia] charset: iso-8859-15 [language.ia] description: Interlingua [language.ia] enabled: yes [language.it] charset: iso-8859-1 [language.it] description: Italian [language.it] enabled: yes [language.ja] charset: euc-jp [language.ja] description: Japanese [language.ja] enabled: yes [language.ko] charset: euc-kr [language.ko] description: Korean [language.ko] enabled: yes [language.lt] charset: iso-8859-13 [language.lt] description: Lithuanian [language.lt] enabled: yes [language.nl] charset: iso-8859-1 [language.nl] description: Dutch [language.nl] enabled: yes [language.no] charset: iso-8859-1 [language.no] description: Norwegian [language.no] enabled: yes [language.pl] charset: iso-8859-2 [language.pl] description: Polish [language.pl] enabled: yes [language.pt] charset: iso-8859-1 [language.pt] description: Protuguese [language.pt] enabled: yes [language.pt_BR] charset: iso-8859-1 [language.pt_BR] description: Protuguese (Brazil) [language.pt_BR] enabled: yes [language.ro] charset: iso-8859-2 [language.ro] description: Romanian [language.ro] enabled: yes [language.ru] charset: koi8-r [language.ru] description: Russian [language.ru] enabled: yes [language.sk] charset: utf-8 [language.sk] description: Slovak [language.sk] enabled: yes [language.sl] charset: iso-8859-2 [language.sl] description: Slovenian [language.sl] enabled: yes [language.sr] charset: utf-8 [language.sr] description: Serbian [language.sr] enabled: yes [language.sv] charset: iso-8859-1 [language.sv] description: Swedish [language.sv] enabled: yes [language.tr] charset: iso-8859-9 [language.tr] description: Turkish [language.tr] enabled: yes [language.uk] charset: utf-8 [language.uk] description: Ukrainian [language.uk] enabled: yes [language.vi] charset: utf-8 [language.vi] description: Vietnamese [language.vi] enabled: yes [language.zh_CN] charset: utf-8 [language.zh_CN] description: Chinese [language.zh_CN] enabled: yes [language.zh_TW] charset: utf-8 [language.zh_TW] description: Chinese (Taiwan) [language.zh_TW] enabled: yes [logging.archiver] datefmt: %b %d %H:%M:%S %Y [logging.archiver] format: %(asctime)s (%(process)d) %(message)s [logging.archiver] level: info [logging.archiver] path: mailman.log [logging.archiver] propagate: no [logging.bounce] datefmt: %b %d %H:%M:%S %Y [logging.bounce] format: %(asctime)s (%(process)d) %(message)s [logging.bounce] level: info [logging.bounce] path: bounce.log [logging.bounce] propagate: no [logging.config] datefmt: %b %d %H:%M:%S %Y [logging.config] format: %(asctime)s (%(process)d) %(message)s [logging.config] level: info [logging.config] path: mailman.log [logging.config] propagate: no [logging.database] datefmt: %b %d %H:%M:%S %Y [logging.database] format: %(asctime)s (%(process)d) %(message)s [logging.database] level: warn [logging.database] path: mailman.log [logging.database] propagate: no [logging.debug] datefmt: %b %d %H:%M:%S %Y [logging.debug] format: %(asctime)s (%(process)d) %(message)s [logging.debug] level: info [logging.debug] path: debug.log [logging.debug] propagate: no [logging.error] datefmt: %b %d %H:%M:%S %Y [logging.error] format: %(asctime)s (%(process)d) %(message)s [logging.error] level: info [logging.error] path: mailman.log [logging.error] propagate: no [logging.fromusenet] datefmt: %b %d %H:%M:%S %Y [logging.fromusenet] format: %(asctime)s (%(process)d) %(message)s [logging.fromusenet] level: info [logging.fromusenet] path: mailman.log [logging.fromusenet] propagate: no [logging.http] datefmt: %b %d %H:%M:%S %Y [logging.http] format: %(asctime)s (%(process)d) %(message)s [logging.http] level: info [logging.http] path: mailman.log [logging.http] propagate: no [logging.locks] datefmt: %b %d %H:%M:%S %Y [logging.locks] format: %(asctime)s (%(process)d) %(message)s [logging.locks] level: info [logging.locks] path: mailman.log [logging.locks] propagate: no [logging.mischief] datefmt: %b %d %H:%M:%S %Y [logging.mischief] format: %(asctime)s (%(process)d) %(message)s [logging.mischief] level: info [logging.mischief] path: mailman.log [logging.mischief] propagate: no [logging.plugins] datefmt: %b %d %H:%M:%S %Y [logging.plugins] format: %(asctime)s (%(process)d) %(message)s [logging.plugins] level: info [logging.plugins] path: plugins.log [logging.plugins] propagate: no [logging.root] datefmt: %b %d %H:%M:%S %Y [logging.root] format: %(asctime)s (%(process)d) %(message)s [logging.root] level: info [logging.root] path: mailman.log [logging.root] propagate: no [logging.runner] datefmt: %b %d %H:%M:%S %Y [logging.runner] format: %(asctime)s (%(process)d) %(message)s [logging.runner] level: info [logging.runner] path: mailman.log [logging.runner] propagate: no [logging.smtp] datefmt: %b %d %H:%M:%S %Y [logging.smtp] every: $msgid smtp to $listname for $recip recips, completed in $time seconds [logging.smtp] failure: $msgid delivery to $recip failed with code $smtpcode, $smtpmsg [logging.smtp] format: %(asctime)s (%(process)d) %(message)s [logging.smtp] level: info [logging.smtp] path: smtp.log [logging.smtp] propagate: no [logging.smtp] refused: $msgid post to $listname from $sender, $size bytes, $refused failures [logging.smtp] success: $msgid post to $listname from $sender, $size bytes [logging.subscribe] datefmt: %b %d %H:%M:%S %Y [logging.subscribe] format: %(asctime)s (%(process)d) %(message)s [logging.subscribe] level: info [logging.subscribe] path: mailman.log [logging.subscribe] propagate: no [logging.vette] datefmt: %b %d %H:%M:%S %Y [logging.vette] format: %(asctime)s (%(process)d) %(message)s [logging.vette] level: info [logging.vette] path: mailman.log [logging.vette] propagate: no [mailman] cache_life: 7d [mailman] default_language: en [mailman] email_commands_max_lines: 10 [mailman] filtered_messages_are_preservable: no [mailman] html_to_plain_text_command: /usr/bin/lynx -dump $filename [mailman] layout: debian [mailman] listname_chars: [-_.0-9a-z] [mailman] noreply_address: noreply [mailman] pending_request_life: 3d [mailman] post_hook: [mailman] pre_hook: [mailman] sender_headers: from from_ reply-to sender [mailman] site_owner: max.paragnani(a)gmail.com [mta] configuration: python:mailman.config.postfix [mta] delivery_retry_period: 5d [mta] incoming: mailman.mta.postfix.LMTP [mta] lmtp_host: 127.0.0.1 [mta] lmtp_port: 8024 [mta] max_autoresponses_per_day: 10 [mta] max_delivery_threads: 0 [mta] max_recipients: 500 [mta] max_sessions_per_connection: 0 [mta] outgoing: mailman.mta.deliver.deliver [mta] remove_dkim_headers: no [mta] smtp_host: localhost [mta] smtp_pass: [mta] smtp_port: 25 [mta] smtp_user: [mta] verp_confirm_format: $address+$cookie [mta] verp_confirm_regexp: ^(.*<)?(?P<addr>[^+]+?)\+(?P<cookie>[^@]+)@.*$ [mta] verp_confirmations: no [mta] verp_delimiter: + [mta] verp_delivery_interval: 0 [mta] verp_format: ${bounces}+${local}=${domain} [mta] verp_personalized_deliveries: no [mta] verp_probe_format: $bounces+$token@$domain [mta] verp_probe_regexp: ^(?P<bounces>[^+]+?)\+(?P<token>[^@]+)@.*$ [mta] verp_probes: no [mta] verp_regexp: ^(?P<bounces>[^+]+?)\+(?P<local>[^=]+)=(?P<domain>[^@]+)@.*$ [nntp] host: [nntp] password: [nntp] port: [nntp] remove_headers: nntp-posting-host nntp-posting-date x-trace x-complaints-to xref date-received posted posting-version relay-version received [nntp] rewrite_duplicate_headers: To X-Original-To CC X-Original-CC Content-Transfer-Encoding X-Original-Content-Transfer-Encoding MIME-Version X-MIME-Version [nntp] user: [passwords] configuration: python:mailman.config.passlib [passwords] password_length: 8 [plugin.master] class: [plugin.master] component_package: [plugin.master] configuration: [plugin.master] enabled: no [shell] banner: Welcome to the GNU Mailman shell [shell] history_file: [shell] prompt: >>> [shell] use_ipython: no [styles] default: legacy-default [webservice] admin_pass: --------------------------------- [webservice] admin_user: restadmin [webservice] api_version: 3.1 [webservice] hostname: localhost [webservice] port: 8001 [webservice] show_tracebacks: yes [webservice] use_https: no

7 20

Re: Importing mbox files into archive defect with lines with From
by Alex Schuilenburg Sept. 21, 2023

Sept. 21, 2023

Hi Stephen On 19/09/2023 19:59, Stephen J. Turnbull wrote: > Did you intend to send this to me only? Nope, apologies. I'm happy to add the list back in - I thought I hit reply-to-list. > Alex Schuilenburg writes: > > > Yes, I retested with from the git head as well. Same result. It > > sees the line > > > > From 1st April 2019, our turnover has exceeded the threshold for > > > > as the start of a new message and reports no anomolies although > > there is clearly one. > > If there is an empty line preceding that one, and the "F" is in the > first column (no marginal whitespace), that is considered correct > behavior for processing an mbox file. As an email separator agreed, provided the body has all "First " (preceded by a blank line and nothing preceding on the same line) suitably escaped. > If you don't like it, don't use the mbox format. The maildir > message-per-file format is widely supported, and if you want a > folder-per-file rather than message-per-file format, MMDF is fairly > widely supported, and does not suffer from the ambiguities of mbox. > All three (with variations) are supported by recent Python 3. Understood. My issue is the lists were imported from MM2.1 in 2020 into MM3.2.1 onto hyperkitty+mariadb/mysql. So the current installation has no mbox files - archives are stored in a mysql database. > > The old MM3 installation I am migrating away from is obviously > > broken in that its mbox archive when downloaded is not escaped, > > That's interesting. I presume that's because HyperKitty saves > messages in a database rather than as mbox files, and the old mbox > exporter just flattened and concatenated the messages. Or perhaps > that also uses mailbox.mbox and old enough versions of that didn't > From-stuff. Spot on. I have to move the lists onto a new Debian 12 server using the native mailman 3.3.8 & mailman-web 0+20200530-2 packages. I tried dropping in the old mailman3 database under the new software but that did not work. Instead I manually imported the old mailman3 data directly into the new mailman3 database as, after inspections, there were no new tables and only a couple of additional fields which have suitable defaults. So dumped the mailman3 data with mysqldump --no-create-info --no-create-db --disable-keys --complete-insert --ignore-table=mailman3.alembic_version mailman3 and simply imported the dump into the new schema. OK so far. The lists showed up in postorius, obviously without archives in hyperkitty. > The normal way to upgrade a HyperKitty archive is to do nothing, just > upgrade the software. I guess you moved to a new host and deleted the > database? The preferred way is to dump the database to SQL, and then > load it in to the new database directly rather than downloading the > mbox files and importing. No ambiguity and much faster. Thats what I thought initially, but that failed as per https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message…. As my old installation appears to have the django_migrations table inconsistent with the state of the database, and Debian have been unresponsive so far. Unfortunately the same mailman3-style manual import of mailman3web from old mailman3web db into the new db was not possible. There were additional tables and fields that needed values rather than defaults. Instead I opted to download the mbox exports from the old installation via the web interface and import them into the new installation for expediency.This is where I was when I posted the message. However, the old installation's mbox archive export (from the database) was problematic (e.g. 5min timeout) but after getting around those issues I ended up with some broken mbox files (e.g. the "From 1st April ..." line within a message, resulting in hyperkitty_import failures). > > although I tested downloading this thread archive and it is clearly > > escaped. Unfortunately I cannot tell if hyperkitty_import works > > using the git head since I am restricted to using the version > > provided with Debian 12. > > In July it worked for me on a site with 5300 archived lists. I assume > some of them had From-stuffed lines. Can't be sure, most of the posts > are machine-generated, but lines beginning with "From " are pretty > common in natural English. I'd be surprised if there were not any. I have 2003 lists and several occurrences. > > > There are indeed two versions though of mailbox.py on the VM: > > > > /usr/lib/python3/dist-packages/mailman/utilities/mailbox.py: from > > mailman3 (3.3.8-2~deb12u1) > > /usr/lib/python3.11/mailbox.py from libpython3.11-stdlib (3.11.2-6) > > The first applies one small change to the second (a so-called > "monkey-patch") for use by Mailman core. It should only be visible > to Python by the name "mailman.utilities.mailbox". The HyperKitty > utilities import the name "mailbox". If overwriting the first with > the second changes HyperKitty's behavior, something is wrong with > sys.path. Then I guess that is the case in Debian 12. > > > the latter of which appears far more substantial , so I dropped > > that module over the former and reran hyperkitty_import over the > > '>' escaped mbox, and while it did import without error, it did > > leave the escape in place (i.e. the 'From ...' was quoted when > > viewed). > > This is considered correct behavior. It is not possible to determine > whether the escape was in the original, or added by a receiving MTA. > Better to leave it. I thought that ">From " would be escaped to ">>From ", and so on, so the escape could easily be reversed when imported. I tested exports from the mailman-users lists and lines beginning "From " (preceded by a blank line) are escaped to ">From ", so incorrectly figured this would be unescaped by hyperkitty_import. After all, I would expect that an export of the archive to mbox, followed by a delete of the archive, followed by a hyperkitty_import of the archive, should leave you at the same place. Not with ">From " escapes in the new archives. In fact I also had a number of messages with "Message-ID: <>" and worse: all messages with attachments had the text/plain content empty. So mbox exports from MM 3.2.1 on Debian 10 (using hyperkitty+mysql) are broken. > > > The unescaped mbox import died in the same way. > > As expected. > > > Anyhow, thanks for your suggestion. For now I can stick with a > > manual repair and spaced escape of From_. > > If the old database is still available, I recommend dumping that and > loading it into a fresh version of the DBMS. > ... Thanks for the pointer. As I had already done the same with mailman3, so repeated the excercise. The following dump and import worked. oldhost> mysqldump --no-create-info --no-create-db --disable-keys --complete-insert mailman3web > mailman3web.sql newhost> mysql MariaDB [(none]> use mailman3web MariaDB [mailman3web]> source mailman3web.sql Thanks again -- Alex

2 3

Can't send emails to list users
by Rob Passalacqua Sept. 19, 2023

Sept. 19, 2023

I've looked on the forums and haven't found someone with the exact same issue as me. It appears that my mailman 3 server is either only sending to the first3 recipients on the list or only sending out mail to users that are members in Django because only 3 recipients are getting the emails. Here is my /var/log/mailman3/smtp.log: Sep 01 08:00:04 2023 (1405) <169357680279.2857929.16011221517221650936(a)lists.mydomain.com> smtp to graduates(a)lists.mydomain.com for 4 recips, completed in 0.028921127319335938 seconds Sep 01 08:00:04 2023 (1405) <169357680279.2857929.16011221517221650936(a)lists.mydomain.com> post to graduates(a)lists.mydomain.com from systemadmins(a)mydomain.com, 1107 bytes Sep 01 08:00:04 2023 (1405) <169357680284.2857929.17642987556878027498(a)lists.mydomain.com> smtp to undergraduates(a)lists.mydomain.com for 4 recips, completed in 0.00876307487487793 seconds Sep 01 08:00:04 2023 (1405) <169357680284.2857929.17642987556878027498(a)lists.mydomain.com> post to undergraduates(a)lists.mydomain.com from systemadmins(a)mydomain.com, 1384 bytes Sep 01 08:02:03 2023 (1405) <BY5PR04MB6787FC43405D111FDBF24BBBD2E5A(a)BY5PR04MB6787.namprd04.prod.outlook.com> smtp to graduates(a)lists.mydomain.com for 4 recips, completed in 0.08111977577209473 seconds Sep 01 08:02:03 2023 (1405) <BY5PR04MB6787FC43405D111FDBF24BBBD2E5A(a)BY5PR04MB6787.namprd04.prod.outlook.com> post to graduates(a)lists.mydomain.com from itroost(a)mydomain.com, 22320 bytes Sep 01 08:08:21 2023 (1405) <BY5PR04MB6787FC43405D111FDBF24BBBD2E5A(a)BY5PR04MB6787.namprd04.prod.outlook.com> smtp to undergraduates(a)lists.mydomain.com for 4 recips, completed in 0.08126330375671387 seconds Sep 01 08:08:21 2023 (1405) <BY5PR04MB6787FC43405D111FDBF24BBBD2E5A(a)BY5PR04MB6787.namprd04.prod.outlook.com> post to undergraduates(a)lists.mydomain.com from itroost(a)mydomain.com, 22320 bytes Sep 01 08:08:33 2023 (1405) <SJ0PR04MB7469F9DA4C471D4CF0AA8329C8E5A(a)SJ0PR04MB7469.namprd04.prod.outlook.com> smtp to undergraduates(a)lists.mydomain.com for 4 recips, completed in 0.19033193588256836 seconds Sep 01 08:08:33 2023 (1405) <SJ0PR04MB7469F9DA4C471D4CF0AA8329C8E5A(a)SJ0PR04MB7469.namprd04.prod.outlook.com> post to undergraduates(a)lists.mydomain.com from marcomm(a)mydomain.com, 627057 bytes Sep 08 13:16:05 2023 (1402) Available AUTH mechanisms: LOGIN(builtin) PLAIN(builtin) Sep 08 13:16:05 2023 (1402) Peer: ('127.0.0.1', 39988) Sep 08 13:16:05 2023 (1402) ('127.0.0.1', 39988) handling connection Sep 08 13:16:05 2023 (1402) ('127.0.0.1', 39988) Data: b'LHLO lists.mydomain.com' Sep 08 13:16:05 2023 (1402) ('127.0.0.1', 39988) Data: b'MAIL FROM:<radiga(a)mydomain.com>' Sep 08 13:16:05 2023 (1402) ('127.0.0.1', 39988) sender: radiga(a)mydomain.com Sep 08 13:16:05 2023 (1402) ('127.0.0.1', 39988) Data: b'RCPT TO:<undergraduates(a)lists.mydomain.com>' Sep 08 13:16:05 2023 (1402) ('127.0.0.1', 39988) recip: undergraduates(a)lists.mydomain.com Sep 08 13:16:05 2023 (1402) ('127.0.0.1', 39988) Data: b'DATA' Sep 08 13:16:05 2023 (1402) ('127.0.0.1', 39988) Data: b'QUIT' Sep 08 13:16:05 2023 (1402) ('127.0.0.1', 39988) connection lost Sep 08 13:16:05 2023 (1402) Connection lost during _handle_client() Sep 08 13:16:07 2023 (1405) <169420056594.1401.9589247638462690499(a)lists.mydomain.com> smtp to undergraduates(a)lists.mydomain.com for 1 recips, completed in 0.005960226058959961 seconds Sep 08 13:16:07 2023 (1405) <169420056594.1401.9589247638462690499(a)lists.mydomain.com> post to undergraduates(a)lists.mydomain.com from undergraduates-bounces(a)lists.mydomain.com, 1151 bytes Sep 08 14:26:48 2023 (1405) <CYYPR04MB90325509F556F72D6E562F1CA2EDA(a)CYYPR04MB9032.namprd04.prod.outlook.com> smtp to undergraduates(a)lists.mydomain.com for 4 recips, completed in 0.11815094947814941 seconds Sep 08 14:26:48 2023 (1405) <CYYPR04MB90325509F556F72D6E562F1CA2EDA(a)CYYPR04MB9032.namprd04.prod.outlook.com> post to undergraduates(a)lists.mydomain.com from radiga(a)mydomain.com, 19719 bytes Sep 11 16:28:09 2023 (1402) Available AUTH mechanisms: LOGIN(builtin) PLAIN(builtin) Sep 11 16:28:09 2023 (1402) Peer: ('127.0.0.1', 54070) Sep 11 16:28:09 2023 (1402) ('127.0.0.1', 54070) handling connection Sep 11 16:28:09 2023 (1402) ('127.0.0.1', 54070) Data: b'LHLO lists.mydomain.com' Sep 11 16:28:09 2023 (1402) ('127.0.0.1', 54070) Data: b'MAIL FROM:<mbutterworth(a)mydomain.com>' Sep 11 16:28:09 2023 (1402) ('127.0.0.1', 54070) sender: mbutterworth(a)mydomain.com Sep 11 16:28:09 2023 (1402) ('127.0.0.1', 54070) Data: b'RCPT TO:<graduates(a)lists.mydomain.com>' Sep 11 16:28:09 2023 (1402) ('127.0.0.1', 54070) recip: graduates(a)lists.mydomain.com Sep 11 16:28:09 2023 (1402) ('127.0.0.1', 54070) Data: b'RCPT TO:<undergraduates(a)lists.mydomain.com>' Sep 11 16:28:09 2023 (1402) ('127.0.0.1', 54070) recip: undergraduates(a)lists.mydomain.com Sep 11 16:28:09 2023 (1402) ('127.0.0.1', 54070) Data: b'DATA' Sep 11 16:28:09 2023 (1402) ('127.0.0.1', 54070) Data: b'QUIT' Sep 11 16:28:09 2023 (1402) ('127.0.0.1', 54070) connection lost Sep 11 16:28:09 2023 (1402) Connection lost during _handle_client() Sep 11 16:28:12 2023 (1405) <169447129087.1401.7570255973486097010(a)lists.mydomain.com> smtp to graduates(a)lists.mydomain.com for 1 recips, completed in 0.0067327022552490234 seconds Sep 11 16:28:12 2023 (1405) <169447129087.1401.7570255973486097010(a)lists.mydomain.com> post to graduates(a)lists.mydomain.com from graduates-bounces(a)lists.mydomain.com, 1125 bytes Sep 11 16:28:12 2023 (1405) <169447129099.1401.13948217098256502621(a)lists.mydomain.com> smtp to undergraduates(a)lists.mydomain.com for 1 recips, completed in 0.005612611770629883 seconds Sep 11 16:28:12 2023 (1405) <169447129099.1401.13948217098256502621(a)lists.mydomain.com> post to undergraduates(a)lists.mydomain.com from undergraduates-bounces(a)lists.mydomain.com, 1225 bytes Sep 12 08:00:04 2023 (1405) <169452720292.3537648.2620214486815282831(a)lists.mydomain.com> smtp to graduates(a)lists.mydomain.com for 4 recips, completed in 0.027950286865234375 seconds Sep 12 08:00:04 2023 (1405) <169452720292.3537648.2620214486815282831(a)lists.mydomain.com> post to graduates(a)lists.mydomain.com from systemadmins(a)mydomain.com, 1054 bytes Sep 12 08:00:04 2023 (1405) <169452720295.3537648.16444246393071130094(a)lists.mydomain.com> smtp to undergraduates(a)lists.mydomain.com for 4 recips, completed in 0.0057718753814697266 seconds Sep 12 08:00:04 2023 (1405) <169452720295.3537648.16444246393071130094(a)lists.mydomain.com> post to undergraduates(a)lists.mydomain.com from systemadmins(a)mydomain.com, 1151 bytes Sep 12 08:33:17 2023 (1405) <BYAPR04MB4438A507A16AE14A6CFF7E33A1F2A(a)BYAPR04MB4438.namprd04.prod.outlook.com> smtp to graduates(a)lists.mydomain.com for 4 recips, completed in 0.08274292945861816 seconds Sep 12 08:33:17 2023 (1405) <BYAPR04MB4438A507A16AE14A6CFF7E33A1F2A(a)BYAPR04MB4438.namprd04.prod.outlook.com> post to graduates(a)lists.mydomain.com from mbutterworth(a)mydomain.com, 53024 bytes Sep 12 08:33:26 2023 (1405) <BYAPR04MB4438A507A16AE14A6CFF7E33A1F2A(a)BYAPR04MB4438.namprd04.prod.outlook.com> smtp to undergraduates(a)lists.mydomain.com for 4 recips, completed in 0.061426639556884766 seconds Sep 12 08:33:26 2023 (1405) <BYAPR04MB4438A507A16AE14A6CFF7E33A1F2A(a)BYAPR04MB4438.namprd04.prod.outlook.com> post to undergraduates(a)lists.mydomain.com from mbutterworth(a)mydomain.com, 53024 bytes Sep 12 13:19:19 2023 (1402) Available AUTH mechanisms: LOGIN(builtin) PLAIN(builtin) Sep 12 13:19:19 2023 (1402) Peer: ('127.0.0.1', 54328) Sep 12 13:19:19 2023 (1402) ('127.0.0.1', 54328) handling connection Sep 12 13:19:19 2023 (1402) ('127.0.0.1', 54328) Data: b'LHLO lists.mydomain.com' Sep 12 13:19:19 2023 (1402) ('127.0.0.1', 54328) Data: b'MAIL FROM:<oanderson(a)mydomain.com>' Sep 12 13:19:19 2023 (1402) ('127.0.0.1', 54328) sender: oanderson(a)mydomain.com Sep 12 13:19:19 2023 (1402) ('127.0.0.1', 54328) Data: b'RCPT TO:<graduates(a)lists.mydomain.com>' Sep 12 13:19:19 2023 (1402) ('127.0.0.1', 54328) recip: graduates(a)lists.mydomain.com Sep 12 13:19:19 2023 (1402) ('127.0.0.1', 54328) Data: b'RCPT TO:<undergraduates(a)lists.mydomain.com>' Sep 12 13:19:19 2023 (1402) ('127.0.0.1', 54328) recip: undergraduates(a)lists.mydomain.com Sep 12 13:19:19 2023 (1402) ('127.0.0.1', 54328) Data: b'DATA' Sep 12 13:19:20 2023 (1402) ('127.0.0.1', 54328) Data: b'QUIT' Sep 12 13:19:20 2023 (1402) ('127.0.0.1', 54328) connection lost Sep 12 13:19:20 2023 (1402) Connection lost during _handle_client() Sep 12 13:19:22 2023 (1405) <169454636036.1401.8937840345817588576(a)lists.mydomain.com> smtp to graduates(a)lists.mydomain.com for 1 recips, completed in 0.0059452056884765625 seconds Sep 12 13:19:22 2023 (1405) <169454636036.1401.8937840345817588576(a)lists.mydomain.com> post to graduates(a)lists.mydomain.com from graduates-bounces(a)lists.mydomain.com, 1152 bytes Sep 12 13:19:22 2023 (1405) <169454636048.1401.2318933518942482920(a)lists.mydomain.com> smtp to undergraduates(a)lists.mydomain.com for 1 recips, completed in 0.005008220672607422 seconds Sep 12 13:19:22 2023 (1405) <169454636048.1401.2318933518942482920(a)lists.mydomain.com> post to undergraduates(a)lists.mydomain.com from undergraduates-bounces(a)lists.mydomain.com, 1251 bytes Sep 12 15:25:29 2023 (1402) Available AUTH mechanisms: LOGIN(builtin) PLAIN(builtin) Sep 12 15:25:29 2023 (1402) Peer: ('127.0.0.1', 44946) Sep 12 15:25:29 2023 (1402) ('127.0.0.1', 44946) handling connection Sep 12 15:25:29 2023 (1402) ('127.0.0.1', 44946) Data: b'LHLO lists.mydomain.com' Sep 12 15:25:29 2023 (1402) ('127.0.0.1', 44946) Data: b'MAIL FROM:<oanderson(a)mydomain.com>' Sep 12 15:25:29 2023 (1402) ('127.0.0.1', 44946) sender: oanderson(a)mydomain.com Sep 12 15:25:29 2023 (1402) ('127.0.0.1', 44946) Data: b'RCPT TO:<undergraduates(a)lists.mydomain.com>' Sep 12 15:25:29 2023 (1402) ('127.0.0.1', 44946) recip: undergraduates(a)lists.mydomain.com Sep 12 15:25:29 2023 (1402) ('127.0.0.1', 44946) Data: b'DATA' Sep 12 15:25:29 2023 (1402) ('127.0.0.1', 44946) Data: b'QUIT' Sep 12 15:25:29 2023 (1402) ('127.0.0.1', 44946) connection lost Sep 12 15:25:29 2023 (1402) Connection lost during _handle_client() Sep 12 15:25:30 2023 (1405) <169455392982.1401.10957221749647131956(a)lists.mydomain.com> smtp to undergraduates(a)lists.mydomain.com for 1 recips, completed in 0.006732940673828125 seconds Sep 12 15:25:30 2023 (1405) <169455392982.1401.10957221749647131956(a)lists.mydomain.com> post to undergraduates(a)lists.mydomain.com from undergraduates-bounces(a)lists.mydomain.com, 1237 bytes Sep 13 08:00:04 2023 (1405) <169461360294.3599633.12410089636004689205(a)lists.mydomain.com> smtp to graduates(a)lists.mydomain.com for 4 recips, completed in 0.027216196060180664 seconds Sep 13 08:00:04 2023 (1405) <169461360294.3599633.12410089636004689205(a)lists.mydomain.com> post to graduates(a)lists.mydomain.com from systemadmins(a)mydomain.com, 1079 bytes Sep 13 08:00:04 2023 (1405) <169461360298.3599633.9616667478508973418(a)lists.mydomain.com> smtp to undergraduates(a)lists.mydomain.com for 4 recips, completed in 0.00615382194519043 seconds Sep 13 08:00:04 2023 (1405) <169461360298.3599633.9616667478508973418(a)lists.mydomain.com> post to undergraduates(a)lists.mydomain.com from systemadmins(a)mydomain.com, 1377 bytes Sep 13 08:37:09 2023 (1405) <BYAPR04MB5813FE78DC3323A0822D9FE4DBF1A(a)BYAPR04MB5813.namprd04.prod.outlook.com> smtp to graduates(a)lists.mydomain.com for 4 recips, completed in 0.438995361328125 seconds Sep 13 08:37:09 2023 (1405) <BYAPR04MB5813FE78DC3323A0822D9FE4DBF1A(a)BYAPR04MB5813.namprd04.prod.outlook.com> post to graduates(a)lists.mydomain.com from oanderson(a)mydomain.com, 1787833 bytes Sep 13 08:37:37 2023 (1405) <BYAPR04MB5813FE78DC3323A0822D9FE4DBF1A(a)BYAPR04MB5813.namprd04.prod.outlook.com> smtp to undergraduates(a)lists.mydomain.com for 4 recips, completed in 0.41765809059143066 seconds Sep 13 08:37:37 2023 (1405) <BYAPR04MB5813FE78DC3323A0822D9FE4DBF1A(a)BYAPR04MB5813.namprd04.prod.outlook.com> post to undergraduates(a)lists.mydomain.com from oanderson(a)mydomain.com, 1787833 bytes Sep 13 08:37:37 2023 (1405) <BYAPR04MB581366BC29E904B4A7E7EFCCDBF1A(a)BYAPR04MB5813.namprd04.prod.outlook.com> smtp to undergraduates(a)lists.mydomain.com for 4 recips, completed in 0.05196428298950195 seconds Sep 13 08:37:37 2023 (1405) <BYAPR04MB581366BC29E904B4A7E7EFCCDBF1A(a)BYAPR04MB5813.namprd04.prod.outlook.com> post to undergraduates(a)lists.mydomain.com from oanderson(a)mydomain.com, 22280 bytes Sep 14 11:13:14 2023 (1402) Available AUTH mechanisms: LOGIN(builtin) PLAIN(builtin) Sep 14 11:13:14 2023 (1402) Peer: ('127.0.0.1', 46146) Sep 14 11:13:14 2023 (1402) ('127.0.0.1', 46146) handling connection Sep 14 11:13:14 2023 (1402) ('127.0.0.1', 46146) Data: b'LHLO lists.mydomain.com' Sep 14 11:13:14 2023 (1402) ('127.0.0.1', 46146) Data: b'MAIL FROM:<informationservices(a)mydomain.com>' Sep 14 11:13:14 2023 (1402) ('127.0.0.1', 46146) sender: informationservices(a)mydomain.com Sep 14 11:13:14 2023 (1402) ('127.0.0.1', 46146) Data: b'RCPT TO:<undergraduates(a)lists.mydomain.com>' Sep 14 11:13:14 2023 (1402) ('127.0.0.1', 46146) recip: undergraduates(a)lists.mydomain.com Sep 14 11:13:14 2023 (1402) ('127.0.0.1', 46146) Data: b'DATA' Sep 14 11:13:14 2023 (1402) ('127.0.0.1', 46146) Data: b'QUIT' Sep 14 11:13:14 2023 (1402) ('127.0.0.1', 46146) connection lost Sep 14 11:13:14 2023 (1402) Connection lost during _handle_client() Sep 14 11:13:16 2023 (1405) <169471159483.1401.16856017446433914677(a)lists.mydomain.com> smtp to undergraduates(a)lists.mydomain.com for 1 recips, completed in 0.005692005157470703 seconds Sep 14 11:13:16 2023 (1405) <169471159483.1401.16856017446433914677(a)lists.mydomain.com> post to undergraduates(a)lists.mydomain.com from undergraduates-bounces(a)lists.mydomain.com, 1210 bytes Sep 14 11:15:53 2023 (1405) <SJ0PR04MB85671FB097F25CF9F4874740BFF7A(a)SJ0PR04MB8567.namprd04.prod.outlook.com> smtp to undergraduates(a)lists.mydomain.com for 4 recips, completed in 0.08924412727355957 seconds Sep 14 11:15:53 2023 (1405) <SJ0PR04MB85671FB097F25CF9F4874740BFF7A(a)SJ0PR04MB8567.namprd04.prod.outlook.com> post to undergraduates(a)lists.mydomain.com from informationservices(a)mydomain.com, 22049 bytes Sep 14 14:34:11 2023 (1402) Available AUTH mechanisms: LOGIN(builtin) PLAIN(builtin) Sep 14 14:34:11 2023 (1402) Peer: ('127.0.0.1', 60848) Sep 14 14:34:11 2023 (1402) ('127.0.0.1', 60848) handling connection Sep 14 14:34:11 2023 (1402) ('127.0.0.1', 60848) Data: b'LHLO lists.mydomain.com' Sep 14 14:34:11 2023 (1402) ('127.0.0.1', 60848) Data: b'MAIL FROM:<informationservices(a)mydomain.com>' Sep 14 14:34:11 2023 (1402) ('127.0.0.1', 60848) sender: informationservices(a)mydomain.com Sep 14 14:34:11 2023 (1402) ('127.0.0.1', 60848) Data: b'RCPT TO:<ug(a)lists.mydomain.com>' Sep 14 14:34:11 2023 (1402) ('127.0.0.1', 60848) recip: ug(a)lists.mydomain.com Sep 14 14:34:11 2023 (1402) ('127.0.0.1', 60848) Data: b'DATA' Sep 14 14:34:11 2023 (1402) ('127.0.0.1', 60848) Data: b'QUIT' Sep 14 14:34:11 2023 (1402) ('127.0.0.1', 60848) connection lost Sep 14 14:34:11 2023 (1402) Connection lost during _handle_client() Sep 14 14:34:14 2023 (1405) <169472365226.1401.465743651937418379(a)lists.mydomain.com> smtp to ug(a)lists.mydomain.com for 1 recips, completed in 0.00711822509765625 seconds Sep 14 14:34:14 2023 (1405) <169472365226.1401.465743651937418379(a)lists.mydomain.com> post to ug(a)lists.mydomain.com from ug-bounces(a)lists.mydomain.com, 1153 bytes Sep 14 14:34:33 2023 (1405) <SJ0PR04MB856797E91A59977ABCF9BAB7BFF7A(a)SJ0PR04MB8567.namprd04.prod.outlook.com> smtp to ug(a)lists.mydomain.com for 4 recips, completed in 0.054645538330078125 seconds Sep 14 14:34:33 2023 (1405) <SJ0PR04MB856797E91A59977ABCF9BAB7BFF7A(a)SJ0PR04MB8567.namprd04.prod.outlook.com> post to ug(a)lists.mydomain.com from informationservices(a)mydomain.com, 21976 bytes Sep 14 16:36:56 2023 (1305) Available AUTH mechanisms: LOGIN(builtin) PLAIN(builtin) Sep 14 16:36:56 2023 (1305) Peer: ('127.0.0.1', 54478) Sep 14 16:36:56 2023 (1305) ('127.0.0.1', 54478) handling connection Sep 14 16:36:56 2023 (1305) ('127.0.0.1', 54478) Data: b'LHLO lists.mydomain.com' Sep 14 16:36:56 2023 (1305) ('127.0.0.1', 54478) Data: b'MAIL FROM:<rpassalacqua(a)mydomain.com>' Sep 14 16:36:56 2023 (1305) ('127.0.0.1', 54478) sender: rpassalacqua(a)mydomain.com Sep 14 16:36:56 2023 (1305) ('127.0.0.1', 54478) Data: b'RCPT TO:<test(a)lists.mydomain.com>' Sep 14 16:36:56 2023 (1305) ('127.0.0.1', 54478) recip: test(a)lists.mydomain.com Sep 14 16:36:56 2023 (1305) ('127.0.0.1', 54478) Data: b'DATA' Sep 14 16:36:56 2023 (1305) ('127.0.0.1', 54478) Data: b'QUIT' Sep 14 16:36:56 2023 (1305) ('127.0.0.1', 54478) connection lost Sep 14 16:36:56 2023 (1305) Connection lost during _handle_client() Sep 14 16:36:58 2023 (1307) <169473101747.1304.15129450588472089900(a)lists.mydomain.com> smtp to test(a)lists.mydomain.com for 1 recips, completed in 0.0060198307037353516 seconds Sep 14 16:36:58 2023 (1307) <169473101747.1304.15129450588472089900(a)lists.mydomain.com> post to test(a)lists.mydomain.com from test-bounces(a)lists.mydomain.com, 1067 bytes Sep 14 16:38:48 2023 (1307) <BY5PR04MB71216AD8880847E842960CB6B3F7A(a)BY5PR04MB7121.namprd04.prod.outlook.com> smtp to test(a)lists.mydomain.com for 3 recips, completed in 0.05848550796508789 seconds Sep 14 16:38:48 2023 (1307) <BY5PR04MB71216AD8880847E842960CB6B3F7A(a)BY5PR04MB7121.namprd04.prod.outlook.com> post to test(a)lists.mydomain.com from rpassalacqua(a)mydomain.com, 8680 bytes Sep 14 17:39:38 2023 (4281) Available AUTH mechanisms: LOGIN(builtin) PLAIN(builtin) Sep 14 17:39:38 2023 (4281) Peer: ('127.0.0.1', 38814) Sep 14 17:39:38 2023 (4281) ('127.0.0.1', 38814) handling connection Sep 14 17:39:38 2023 (4281) ('127.0.0.1', 38814) Data: b'LHLO lists.mydomain.com' Sep 14 17:39:38 2023 (4281) ('127.0.0.1', 38814) Data: b'MAIL FROM:<rpassalacqua(a)mydomain.com>' Sep 14 17:39:38 2023 (4281) ('127.0.0.1', 38814) sender: rpassalacqua(a)mydomain.com Sep 14 17:39:38 2023 (4281) ('127.0.0.1', 38814) Data: b'RCPT TO:<test(a)lists.mydomain.com>' Sep 14 17:39:38 2023 (4281) ('127.0.0.1', 38814) recip: test(a)lists.mydomain.com Sep 14 17:39:38 2023 (4281) ('127.0.0.1', 38814) Data: b'DATA' Sep 14 17:39:38 2023 (4281) ('127.0.0.1', 38814) Data: b'QUIT' Sep 14 17:39:38 2023 (4281) ('127.0.0.1', 38814) connection lost Sep 14 17:39:38 2023 (4281) Connection lost during _handle_client() Sep 14 17:39:40 2023 (4283) <169473477870.4280.4174702240504737654(a)lists.mydomain.com> smtp to test(a)lists.mydomain.com for 1 recips, completed in 0.005831241607666016 seconds Sep 14 17:39:40 2023 (4283) <169473477870.4280.4174702240504737654(a)lists.mydomain.com> post to test(a)lists.mydomain.com from test-bounces(a)lists.mydomain.com, 1085 bytes Sep 14 17:42:59 2023 (4283) <BY5PR04MB71215FF54B65F1D74C4567C0B3F7A(a)BY5PR04MB7121.namprd04.prod.outlook.com> smtp to test(a)lists.mydomain.com for 3 recips, completed in 0.06569862365722656 seconds Sep 14 17:42:59 2023 (4283) <BY5PR04MB71215FF54B65F1D74C4567C0B3F7A(a)BY5PR04MB7121.namprd04.prod.outlook.com> post to test(a)lists.mydomain.com from rpassalacqua(a)mydomain.com, 32685 bytes Sep 14 18:03:41 2023 (4281) Available AUTH mechanisms: LOGIN(builtin) PLAIN(builtin) Sep 14 18:03:41 2023 (4281) Peer: ('127.0.0.1', 42054) Sep 14 18:03:41 2023 (4281) ('127.0.0.1', 42054) handling connection Sep 14 18:03:41 2023 (4281) ('127.0.0.1', 42054) Data: b'LHLO lists.mydomain.com' Sep 14 18:03:41 2023 (4281) ('127.0.0.1', 42054) Data: b'MAIL FROM:<rpassalacqua(a)mydomain.com>' Sep 14 18:03:41 2023 (4281) ('127.0.0.1', 42054) sender: rpassalacqua(a)mydomain.com Sep 14 18:03:41 2023 (4281) ('127.0.0.1', 42054) Data: b'RCPT TO:<test(a)lists.mydomain.com>' Sep 14 18:03:41 2023 (4281) ('127.0.0.1', 42054) recip: test(a)lists.mydomain.com Sep 14 18:03:41 2023 (4281) ('127.0.0.1', 42054) Data: b'DATA' Sep 14 18:03:41 2023 (4281) ('127.0.0.1', 42054) Data: b'QUIT' Sep 14 18:03:41 2023 (4281) ('127.0.0.1', 42054) connection lost Sep 14 18:03:41 2023 (4281) Connection lost during _handle_client() Sep 14 18:03:42 2023 (4283) <169473622130.4280.7069249432915457814(a)lists.mydomain.com> smtp to test(a)lists.mydomain.com for 1 recips, completed in 0.006022214889526367 seconds Sep 14 18:03:42 2023 (4283) <169473622130.4280.7069249432915457814(a)lists.mydomain.com> post to test(a)lists.mydomain.com from test-bounces(a)lists.mydomain.com, 1065 bytes Sep 14 18:07:57 2023 (4281) Available AUTH mechanisms: LOGIN(builtin) PLAIN(builtin) Sep 14 18:07:57 2023 (4281) Peer: ('127.0.0.1', 50610) Sep 14 18:07:57 2023 (4281) ('127.0.0.1', 50610) handling connection Sep 14 18:07:57 2023 (4281) ('127.0.0.1', 50610) Data: b'LHLO lists.mydomain.com' Sep 14 18:07:57 2023 (4281) ('127.0.0.1', 50610) Data: b'MAIL FROM:<rpassalacqua(a)mydomain.com>' Sep 14 18:07:57 2023 (4281) ('127.0.0.1', 50610) sender: rpassalacqua(a)mydomain.com Sep 14 18:07:57 2023 (4281) ('127.0.0.1', 50610) Data: b'RCPT TO:<test(a)lists.mydomain.com>' Sep 14 18:07:57 2023 (4281) ('127.0.0.1', 50610) recip: test(a)lists.mydomain.com Sep 14 18:07:57 2023 (4281) ('127.0.0.1', 50610) Data: b'DATA' Sep 14 18:07:57 2023 (4281) ('127.0.0.1', 50610) Data: b'QUIT' Sep 14 18:07:57 2023 (4281) ('127.0.0.1', 50610) connection lost Sep 14 18:07:57 2023 (4281) Connection lost during _handle_client() Sep 14 18:07:58 2023 (4283) <169473647867.4280.14938940229014329856(a)lists.mydomain.com> smtp to test(a)lists.mydomain.com for 1 recips, completed in 0.0055654048919677734 seconds Sep 14 18:07:58 2023 (4283) <169473647867.4280.14938940229014329856(a)lists.mydomain.com> post to test(a)lists.mydomain.com from test-bounces(a)lists.mydomain.com, 1098 bytes Sep 14 18:10:17 2023 (4283) <BY5PR04MB71217ABD906F6FE7AFD2B4B9B3F7A(a)BY5PR04MB7121.namprd04.prod.outlook.com> smtp to test(a)lists.mydomain.com for 3 recips, completed in 0.06551766395568848 seconds Sep 14 18:10:17 2023 (4283) <BY5PR04MB71217ABD906F6FE7AFD2B4B9B3F7A(a)BY5PR04MB7121.namprd04.prod.outlook.com> post to test(a)lists.mydomain.com from rpassalacqua(a)mydomain.com, 8688 bytes Sep 14 18:10:20 2023 (4283) <BY5PR04MB7121FAB23617A4597304E327B3F6A(a)BY5PR04MB7121.namprd04.prod.outlook.com> smtp to test(a)lists.mydomain.com for 3 recips, completed in 0.03918266296386719 seconds Sep 14 18:10:20 2023 (4283) <BY5PR04MB7121FAB23617A4597304E327B3F6A(a)BY5PR04MB7121.namprd04.prod.outlook.com> post to test(a)lists.mydomain.com from rpassalacqua(a)mydomain.com, 8880 bytes Sep 15 09:16:03 2023 (4281) Available AUTH mechanisms: LOGIN(builtin) PLAIN(builtin) Sep 15 09:16:03 2023 (4281) Peer: ('127.0.0.1', 38006) Sep 15 09:16:03 2023 (4281) ('127.0.0.1', 38006) handling connection Sep 15 09:16:03 2023 (4281) ('127.0.0.1', 38006) Data: b'LHLO lists.mydomain.com' Sep 15 09:16:03 2023 (4281) ('127.0.0.1', 38006) Data: b'MAIL FROM:<rpassalacqua(a)mydomain.com>' Sep 15 09:16:03 2023 (4281) ('127.0.0.1', 38006) sender: rpassalacqua(a)mydomain.com Sep 15 09:16:03 2023 (4281) ('127.0.0.1', 38006) Data: b'RCPT TO:<test(a)lists.mydomain.com>' Sep 15 09:16:03 2023 (4281) ('127.0.0.1', 38006) recip: test(a)lists.mydomain.com Sep 15 09:16:03 2023 (4281) ('127.0.0.1', 38006) Data: b'DATA' Sep 15 09:16:03 2023 (4281) ('127.0.0.1', 38006) Data: b'QUIT' Sep 15 09:16:03 2023 (4281) ('127.0.0.1', 38006) connection lost Sep 15 09:16:03 2023 (4281) Connection lost during _handle_client() Sep 15 09:16:05 2023 (4283) <169479096385.4280.8198285364938859931(a)lists.mydomain.com> smtp to test(a)lists.mydomain.com for 1 recips, completed in 0.005726337432861328 seconds Sep 15 09:16:05 2023 (4283) <169479096385.4280.8198285364938859931(a)lists.mydomain.com> post to test(a)lists.mydomain.com from test-bounces(a)lists.mydomain.com, 1069 bytes Sep 15 09:16:54 2023 (4283) <BY5PR04MB71219485E3D6DBF7FFEF45E5B3F6A(a)BY5PR04MB7121.namprd04.prod.outlook.com> smtp to test(a)lists.mydomain.com for 3 recips, completed in 0.04341244697570801 seconds Sep 15 09:16:54 2023 (4283) <BY5PR04MB71219485E3D6DBF7FFEF45E5B3F6A(a)BY5PR04MB7121.namprd04.prod.outlook.com> post to test(a)lists.mydomain.com from rpassalacqua(a)mydomain.com, 9719 bytes Sep 15 11:12:26 2023 (4281) Available AUTH mechanisms: LOGIN(builtin) PLAIN(builtin) Sep 15 11:12:26 2023 (4281) Peer: ('127.0.0.1', 59844) Sep 15 11:12:26 2023 (4281) ('127.0.0.1', 59844) handling connection Sep 15 11:12:26 2023 (4281) ('127.0.0.1', 59844) Data: b'LHLO lists.mydomain.com' Sep 15 11:12:26 2023 (4281) ('127.0.0.1', 59844) Data: b'MAIL FROM:<rpassalacqua(a)mydomain.com>' Sep 15 11:12:26 2023 (4281) ('127.0.0.1', 59844) sender: rpassalacqua(a)mydomain.com Sep 15 11:12:26 2023 (4281) ('127.0.0.1', 59844) Data: b'RCPT TO:<test(a)lists.mydomain.com>' Sep 15 11:12:26 2023 (4281) ('127.0.0.1', 59844) recip: test(a)lists.mydomain.com Sep 15 11:12:26 2023 (4281) ('127.0.0.1', 59844) Data: b'DATA' Sep 15 11:12:26 2023 (4281) ('127.0.0.1', 59844) Data: b'QUIT' Sep 15 11:12:26 2023 (4281) ('127.0.0.1', 59844) connection lost Sep 15 11:12:26 2023 (4281) Connection lost during _handle_client() Sep 15 11:12:28 2023 (4283) <169479794718.4280.8209850830279553803(a)lists.mydomain.com> smtp to test(a)lists.mydomain.com for 1 recips, completed in 0.005163669586181641 seconds Sep 15 11:12:28 2023 (4283) <169479794718.4280.8209850830279553803(a)lists.mydomain.com> post to test(a)lists.mydomain.com from test-bounces(a)lists.mydomain.com, 1098 bytes Sep 15 11:12:49 2023 (4283) <BY5PR04MB71214E309721B3CC9F3072F9B3F6A(a)BY5PR04MB7121.namprd04.prod.outlook.com> smtp to test(a)lists.mydomain.com for 3 recips, completed in 0.0408024787902832 seconds Sep 15 11:12:49 2023 (4283) <BY5PR04MB71214E309721B3CC9F3072F9B3F6A(a)BY5PR04MB7121.namprd04.prod.outlook.com> post to test(a)lists.mydomain.com from rpassalacqua(a)mydomain.com, 8817 bytes Sep 18 16:51:02 2023 (1286) Available AUTH mechanisms: LOGIN(builtin) PLAIN(builtin) Sep 18 16:51:02 2023 (1286) Peer: ('127.0.0.1', 56034) Sep 18 16:51:02 2023 (1286) ('127.0.0.1', 56034) handling connection Sep 18 16:51:02 2023 (1286) ('127.0.0.1', 56034) Data: b'LHLO lists.mydomain.com' Sep 18 16:51:02 2023 (1286) ('127.0.0.1', 56034) Data: b'MAIL FROM:<rpassalacqua(a)mydomain.com>' Sep 18 16:51:02 2023 (1286) ('127.0.0.1', 56034) sender: rpassalacqua(a)mydomain.com Sep 18 16:51:02 2023 (1286) ('127.0.0.1', 56034) Data: b'RCPT TO:<test(a)lists.mydomain.com>' Sep 18 16:51:02 2023 (1286) ('127.0.0.1', 56034) recip: test(a)lists.mydomain.com Sep 18 16:51:02 2023 (1286) ('127.0.0.1', 56034) Data: b'DATA' Sep 18 16:51:02 2023 (1286) ('127.0.0.1', 56034) Data: b'QUIT' Sep 18 16:51:02 2023 (1286) ('127.0.0.1', 56034) connection lost Sep 18 16:51:02 2023 (1286) Connection lost during _handle_client() Sep 18 16:51:03 2023 (1288) <169507746274.1285.2209553928985210953(a)lists.mydomain.com> smtp to test(a)lists.mydomain.com for 1 recips, completed in 0.005767107009887695 seconds Sep 18 16:51:03 2023 (1288) <169507746274.1285.2209553928985210953(a)lists.mydomain.com> post to test(a)lists.mydomain.com from test-bounces(a)lists.mydomain.com, 1075 bytes Sep 18 16:58:09 2023 (1288) <BY5PR04MB7121D7152C07846F0FCFB100B3FBA(a)BY5PR04MB7121.namprd04.prod.outlook.com> smtp to test(a)lists.mydomain.com for 3 recips, completed in 0.07815432548522949 seconds Sep 18 16:58:09 2023 (1288) <BY5PR04MB7121D7152C07846F0FCFB100B3FBA(a)BY5PR04MB7121.namprd04.prod.outlook.com> post to test(a)lists.mydomain.com from rpassalacqua(a)mydomain.com, 8756 bytes Sep 19 08:49:33 2023 (1286) Available AUTH mechanisms: LOGIN(builtin) PLAIN(builtin) Sep 19 08:49:33 2023 (1286) Peer: ('127.0.0.1', 59616) Sep 19 08:49:33 2023 (1286) ('127.0.0.1', 59616) handling connection Sep 19 08:49:33 2023 (1286) ('127.0.0.1', 59616) Data: b'LHLO lists.mydomain.com' Sep 19 08:49:33 2023 (1286) ('127.0.0.1', 59616) Data: b'MAIL FROM:<rpassalacqua(a)mydomain.com>' Sep 19 08:49:33 2023 (1286) ('127.0.0.1', 59616) sender: rpassalacqua(a)mydomain.com Sep 19 08:49:33 2023 (1286) ('127.0.0.1', 59616) Data: b'RCPT TO:<test(a)lists.mydomain.com>' Sep 19 08:49:33 2023 (1286) ('127.0.0.1', 59616) recip: test(a)lists.mydomain.com Sep 19 08:49:33 2023 (1286) ('127.0.0.1', 59616) Data: b'DATA' Sep 19 08:49:33 2023 (1286) ('127.0.0.1', 59616) Data: b'QUIT' Sep 19 08:49:33 2023 (1286) ('127.0.0.1', 59616) connection lost Sep 19 08:49:33 2023 (1286) Connection lost during _handle_client() Sep 19 08:49:36 2023 (1288) <169513497462.1285.8696625500767060363(a)lists.mydomain.com> smtp to test(a)lists.mydomain.com for 1 recips, completed in 0.007772684097290039 seconds Sep 19 08:49:36 2023 (1288) <169513497462.1285.8696625500767060363(a)lists.mydomain.com> post to test(a)lists.mydomain.com from test-bounces(a)lists.mydomain.com, 1076 bytes Sep 19 08:50:23 2023 (1288) <BY5PR04MB7121991E697D92F88D586AFFB3FAA(a)BY5PR04MB7121.namprd04.prod.outlook.com> smtp to test(a)lists.mydomain.com for 3 recips, completed in 0.04478025436401367 seconds Sep 19 08:50:23 2023 (1288) <BY5PR04MB7121991E697D92F88D586AFFB3FAA(a)BY5PR04MB7121.namprd04.prod.outlook.com> post to test(a)lists.mydomain.com from rpassalacqua(a)mydomain.com, 8828 bytes

3 4

Importing mbox files into archive defect with lines with From
by andrew.bernard＠gmail.com Sept. 19, 2023

Sept. 19, 2023

A curious problem, but seems to be well defined. I am importing mbox format files with 25 years worth of archives in 250 files from a Listserv list into hyperkitty. All is going swimmingly, except I get lots of partial emails with sender of None put into the current month, with text that has clearly been truncated. As I look at each one, I see that the line in the imported text is immediately after a line starting with 'From'. Clearly, 'From:' is an RCS-82 header, but 'From ' is not, and yet there is much evidence here that this is messing up the import. Is this a known bug? If not, how do I report it?

8 15