redirecting -bounces replies
Greetings,
Is it possible to redirect the -bounces alias of a specific list so that it also goes to a person, in addition to the normal bounces processing for that list?
In Mailman2, I know that I could do that by modifying the aliases table.
I've been poking around in Mailman3, but haven't managed to figure out which container I need to be looking at. And rather than keep spinning, I figured that I'd ask the hive mind, since I'm sure one of you can quickly point me to the correct location.
Thanks!
-p
Pat Hirayama Pronouns: he/him/his Systems Engineer IT | Systems Engineering - Infrastructure Fred Hutch Cancer Center O 206.667.4856
phirayam@fredhutch.org<mailto:phirayam@fredhutch.org>
If you are using Postfix with mysql you could use an entry in the virtual_aliases table by doing something like:
MariaDB [mailserver]> REPLACE INTO mailserver.virtual_aliases (id,domain_id,source,destination) VALUES ('N', '1', 'ListNameHere-bounces@example.org', 'person@example.org'); Query OK, 1 row affected (0.010 sec)
where the value 'N' is one larger than the largest id entry already present in said table ....
Cheers, Nelson
On 10/31/24 19:17, Hirayama, Pat wrote:
Greetings,
Is it possible to redirect the -bounces alias of a specific list so that it also goes to a person, in addition to the normal bounces processing for that list?
In Mailman2, I know that I could do that by modifying the aliases table.
I've been poking around in Mailman3, but haven't managed to figure out which container I need to be looking at. And rather than keep spinning, I figured that I'd ask the hive mind, since I'm sure one of you can quickly point me to the correct location.
Thanks!
-p
Pat Hirayama Pronouns: he/him/his Systems Engineer IT | Systems Engineering - Infrastructure Fred Hutch Cancer Center O 206.667.4856
phirayam@fredhutch.org<mailto:phirayam@fredhutch.org>
Mailman-users mailing list --mailman-users@mailman3.org To unsubscribe send an email tomailman-users-leave@mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ Archived at:https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message/...
This message sent tojustfixit@marilynstrother.com
On 10/31/24 16:17, Hirayama, Pat wrote:
Is it possible to redirect the -bounces alias of a specific list so that it also goes to a person, in addition to the normal bounces processing for that list?
In Mailman2, I know that I could do that by modifying the aliases table.
You can do the same in MM3 if you want to just deliver to a person and not to normal bounce processing, but if you want to do both, and your MTA is Postfix, you would need to add and alias domain to your lists domain and configure Postfix according to https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/mta.ht....
Then for example if your list domain is example.com and its alias domain
is x.example.com, you could modify one line in the postfix_vmap file for
the listname mappings from
listname-bounces@example.com listname-bounces@x.example.com
to
listname-bounces@example.com listname-bounces@x.example.com,
person@example.com
and then run postmap on the file. The problem is any time you create or
delete a list or run mailman aliases or run mailman start with the
--generate-alias-file option, the file is regenerated and you will have
to edit it again.
To avoid that issue, you can create a separate vmap file containing only the
listname-bounces@example.com listname-bounces@x.example.com,
person@example.com
entry and then add that file to virtual_alias_maps in Postfix main.cf, being sure to add it ahead of the postfix_vmap entry.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
Instead of what I wrote at https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message/... you might consider whether setting the list's Notify owner on bounce increment to Yes and Forward unrecognized bounces to List or Site admins might do what you want.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
Thanks, Mark.
I (finally) started working on this ... and in trying to implement your suggestion — ran into a problem, I think.
The current postfix_vmap has entries like:
list-bounces@lists.domain.info lmtp:[mailman-core]:24
So, when I try adding entries to a separate vmap file, like:
list-bounces@lists.domain.info lmtp:[mailman-core]:24, user@gmail.com
It only goes through normal bounce processing.
If I do:
list-bounces@lists.domain.info user@gmail.com, lmtp:[mailman-core]:24
Then it goes to the gmail address, and no bounce processing happens.
I'm thinking that I can't combine two methods of delivery (LMTP + email address). Do you know if that is correct?
Thanks,
-p
Pat Hirayama Pronouns: he/him/his Systems Engineer IT | Systems Engineering Fred Hutchinson Cancer Center O 206.667.4856 phirayam@fredhutch.org
From: Mark Sapiro <mark@msapiro.net> Sent: Thursday, October 31, 2024 21:18 To: mailman-users@mailman3.org <mailman-users@mailman3.org> Subject: [MM3-users] Re: redirecting -bounces replies
CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe.
On 10/31/24 16:17, Hirayama, Pat wrote:
Is it possible to redirect the -bounces alias of a specific list so that it also goes to a person, in addition to the normal bounces processing for that list?
In Mailman2, I know that I could do that by modifying the aliases table.
You can do the same in MM3 if you want to just deliver to a person and not to normal bounce processing, but if you want to do both, and your MTA is Postfix, you would need to add and alias domain to your lists domain and configure Postfix according to https://urldefense.com/v3/__https://docs.mailman3.org/projects/mailman/en/la... .
Then for example if your list domain is example.com and its alias domain
is x.example.com, you could modify one line in the postfix_vmap file for
the listname mappings from
listname-bounces@example.com listname-bounces@x.example.com
to
listname-bounces@example.com listname-bounces@x.example.com,
person@example.com
and then run postmap on the file. The problem is any time you create or
delete a list or run mailman aliases or run mailman start with the
--generate-alias-file option, the file is regenerated and you will have
to edit it again.
To avoid that issue, you can create a separate vmap file containing only the
listname-bounces@example.com listname-bounces@x.example.com,
person@example.com
entry and then add that file to virtual_alias_maps in Postfix main.cf, being sure to add it ahead of the postfix_vmap entry.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
Mailman-users mailing list -- mailman-users@mailman3.org To unsubscribe send an email to mailman-users-leave@mailman3.org https://urldefense.com/v3/__https://lists.mailman3.org/mailman3/lists/mailma... Archived at: https://urldefense.com/v3/__https://lists.mailman3.org/archives/list/mailman...
This message sent to phirayam@fredhutch.org
Hirayama, Pat writes:
So, when I try adding entries to a separate vmap file, like:
list-bounces@lists.domain.info lmtp:[mailman-core]:24, user@gmail.com
It only goes through normal bounce processing.
IIRC the usual configuration uses the virtual map as a transport file. The transport file format allows only one result, which must be a transport of the form protocol:host:port.
I'm surprised that either of those works at all, as both are syntax errors. (Unless possibly 'lmtp:[mailman-core]:24' is being interpreted as a local but undeliverable address? I forget whether colons and square brackets are allowed in local-parts.)
What are your Postfix logs saying about all this mischief?
I'm thinking that I can't combine two methods of delivery (LMTP + email address). Do you know if that is correct?
It's not impossible, I think, but it's probably both tricky and ugly. :^) You need one virtual alias mapping'list-bounces@lists.domain.info' to 'user@gmail.com' and another address (probably with a "fake" domain such as 'bounces.lists.domain.info'), and the latter address gets mapped in a transport to lmtp:[mailman-core]:24.
-- GNU Mailman consultant (installation, migration, customization) Sirius Open Source https://www.siriusopensource.com/ Software systems consulting in Europe, North America, and Japan
On 6/25/25 10:53, Hirayama, Pat wrote:
Thanks, Mark.
I (finally) started working on this ... and in trying to implement your suggestion — ran into a problem, I think.
The current postfix_vmap has entries like:
list-bounces@lists.domain.info lmtp:[mailman-core]:24
This looks very strange. It should be something like
list-bounces@lists.domain.info list-bounces@alias.domain
where alias.domain is the configured alias domain for the mail host lists.domain.info.
So, when I try adding entries to a separate vmap file, like:
list-bounces@lists.domain.info lmtp:[mailman-core]:24, user@gmail.com
It only goes through normal bounce processing.
If I do:
list-bounces@lists.domain.info user@gmail.com, lmtp:[mailman-core]:24
Then it goes to the gmail address, and no bounce processing happens.
The issue here is the value lmtp:[mailman-core]:24 is completely
wrong. It should be an email address with a syntactically valid domain
name. The domain name isn't a real domain. It is only a name exposed to
Postorius in the postfix_vmap and postfix_lmtp files.
What do you have configured for the alias domain for the lists.domain.info domain? See https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/mta.ht...
If you have this properly configured, adding user@gmail.com in either order in postfix_vmap should work.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
Hi Mark,
Thank you for your reply.
I admit that I don't know Mailman 3 as well as I knew Mailman 2. And the 2 -> 3 upgrade was handled by someone else, who has since left the org. As near as I have been able to discern, Mailman 3 is running on a docker host with four containers running, with mailman, postfix, nginx and django-uswgi in separate containers.
% sudo docker ps CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES 1b4262f81b98 mailman-nginx:1.21.3 "/docker-entrypoint.…" 3 years ago Up 3 weeks 0.0.0.0:80->80/tcp, 0.0.0.0:443->443/tcp mailman-nginx a5e4fa75ccb3 mailman-postfix:3.5.10-r0 "postfix start-fg" 4 years ago Up 2 weeks 0.0.0.0:25->25/tcp mailman-postfix 7a358c807714 mailman-django-uwsgi:2.0.19.1 "uwsgi --ini uwsgi.i…" 4 years ago Up 3 weeks 8000/tcp mailman-django-uwsgi 9a917897da10 mailman-core:3.3.1 "master" 4 years ago Up 3 weeks 24/tcp, 8001/tcp mailman-core
When I look at main.cf inside mailman-postfix:
transport_maps = hash:/opt/mailman/var/data/postfix_lmtp local_recipient_maps = hash:/opt/mailman/var/data/postfix_lmtp relay_domains = hash:/opt/mailman/var/data/postfix_domains virtual_alias_maps = hash:/opt/mailman/var/data/postfix_vmap-exceptions, hash:/opt/mailman/var/data/postfix_vmap
When I look at the domains in mailman-core, I see:
- owner: cit-sys-engineering@fredhutch.org
show_domains() <Domain fhcrc.org> <Domain fredhutch.org> <Domain lists.fhcrc.org, , alias: lists.fredhutch.org> <Domain lists.hanc.info, , alias: >
When I look at /opt/mailman/var/data/postfix_domains inside the postfix container, that seems to match:
fredhutch.org fredhutch.org lists.fredhutch.org lists.fhcrc.org lists.hanc.info lists.hanc.info
Now, when I look at the entries for a test list on lists.fhcrc.org, postfix_vmap looks like:
pattest@lists.fhcrc.org pattest@lists.fredhutch.org pattest-bounces@lists.fhcrc.org pattest-bounces@lists.fredhutch.org pattest-confirm@lists.fhcrc.org pattest-confirm@lists.fredhutch.org pattest-join@lists.fhcrc.org pattest-join@lists.fredhutch.org pattest-leave@lists.fhcrc.org pattest-leave@lists.fredhutch.org pattest-owner@lists.fhcrc.org pattest-owner@lists.fredhutch.org pattest-request@lists.fhcrc.org pattest-request@lists.fredhutch.org pattest-subscribe@lists.fhcrc.org pattest-subscribe@lists.fredhutch.org pattest-unsubscribe@lists.fhcrc.org pattest-unsubscribe@lists.fredhutch.org
and postfix_lmtp looks like:
pattest@lists.fredhutch.org lmtp:[mailman-core]:24 pattest-bounces@lists.fredhutch.org lmtp:[mailman-core]:24 pattest-confirm@lists.fredhutch.org lmtp:[mailman-core]:24 pattest-join@lists.fredhutch.org lmtp:[mailman-core]:24 pattest-leave@lists.fredhutch.org lmtp:[mailman-core]:24 pattest-owner@lists.fredhutch.org lmtp:[mailman-core]:24 pattest-request@lists.fredhutch.org lmtp:[mailman-core]:24 pattest-subscribe@lists.fredhutch.org lmtp:[mailman-core]:24 pattest-unsubscribe@lists.fredhutch.org lmtp:[mailman-core]:24
But for a test list on lists.hanc.info (the lists that I want to modify the bounce processing for), there is nothing in postfix_vmap, but there are entries in postfix_lmtp:
phtest@lists.hanc.info lmtp:[mailman-core]:24 phtest-bounces@lists.hanc.info lmtp:[mailman-core]:24 phtest-confirm@lists.hanc.info lmtp:[mailman-core]:24 phtest-join@lists.hanc.info lmtp:[mailman-core]:24 phtest-leave@lists.hanc.info lmtp:[mailman-core]:24 phtest-owner@lists.hanc.info lmtp:[mailman-core]:24 phtest-request@lists.hanc.info lmtp:[mailman-core]:24 phtest-subscribe@lists.hanc.info lmtp:[mailman-core]:24 phtest-unsubscribe@lists.hanc.info lmtp:[mailman-core]:24
And in postfix_vmap-exceptions, I added:
phtest-bounces@lists.hanc.info lmtp:[mailman-core]:24, user@gmail.com
I tried the above with and without a comma, and moving the email address before the lmtp entry as well.
Everything else seems to be working — there are over 40k lmtp: entries in postfix_lmtp, and messages are being delivered. I sort of assumed that the lmtp:[mailman-core]:24 thing was a result of all this being dockerized....
Suggestions appreciated.
Thanks,
-p
Pat Hirayama Pronouns: he/him/his Systems Engineer IT | Systems Engineering Fred Hutchinson Cancer Center O 206.667.4856 phirayam@fredhutch.org
From: Mark Sapiro <mark@msapiro.net> Sent: Thursday, June 26, 2025 09:33 To: mailman-users@mailman3.org <mailman-users@mailman3.org> Subject: [MM3-users] Re: redirecting -bounces replies
CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe.
On 6/25/25 10:53, Hirayama, Pat wrote:
Thanks, Mark.
I (finally) started working on this ... and in trying to implement your suggestion — ran into a problem, I think.
The current postfix_vmap has entries like:
list-bounces@lists.domain.info lmtp:[mailman-core]:24
This looks very strange. It should be something like
list-bounces@lists.domain.info list-bounces@alias.domain
where alias.domain is the configured alias domain for the mail host lists.domain.info.
So, when I try adding entries to a separate vmap file, like:
list-bounces@lists.domain.info lmtp:[mailman-core]:24, user@gmail.com
It only goes through normal bounce processing.
If I do:
list-bounces@lists.domain.info user@gmail.com, lmtp:[mailman-core]:24
Then it goes to the gmail address, and no bounce processing happens.
The issue here is the value lmtp:[mailman-core]:24 is completely
wrong. It should be an email address with a syntactically valid domain
name. The domain name isn't a real domain. It is only a name exposed to
Postorius in the postfix_vmap and postfix_lmtp files.
What do you have configured for the alias domain for the lists.domain.info domain? See https://urldefense.com/v3/__https://docs.mailman3.org/projects/mailman/en/la...
If you have this properly configured, adding user@gmail.com in either order in postfix_vmap should work.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
Mailman-users mailing list -- mailman-users@mailman3.org To unsubscribe send an email to mailman-users-leave@mailman3.org https://urldefense.com/v3/__https://lists.mailman3.org/mailman3/lists/mailma... Archived at: https://urldefense.com/v3/__https://lists.mailman3.org/archives/list/mailman...
This message sent to phirayam@fredhutch.org
On 6/26/25 11:37, Hirayama, Pat wrote:
When I look at the domains in mailman-core, I see:
show_domains() <Domain fhcrc.org> <Domain fredhutch.org> <Domain lists.fhcrc.org, , alias: lists.fredhutch.org> <Domain lists.hanc.info, , alias: >
- owner: cit-sys-engineering@fredhutch.org
This is part of the problem. The alias domain for a list should not be a real domain. Apparently, someone set this up so that mail to lists in the lists.fhcrc.org domain would go to the corresponding list in the lists.fredhutch.org domain. I think that may actually work, but you need more. In order to add recipients to the patest-bounces addresses, the recipient domains need to have an alias domain. In the cases below the domains lists.fredhutch.org and lists.hanc.info. E.g set an alias domain for lists.fredhutch.org to x.lists.fredhutch.org and for lists.hanc.info to x.lists.hanc.info. Then postfix_vmap will contain entries like
pattest@lists.fhcrc.org pattest@lists.fredhutch.org pattest-bounces@lists.fhcrc.org pattest-bounces@lists.fredhutch.org pattest-confirm@lists.fhcrc.org pattest-confirm@lists.fredhutch.org pattest-join@lists.fhcrc.org pattest-join@lists.fredhutch.org pattest-leave@lists.fhcrc.org pattest-leave@lists.fredhutch.org pattest-owner@lists.fhcrc.org pattest-owner@lists.fredhutch.org pattest-request@lists.fhcrc.org pattest-request@lists.fredhutch.org pattest-subscribe@lists.fhcrc.org pattest-subscribe@lists.fredhutch.org pattest-unsubscribe@lists.fhcrc.org pattest-unsubscribe@lists.fredhutch.orgpattest@lists.fredhutch.org
pattest@lists.fredhutch.org pattest@x.lists.fredhutch.org pattest-bounces@lists.fredhutch.org pattest-bounces@x.lists.fredhutch.org pattest-confirm@lists.fredhutch.org pattest-confirm@x.lists.fredhutch.org pattest-join@lists.fredhutch.org pattest-join@x.lists.fredhutch.org pattest-leave@lists.fredhutch.org pattest-leave@x.lists.fredhutch.org pattest-owner@lists.fredhutch.org pattest-owner@x.lists.fredhutch.org pattest-request@lists.fredhutch.org pattest-request@x.lists.fredhutch.org pattest-subscribe@lists.fredhutch.org pattest-subscribe@x.lists.fredhutch.org pattest-unsubscribe@lists.fredhutch.org pattest-unsubscribe@x.lists.fredhutch.orgpattest@lists.fredhutch.org
phtest@lists.hanc.info pattest@x.lists.hanc.info phtest-bounces@lists.hanc.info pattest-bounces@x.lists.hanc.info phtest-confirm@lists.hanc.info pattest-confirm@x.lists.hanc.info phtest-join@lists.hanc.info pattest-join@x.lists.hanc.info phtest-leave@lists.hanc.info pattest-leave@x.lists.hanc.info phtest-owner@lists.hanc.info pattest-owner@x.lists.hanc.info phtest-request@lists.hanc.info pattest-request@x.lists.hanc.info phtest-subscribe@lists.hanc.info pattest-subscribe@x.lists.hanc.info phtest-unsubscribe@lists.hanc.info pattest-unsubscribe@x.lists.hanc.infopattest@lists.hanc.info
And I think postfix_lmtp will contain entries like
pattest@x.lists.fredhutch.org lmtp:[mailman-core]:24 pattest-bounces@x.lists.fredhutch.org lmtp:[mailman-core]:24 pattest-confirm@x.lists.fredhutch.org lmtp:[mailman-core]:24 pattest-join@x.lists.fredhutch.org lmtp:[mailman-core]:24 pattest-leave@x.lists.fredhutch.org lmtp:[mailman-core]:24 pattest-owner@x.lists.fredhutch.org lmtp:[mailman-core]:24 pattest-request@x.lists.fredhutch.org lmtp:[mailman-core]:24 pattest-subscribe@x.lists.fredhutch.org lmtp:[mailman-core]:24 pattest-unsubscribe@x.lists.fredhutch.org lmtp:[mailman-core]:24
phtest@x.lists.hanc.info lmtp:[mailman-core]:24 phtest-bounces@x.lists.hanc.info lmtp:[mailman-core]:24 phtest-confirm@x.lists.hanc.info lmtp:[mailman-core]:24 phtest-join@x.lists.hanc.info lmtp:[mailman-core]:24 phtest-leave@x.lists.hanc.info lmtp:[mailman-core]:24 phtest-owner@x.lists.hanc.info lmtp:[mailman-core]:24 phtest-request@x.lists.hanc.info lmtp:[mailman-core]:24 phtest-subscribe@x.lists.hanc.info lmtp:[mailman-core]:24 phtest-unsubscribe@x.lists.hanc.info lmtp:[mailman-core]:24
In any case you will then be able to add the additional recipient to the phtest-bounces@lists.hanc.info entry in postfix_vmap.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
HI Mark,
On 6/26/25 13:16, Mark Sapiro wrote:
On 6/26/25 11:37, Hirayama, Pat wrote:
When I look at the domains in mailman-core, I see:
show_domains() <Domain fhcrc.org> <Domain fredhutch.org> <Domain lists.fhcrc.org, , alias: lists.fredhutch.org> <Domain lists.hanc.info, , alias: >
- owner: cit-sys-engineering@fredhutch.org
This is part of the problem. The alias domain for a list should not be a real domain. Apparently, someone set this up so that mail to lists in the lists.fhcrc.org domain would go to the corresponding list in the lists.fredhutch.org domain. I think that may actually work, but you need more. In order to add recipients to the patest-bounces addresses, the recipient domains need to have an alias domain. In the cases below the domains lists.fredhutch.org and lists.hanc.info. E.g set an alias domain for lists.fredhutch.org to x.lists.fredhutch.org and for lists.hanc.info to x.lists.hanc.info.
Ah, I think that makes sense. So, add the alias domains here or through the CLI:
[cid:3f6bbb96-1ec3-4bdd-9a59-991fc9d1e31b]
Oh, does the alias domain x.lists.hanc.info (etc) need to be resolvable in DNS, or will it be internal just to Mailman?
Thanks,
-p
Pat Hirayama Pronouns: he/him/his Systems Engineer IT | Systems Engineering Fred Hutchinson Cancer Center O 206.667.4856 phirayam@fredhutch.org
Mailman's content filtering has removed the following MIME parts from this message.
Content-Type: image/png Name: image.png
Replaced multipart/alternative part with first alternative.
On 6/26/25 13:31, Hirayama, Pat wrote:
Ah, I think that makes sense. So, add the alias domains here or through the CLI:
Either way is good.
Oh, does the alias domain x.lists.hanc.info (etc) need to be resolvable in DNS, or will it be internal just to Mailman?
No, it does not need to be resolvable in DNS. It is just internal to Postfix.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
Hirayama, Pat wrote on 2025-06-26 11:37:
Everything else seems to be working — there are over 40k lmtp: entries in postfix_lmtp, and messages are being delivered.
Apologies for "butting in", but >40,000 entries in LMTP?
That seems like a bit excessive. Is it due to a failure of my imagination or could there be something (unrelated) awry here?
Well ... each list has 9 email addresses — the list address, the -bounces, the -confirm, the -join, the -leave, the -owner, the -request, the -subscribe and the -unsubscribe ... I think I'm around 4500 listservs right now.....
Anyway, as Mark explained in his most recent replies, the alias domains were not setup correctly, so that needs to be addressed, but I didn't see that his solution would reduce the number of lmtp entries ...
Pat Hirayama Pronouns: he/him/his Systems Engineer IT | Systems Engineering Fred Hutchinson Cancer Center O 206.667.4856 phirayam@fredhutch.org
From: Ron <admin@bclug.ca> Sent: Thursday, June 26, 2025 14:40 To: mailman-users@mailman3.org <mailman-users@mailman3.org> Subject: [MM3-users] Re: redirecting -bounces replies
CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe.
Hirayama, Pat wrote on 2025-06-26 11:37:
Everything else seems to be working — there are over 40k lmtp: entries in postfix_lmtp, and messages are being delivered.
Apologies for "butting in", but >40,000 entries in LMTP?
That seems like a bit excessive. Is it due to a failure of my imagination or could there be something (unrelated) awry here?
Mailman-users mailing list -- mailman-users@mailman3.org To unsubscribe send an email to mailman-users-leave@mailman3.org https://urldefense.com/v3/__https://lists.mailman3.org/mailman3/lists/mailma... Archived at: https://urldefense.com/v3/__https://lists.mailman3.org/archives/list/mailman...
This message sent to phirayam@fredhutch.org
On 6/26/25 15:29, Hirayama, Pat wrote:
Well ... each list has 9 email addresses — the list address, the -bounces, the -confirm, the -join, the -leave, the -owner, the -request, the -subscribe and the -unsubscribe ... I think I'm around 4500 listservs right now.....
4500 lists is a lot, but not unheard of, but please don't call them listservs. See https://wiki.list.org/DOC/Mailman%20is%20not%20Listserv
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
Sorry, I knew that. Thanks for your assistance today.
Pat Hirayama Pronouns: he/him/his Systems Engineer IT | Systems Engineering Fred Hutchinson Cancer Center O 206.667.4856 phirayam@fredhutch.org
From: Mark Sapiro <mark@msapiro.net> Sent: Thursday, June 26, 2025 16:36 To: mailman-users@mailman3.org <mailman-users@mailman3.org> Subject: [MM3-users] Re: redirecting -bounces replies
CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe.
On 6/26/25 15:29, Hirayama, Pat wrote:
Well ... each list has 9 email addresses — the list address, the -bounces, the -confirm, the -join, the -leave, the -owner, the -request, the -subscribe and the -unsubscribe ... I think I'm around 4500 listservs right now.....
4500 lists is a lot, but not unheard of, but please don't call them listservs. See https://urldefense.com/v3/__https://wiki.list.org/DOC/Mailman*20is*20not*20L...
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
Mailman-users mailing list -- mailman-users@mailman3.org To unsubscribe send an email to mailman-users-leave@mailman3.org https://urldefense.com/v3/__https://lists.mailman3.org/mailman3/lists/mailma... Archived at: https://urldefense.com/v3/__https://lists.mailman3.org/archives/list/mailman...
This message sent to phirayam@fredhutch.org
participants (5)
-
Hirayama, Pat -
Mark Sapiro -
Nelson Strother -
Ron -
Stephen J. Turnbull