Stopped getting my own messages to a list
I recently stopped getting my own messages when posting to one of the lists. I get my own mail when posting to other lists. Receive own postings is set to Yes. I'm a non-member on the list I'm posting to, but that list has another list as a member, and I'm a member of that list, with Receive my own post set to yes. I've not configured these lists for a long time, and it has worked until recently. Any idea on where to search for the cause?
I've changed dmarc policy on the domain from none to quarantine. Should that matter?
Lars
On October 5, 2026 2:09:04 PM EDT, "Lars Bjørndal via Mailman-users" <mailman-users@mailman3.org> wrote:
I recently stopped getting my own messages when posting to one of the lists. I get my own mail when posting to other lists. Receive own postings is set to Yes. I'm a non-member on the list I'm posting to, but that list has another list as a member, and I'm a member of that list, with Receive my own post set to yes.
Does the post reach that member list? If you post directly to the member list, do you receive that post from the list? Is your delivery enabled on that list?
I've not configured these lists for a long time, and it has worked until recently. Any idea on where to search for the cause?
I've changed dmarc policy on the domain from none to quarantine. Should that matter?
Yes. What is the dmarc mitigation action on those lists?
-- Mark Sapiro <mark@msapiro.net> Sent from my Not_an_iThing with standards compliant, open source software.
Thank you! You wrote:
On October 5, 2026 2:09:04 PM EDT, "Lars Bjørndal via Mailman-users" <mailman-users@mailman3.org> wrote:
I recently stopped getting my own messages when posting to one of the lists. I get my own mail when posting to other lists. Receive own postings is set to Yes. I'm a non-member on the list I'm posting to, but that list has another list as a member, and I'm a member of that list, with Receive my own post set to yes.
Does the post reach that member list?
Yes. I know others who has got them.
If you post directly to the member list, do you receive that post from the list?
I haven't tested that.
Is your delivery enabled on that list?
Yes.
I've not configured these lists for a long time, and it has worked until recently. Any idea on where to search for the cause?
I've changed dmarc policy on the domain from none to quarantine. Should that matter?
Yes. What is the dmarc mitigation action on those lists?
Replace From: with list address and DMARC Mitigate unconditionally set to no for both lists.
Lars
Lars Bjørndal via Mailman-users writes:
I recently stopped getting my own messages when posting to one of the lists.
The most common reason for this is sending from Gmail, which considers the list copy to be a duplicate and it is suppressed. In Gmail this behavior cannot be changed. I don't know if any other MUAs or email providers do this.
I get my own mail when posting to other lists.
That probably rules out the "overeager duplicate suppression" hypothesis.
Receive own postings is set to Yes. I'm a non-member on the list I'm posting to, but that list has another list as a member, and I'm a member of that list,
The nonmember of the posting list and the member of the second list have the same address, correct?
You are allowed to post to the downstream list directly, correct? Are your posts reaching the downstream list archives, or other members of that list? I don't think that cascading lists automatically allow the upstream list to send to the downstream list, unless the upstream list members are specified as permitted. (I may be remembering a feature from Mailman 2 that didn't get ported the same way, though.)
with Receive my own post set to yes. I've not configured these lists for a long time, and it has worked until recently. Any idea on where to search for the cause?
On each list, there are four places where Receive Own Post can be set IIRC.
- On the subscription (highest priority)
- On the address
- On your user
- On the list itself as a default (lowest priority)
The first one to have a non-"inherit" value wins. Since there are two lists there are two subscriptions, and two list defaults to check, as well as the address and the user (common over the two lists). Since you're only seeing this on this one cascade of lists, I'd check those subscriptions first (I guess non-members have no subscription options, so it would be the downstream list subscription if any).
I've changed dmarc policy on the domain from none to quarantine. Should that matter?
It certainly could, if the first list's processing invalidates a signature for a user at the list domain. It would then sign again, for the same domain, so that there would be a valid and an invalid signature for the domain. According to the DKIM standard, this should be considered a pass, but many implementations are buggy. You could set "strip existing DKIM signatures" to yes for the first list to see if that helps.
You should also see those posts in your spam folder.
-- GNU Mailman consultant (installation, migration, customization) Sirius Open Source https://www.siriusopensource.com/ Software systems consulting in Europe, North America, and Japan
Hi, Stephen, and thanks for your input!
You wrote:
Lars Bjørndal via Mailman-users writes:
I recently stopped getting my own messages when posting to one of the lists.
The most common reason for this is sending from Gmail, which considers the list copy to be a duplicate and it is suppressed. In Gmail this behavior cannot be changed. I don't know if any other MUAs or email providers do this.
I'm seinding from this address, and Gmail isn't involved.
I get my own mail when posting to other lists.
That probably rules out the "overeager duplicate suppression" hypothesis.
Receive own postings is set to Yes. I'm a non-member on the list I'm posting to, but that list has another list as a member, and I'm a member of that list,
The nonmember of the posting list and the member of the second list have the same address, correct?
Yes.
You are allowed to post to the downstream list directly, correct?
Hes.
Are your posts reaching the downstream list archives, or other members of that list?
Yes.
I don't think that cascading lists automatically allow the upstream list to send to the downstream list, unless the upstream list members are specified as permitted. (I may be remembering a feature from Mailman 2 that didn't get ported the same way, though.)
with Receive my own post set to yes. I've not configured these lists for a long time, and it has worked until recently. Any idea on where to search for the cause?
On each list, there are four places where Receive Own Post can be set IIRC.
- On the subscription (highest priority)
- On the address
- On your user
- On the list itself as a default (lowest priority)
Good to know.
The first one to have a non-"inherit" value wins. Since there are two lists there are two subscriptions, and two list defaults to check, as well as the address and the user (common over the two lists). Since you're only seeing this on this one cascade of lists, I'd check those subscriptions first (I guess non-members have no subscription options, so it would be the downstream list subscription if any). Right.
I've changed dmarc policy on the domain from none to quarantine. Should that matter?
It certainly could, if the first list's processing invalidates a signature for a user at the list domain. It would then sign again, for the same domain, so that there would be a valid and an invalid signature for the domain. According to the DKIM standard, this should be considered a pass, but many implementations are buggy. You could set "strip existing DKIM signatures" to yes for the first list to see if that helps.
Where do I find this setting? I didn't find it.
You should also see those posts in your spam folder.
Actually, I cannot see my own message in the postfix log, so it seems that the message doesn't leave Mailman3. I'm running opendkim-2.11.0-0.
Lars
Hi, Lars
Lars Bjørndal via Mailman-users writes:
Lars Bjørndal via Mailman-users writes:
You could set "strip existing DKIM signatures" to yes for the first list to see if that helps.
Where do I find this setting? I didn't find it.
You can add it to mailman.cfg.
# Some list posts and mail to the -owner address may contain DomainKey or # DomainKeys Identified Mail (DKIM) signature headers <https://dkim.org/>. # Various list transformations to the message such as adding a list header or # footer or scrubbing attachments or even reply-to munging can break these # signatures. It is generally felt that these signatures have value, even if # broken and even if the outgoing message is resigned. However, some sites # may wish to remove these headers by setting this to 'yes'. remove_dkim_headers: no
You should also see those posts in your spam folder.
Actually, I cannot see my own message in the postfix log, so it seems that the message doesn't leave Mailman3. I'm running opendkim-2.11.0-0.
Then you should check all the logs and try to track where the message gets stopped (eg, if Python's email package decides your mail violates an RFC it will raise an Error and you'll get a traceback in the mailman.log. I think opendkim also writes to separate logs. If there are any
-- GNU Mailman consultant (installation, migration, customization) Sirius Open Source https://www.siriusopensource.com/ Software systems consulting in Europe, North America, and Japan
Thank you, Stephen!
You wrote:
Lars Bjørndal via Mailman-users writes:
Lars Bjørndal via Mailman-users writes:
You could set "strip existing DKIM signatures" to yes for the first list to see if that helps.
Where do I find this setting? I didn't find it.
You can add it to mailman.cfg.
Ah, I see.
# Some list posts and mail to the -owner address may contain DomainKey or # DomainKeys Identified Mail (DKIM) signature headers <https://dkim.org/>. # Various list transformations to the message such as adding a list header or # footer or scrubbing attachments or even reply-to munging can break these # signatures. It is generally felt that these signatures have value, even if # broken and even if the outgoing message is resigned. However, some sites # may wish to remove these headers by setting this to 'yes'. remove_dkim_headers: no
You should also see those posts in your spam folder.
Actually, I cannot see my own message in the postfix log, so it seems that the message doesn't leave Mailman3. I'm running opendkim-2.11.0-0.
Then you should check all the logs and try to track where the message gets stopped (eg, if Python's email package decides your mail violates an RFC it will raise an Error and you'll get a traceback in the mailman.log. I think opendkim also writes to separate logs. If there are any
I'm searching with journalctl and can not find the message to me. But in the mailman.log, I have the following:
Oct 04 20:24:31 2026 (1162431) ACCEPT: <m3zewt729n.fsf@dalen.lamasti.net>
[04/Oct/2026:20:24:32 +0200] "GET /3.1/lists/medlemmer@hodr.no HTTP/1.1" 200 393 "-" "GNU Mailman REST client v3.3.5"
[04/Oct/2026:20:24:32 +0200] "GET /3.1/lists/medlemmer@hodr.no/config HTTP/1.1" 200 3409 "-" "GNU Mailman REST client v3.3.5"
[04/Oct/2026:20:24:33 +0200] "GET /3.1/users/annonsering@hodr.no HTTP/1.1" 404 58 "-" "GNU Mailman REST client v3.3.5"
[04/Oct/2026:20:24:33 +0200] "GET /3.1/lists/medlemmer.hodr.no/roster/owner HTTP/1.1" 200 722 "-" "GNU Mailman REST client v3.3.5"
[04/Oct/2026:20:24:33 +0200] "GET /3.1/addresses/lars@lamasti.net HTTP/1.1" 200 365 "-" "GNU Mailman REST client v3.3.5"
[04/Oct/2026:20:24:33 +0200] "GET /3.1/lists/medlemmer.hodr.no/roster/moderator HTTP/1.1" 200 90 "-" "GNU Mailman REST client v3.3.5"
Oct 04 20:24:33 2026 (1162426) HyperKitty archived message <m3zewt729n.fsf@dalen.lamasti.net> to https://hodr.no/archives/list/medlemmer@hodr.no/message/NJ536JLNQY7HXWUYQ7Q6VQIBVE4RRW32/
[04/Oct/2026:20:28:14 +0200] "GET /3.1/lists/annonsering@hodr.no HTTP/1.1" 200 391 "-" "GNU Mailman REST client v3.3.5"
Oct 04 20:31:21 2026 (1162431) annonsering: DMARC lookup for lars@lamasti.net (_dmarc.lamasti.net) found p=quarantine in _dmarc.lamasti.net. = v=DMARC1; p=quarantine; sp=quarantine; rua=mailto:dmarc@lamasti.net; fo=1; ri=604800
Oct 04 20:31:21 2026 (1162431) ACCEPT: <m3v77h71xj.fsf@dalen.lamasti.net>
[04/Oct/2026:20:31:23 +0200] "GET /3.1/lists/annonsering@hodr.no HTTP/1.1" 200 391 "-" "GNU Mailman REST client v3.3.5"
[04/Oct/2026:20:31:23 +0200] "GET /3.1/lists/annonsering@hodr.no/config HTTP/1.1" 200 3446 "-" "GNU Mailman REST client v3.3.5"
[04/Oct/2026:20:31:24 +0200] "GET /3.1/users/lars@lamasti.net HTTP/1.1" 200 259 "-" "GNU Mailman REST client v3.3.5"
[04/Oct/2026:20:31:24 +0200] "GET /3.1/lists/annonsering.hodr.no/roster/owner HTTP/1.1" 200 724 "-" "GNU Mailman REST client v3.3.5"
[04/Oct/2026:20:31:24 +0200] "GET /3.1/addresses/lars@lamasti.net HTTP/1.1" 200 365 "-" "GNU Mailman REST client v3.3.5"
[04/Oct/2026:20:31:24 +0200] "GET /3.1/lists/annonsering.hodr.no/roster/moderator HTTP/1.1" 200 90 "-" "GNU Mailman REST client v3.3.5"
Oct 04 20:31:25 2026 (1162426) HyperKitty archived message <m3v77h71xj.fsf@dalen.lamasti.net> to https://hodr.no/archives/list/annonsering@hodr.no/message/J5TFS2KDR6CGUC7L4MYXKTCOIQCMXMAW/
Oct 04 20:31:43 2026 (1162431) medlemmer: DMARC lookup for annonsering@hodr.no (_dmarc.hodr.no) found p=quarantine in _dmarc.hodr.no. = v=DMARC1; p=quarantine; sp=quarantine; rua=mailto:dmarc@hodr.no; fo=1; ri=604800
Oct 04 20:31:43 2026 (1162431) ACCEPT: <m3v77h71xj.fsf@dalen.lamasti.net>
[04/Oct/2026:20:31:44 +0200] "GET /3.1/lists/medlemmer@hodr.no HTTP/1.1" 200 393 "-" "GNU Mailman REST client v3.3.5"
[04/Oct/2026:20:31:44 +0200] "GET /3.1/lists/medlemmer@hodr.no/config HTTP/1.1" 200 3409 "-" "GNU Mailman REST client v3.3.5"
[04/Oct/2026:20:31:44 +0200] "GET /3.1/users/annonsering@hodr.no HTTP/1.1" 404 58 "-" "GNU Mailman REST client v3.3.5"
[04/Oct/2026:20:31:44 +0200] "GET /3.1/lists/medlemmer.hodr.no/roster/owner HTTP/1.1" 200 722 "-" "GNU Mailman REST client v3.3.5"
[04/Oct/2026:20:31:44 +0200] "GET /3.1/addresses/lars@lamasti.net HTTP/1.1" 200 365 "-" "GNU Mailman REST client v3.3.5"
[04/Oct/2026:20:31:44 +0200] "GET /3.1/lists/medlemmer.hodr.no/roster/moderator HTTP/1.1" 200 90 "-" "GNU Mailman REST client v3.3.5"
Oct 04 20:31:45 2026 (1162426) HyperKitty archived message <m3v77h71xj.fsf@dalen.lamasti.net> to https://hodr.no/archives/list/medlemmer@hodr.no/message/J5TFS2KDR6CGUC7L4MYXKTCOIQCMXMAW/
In /opt/mailman3/mm/var/logs/smtp.log, I have:
Oct 04 20:31:20 2026 (1162433) Available AUTH mechanisms: LOGIN(builtin) PLAIN(builtin)
Oct 04 20:31:20 2026 (1162433) Peer: ('127.0.0.1', 56550)
Oct 04 20:31:20 2026 (1162433) ('127.0.0.1', 56550) handling connection
Oct 04 20:31:20 2026 (1162433) ('127.0.0.1', 56550) >> b'LHLO dalen.lamasti.net'
Oct 04 20:31:20 2026 (1162433) ('127.0.0.1', 56550) >> b'MAIL FROM:<lrs@dalen.lamasti.net> SIZE=2965'
Oct 04 20:31:20 2026 (1162433) ('127.0.0.1', 56550) sender: lrs@dalen.lamasti.net
Oct 04 20:31:20 2026 (1162433) ('127.0.0.1', 56550) >> b'RCPT TO:<annonsering@boug.hodr.no>'
Oct 04 20:31:20 2026 (1162433) ('127.0.0.1', 56550) recip: annonsering@boug.hodr.no
Oct 04 20:31:20 2026 (1162433) ('127.0.0.1', 56550) >> b'DATA'
Oct 04 20:31:20 2026 (1162433) ('127.0.0.1', 56550) >> b'QUIT'
Oct 04 20:31:20 2026 (1162433) ('127.0.0.1', 56550) connection lost
Oct 04 20:31:20 2026 (1162433) ('127.0.0.1', 56550) Connection lost during _handle_client()
Oct 04 20:31:42 2026 (1162433) Available AUTH mechanisms: LOGIN(builtin) PLAIN(builtin)
Oct 04 20:31:42 2026 (1162433) Peer: ('127.0.0.1', 36900)
Oct 04 20:31:42 2026 (1162433) ('127.0.0.1', 36900) handling connection
Oct 04 20:31:42 2026 (1162433) ('127.0.0.1', 36900) >> b'LHLO dalen.lamasti.net'
Oct 04 20:31:42 2026 (1162433) ('127.0.0.1', 36900) >> b'MAIL FROM:<annonsering-bounces+medlemmer=hodr.no@hodr.no> SIZE=5274'
Oct 04 20:31:42 2026 (1162433) ('127.0.0.1', 36900) sender: annonsering-bounces+medlemmer=hodr.no@hodr.no
Oct 04 20:31:42 2026 (1162433) ('127.0.0.1', 36900) >> b'RCPT TO:<medlemmer@boug.hodr.no>'
Oct 04 20:31:42 2026 (1162433) ('127.0.0.1', 36900) recip: medlemmer@boug.hodr.no
Oct 04 20:31:42 2026 (1162433) ('127.0.0.1', 36900) >> b'DATA'
Oct 04 20:31:42 2026 (1162433) ('127.0.0.1', 36900) >> b'QUIT'
Oct 04 20:31:42 2026 (1162433) ('127.0.0.1', 36900) connection lost
Oct 04 20:31:42 2026 (1162433) ('127.0.0.1', 36900) Connection lost during _handle_client()
Oct 04 20:31:43 2026 (1162434) <m3v77h71xj.fsf@dalen.lamasti.net> smtp to annonsering@hodr.no for 53 recips, completed in 20.956834316253662 seconds
Oct 04 20:31:43 2026 (1162434) <m3v77h71xj.fsf@dalen.lamasti.net> post to annonsering@hodr.no from annonsering@hodr.no, 3441 bytes
Oct 04 20:32:11 2026 (1162434) <m3v77h71xj.fsf@dalen.lamasti.net> smtp to medlemmer@hodr.no for 97 recips, completed in 26.66346001625061 seconds
Oct 04 20:32:11 2026 (1162434) <m3v77h71xj.fsf@dalen.lamasti.net> post to medlemmer@hodr.no from medlemmer@hodr.no, 5843 bytes
Can you see a reason for why I don't get messages to myself out of this?
Thanks, Lars
Lars Bjørndal via Mailman-users writes:
You can add it to mailman.cfg.
Ah, I see.
Yeah, I forgot it wasn't a per-list option (site-wide makes sense, since we recommend handling authentication in the MTA, where you can take advantage of SPF as well as DKIM).
I'm searching with journalctl and can not find the message to me. But in the mailman.log, I have the following:
Looks completely standard to me. The "ACCEPT" messages are from Mailman core saying it received mail from the LMTP runner and found a corresponding list. I'm not sure what the sequence of "GET" is doing, but I'm sure they are from HyperKitty to Mailman core. Your address appears in those GETs because it it the owner address, not because it's a list member. The "DMARC lookup" are from Mailman core. All as expected, based on what you've told us.
You do see the message in both archives, is that correct?
In /opt/mailman3/mm/var/logs/smtp.log, I have:
Pruning expected boilerplate for brevity:
Oct 04 20:31:20 2026 (1162433) Peer: ('127.0.0.1', 56550) Oct 04 20:31:20 2026 (1162433) ('127.0.0.1', 56550) sender: lrs@dalen.lamasti.net Oct 04 20:31:20 2026 (1162433) ('127.0.0.1', 56550) recip: annonsering@boug.hodr.no Oct 04 20:31:42 2026 (1162433) Peer: ('127.0.0.1', 36900) Oct 04 20:31:42 2026 (1162433) ('127.0.0.1', 36900) sender: annonsering-bounces+medlemmer=hodr.no@hodr.no Oct 04 20:31:42 2026 (1162433) ('127.0.0.1', 36900) recip: medlemmer@boug.hodr.no Oct 04 20:31:43 2026 (1162434) <m3v77h71xj.fsf@dalen.lamasti.net> smtp to annonsering@hodr.no for 53 recips, completed in 20.956834316253662 seconds Oct 04 20:31:43 2026 (1162434) <m3v77h71xj.fsf@dalen.lamasti.net> post to annonsering@hodr.no from annonsering@hodr.no, 3441 bytes Oct 04 20:32:11 2026 (1162434) <m3v77h71xj.fsf@dalen.lamasti.net> smtp to medlemmer@hodr.no for 97 recips, completed in 26.66346001625061 seconds Oct 04 20:32:11 2026 (1162434) <m3v77h71xj.fsf@dalen.lamasti.net> post to medlemmer@hodr.no from medlemmer@hodr.no, 5843 bytes
Can you see a reason for why I don't get messages to myself out of this?
As I understand it from this trace, "lrs@dalen.lamasti.net" is you, "annonsering" is the upstream list, and "medlemmer" is the downstream post. I don't understand why it is "lrs@dalen.lamasti.net" and not "lars@lamsti.net". Possibly you have a rewrite rule in the MTA. My guess about nondelivery is that dalen.lamasti.net is covered by the quarantine policy:
_dmarc.lamasti.net descriptive text "v=DMARC1; p=quarantine; "
"sp=quarantine; rua=mailto:dmarc@lamasti.net; fo=1; ri=604800"but it is not covered by your DKIM signature. The signature probably has "d=lamasti.net", but this value must be identical to the domain part of the address to pass DMARC. (Nothing in DKIM or DMARC cares about "lrs" vs. "lars". Only your MTA cares when routing the mail.)
If I am correct in that guess, why the quarantined mail is not showing up in a spam mailbox or something like that is an issue of either your MDA or your MUA configuration. I can't guess about that.
Regards, Steve
-- GNU Mailman consultant (installation, migration, customization) Sirius Open Source https://www.siriusopensource.com/ Software systems consulting in Europe, North America, and Japan
Thanks a lot, Stephen! You wrote:
Lars Bjørndal via Mailman-users writes:
[...]
I'm searching with journalctl and can not find the message to me. But in the mailman.log, I have the following:
Looks completely standard to me. The "ACCEPT" messages are from Mailman core saying it received mail from the LMTP runner and found a corresponding list. I'm not sure what the sequence of "GET" is doing, but I'm sure they are from HyperKitty to Mailman core. Your address appears in those GETs because it it the owner address, not because it's a list member. The "DMARC lookup" are from Mailman core. All as expected, based on what you've told us.
You do see the message in both archives, is that correct?
Yes.
In /opt/mailman3/mm/var/logs/smtp.log, I have:
Pruning expected boilerplate for brevity:
Oct 04 20:31:20 2026 (1162433) Peer: ('127.0.0.1', 56550) Oct 04 20:31:20 2026 (1162433) ('127.0.0.1', 56550) sender: lrs@dalen.lamasti.net Oct 04 20:31:20 2026 (1162433) ('127.0.0.1', 56550) recip: annonsering@boug.hodr.no Oct 04 20:31:42 2026 (1162433) Peer: ('127.0.0.1', 36900) Oct 04 20:31:42 2026 (1162433) ('127.0.0.1', 36900) sender: annonsering-bounces+medlemmer=hodr.no@hodr.no Oct 04 20:31:42 2026 (1162433) ('127.0.0.1', 36900) recip: medlemmer@boug.hodr.no Oct 04 20:31:43 2026 (1162434) <m3v77h71xj.fsf@dalen.lamasti.net> smtp to annonsering@hodr.no for 53 recips, completed in 20.956834316253662 seconds Oct 04 20:31:43 2026 (1162434) <m3v77h71xj.fsf@dalen.lamasti.net> post to annonsering@hodr.no from annonsering@hodr.no, 3441 bytes Oct 04 20:32:11 2026 (1162434) <m3v77h71xj.fsf@dalen.lamasti.net> smtp to medlemmer@hodr.no for 97 recips, completed in 26.66346001625061 seconds Oct 04 20:32:11 2026 (1162434) <m3v77h71xj.fsf@dalen.lamasti.net> post to medlemmer@hodr.no from medlemmer@hodr.no, 5843 bytes
Can you see a reason for why I don't get messages to myself out of this?
As I understand it from this trace, "lrs@dalen.lamasti.net" is you, "annonsering" is the upstream list, and "medlemmer" is the downstream post.
That's right.
I don't understand why it is "lrs@dalen.lamasti.net" and not "lars@lamsti.net".
My account name is lrs, but I have an alias of lars.
Possibly you have a rewrite rule in the MTA. My guess about nondelivery is that dalen.lamasti.net is covered by the quarantine policy:
_dmarc.lamasti.net descriptive text "v=DMARC1; p=quarantine; " "sp=quarantine; rua=mailto:dmarc@lamasti.net; fo=1; ri=604800"but it is not covered by your DKIM signature. The signature probably has "d=lamasti.net", but this value must be identical to the domain part of the address to pass DMARC. (Nothing in DKIM or DMARC cares about "lrs" vs. "lars". Only your MTA cares when routing the mail.)
If I am correct in that guess, why the quarantined mail is not showing up in a spam mailbox or something like that is an issue of either your MDA or your MUA configuration. I can't guess about that.
Ok, thank you. But then I should have seen someting about the message - to me - in the postfix log. Doesn't that make sence? I see that other members, both on annonsering and on medlemmer, does appear in the log, but not lars or lrs for that message.
Lars
Lars Bjørndal via Mailman-users writes:
Thanks a lot, Stephen! You wrote:
I don't understand why it is "lrs@dalen.lamasti.net" and not "lars@lamsti.net".
My account name is lrs, but I have an alias of lars.
Local aliases don't matter DMARC, but the domain vs. subdomain could. I think that because of the "sp=quarantine" in your DMARC record, that should not matter to DMARC policy, but I think it DOES matter to DKIM validation, as described here:
Possibly you have a rewrite rule in the MTA. My guess about nondelivery is that dalen.lamasti.net is covered by the quarantine policy:
_dmarc.lamasti.net descriptive text "v=DMARC1; p=quarantine; " "sp=quarantine; rua=mailto:dmarc@lamasti.net; fo=1; ri=604800"but it is not covered by your DKIM signature. The signature probably has "d=lamasti.net", but this value must be identical to the domain part of the address to pass DMARC. (Nothing in DKIM or DMARC cares about "lrs" vs. "lars". Only your MTA cares when routing the mail.)
Ok, thank you. But then I should have seen someting about the message - to me - in the postfix log. Doesn't that make sence?
That's right. DMARC policy triggers at receipt. Since your address becomes a delivery target only at the delivery from downstream list to your personal address, that's where it would show up. Neither Mailman nor Postfix will refuse to deliver at that point, the policy action is the responsibility of the final recipient. So there will be a local delivery from the downstream list via Postfix to the MX for your subscribed address.
Because "p=quarantine", there will be no delivery failure. Instead, it gets delivered to the last MTA in the chain or an MDA, which then may put it in your INBOX, or may put it somewhere special, typically a spam folder.
If the list's Postfix is also your Postfix, then I'm not sure how Postfix logs receipt, whether it gives the address at receipt, the actual delivered address, or both. Otherwise you should see incoming and outgoing logs for your subscribed address.
The Mailman to outgoing MTA delivery gets obfuscated in Mailman's smtp.log as "delivered to N members" and "posted to M members". Postfix does something similar, I think, in cases where multiple addresses are delivered to the same remote MTA. That is, it only mentions the first of the list of addresses. So that's one reason you might not be seeing your address.
I see that other members, both on annonsering and on medlemmer, does appear in the log, but not lars or lrs for that message.
Does the downstream list personalize delivery? If it does bulk delivery, then you may not see lars@ or lrs@ in the Postfix log. If it's personalized, you should see at least one of them.
-- GNU Mailman consultant (installation, migration, customization) Sirius Open Source https://www.siriusopensource.com/ Software systems consulting in Europe, North America, and Japan
Thank you very much!
After changing receive_list_copy from false to True, I again get my own message.
Lars
On Mon, Oct 12, 2026 at 04:11:38PM +0900, Stephen J. Turnbull wrote:
Lars Bjørndal via Mailman-users writes:
Thanks a lot, Stephen! You wrote:
I don't understand why it is "lrs@dalen.lamasti.net" and not "lars@lamsti.net".
My account name is lrs, but I have an alias of lars.
Local aliases don't matter DMARC, but the domain vs. subdomain could. I think that because of the "sp=quarantine" in your DMARC record, that should not matter to DMARC policy, but I think it DOES matter to DKIM validation, as described here:
Possibly you have a rewrite rule in the MTA. My guess about nondelivery is that dalen.lamasti.net is covered by the quarantine policy:
_dmarc.lamasti.net descriptive text "v=DMARC1; p=quarantine; " "sp=quarantine; rua=mailto:dmarc@lamasti.net; fo=1; ri=604800"but it is not covered by your DKIM signature. The signature probably has "d=lamasti.net", but this value must be identical to the domain part of the address to pass DMARC. (Nothing in DKIM or DMARC cares about "lrs" vs. "lars". Only your MTA cares when routing the mail.)
Ok, thank you. But then I should have seen someting about the message - to me - in the postfix log. Doesn't that make sence?
That's right. DMARC policy triggers at receipt. Since your address becomes a delivery target only at the delivery from downstream list to your personal address, that's where it would show up. Neither Mailman nor Postfix will refuse to deliver at that point, the policy action is the responsibility of the final recipient. So there will be a local delivery from the downstream list via Postfix to the MX for your subscribed address.
Because "p=quarantine", there will be no delivery failure. Instead, it gets delivered to the last MTA in the chain or an MDA, which then may put it in your INBOX, or may put it somewhere special, typically a spam folder.
If the list's Postfix is also your Postfix, then I'm not sure how Postfix logs receipt, whether it gives the address at receipt, the actual delivered address, or both. Otherwise you should see incoming and outgoing logs for your subscribed address.
The Mailman to outgoing MTA delivery gets obfuscated in Mailman's smtp.log as "delivered to N members" and "posted to M members". Postfix does something similar, I think, in cases where multiple addresses are delivered to the same remote MTA. That is, it only mentions the first of the list of addresses. So that's one reason you might not be seeing your address.
I see that other members, both on annonsering and on medlemmer, does appear in the log, but not lars or lrs for that message.
Does the downstream list personalize delivery? If it does bulk delivery, then you may not see lars@ or lrs@ in the Postfix log. If it's personalized, you should see at least one of them.
-- GNU Mailman consultant (installation, migration, customization) Sirius Open Source https://www.siriusopensource.com/ Software systems consulting in Europe, North America, and Japan
participants (3)
-
Lars Bjørndal -
Mark Sapiro -
Stephen J. Turnbull