[email protected] is a pain
Seems I'm not the only one sending posts to the
[email protected] bit bucket.
Could the maintainer of lsml either:
- get rid of [email protected]
- or forward posts in there to lsml
That bright idea might save the maintainer time but it wastes ours.
Doug Gilbert
Quoted 9 lines · Douglas Gilbert
Seems I'm not the only one sending posts to the
[email protected] bit bucket.Could the maintainer of lsml either:
- get rid of [email protected]
- or forward posts in there to lsmlThat bright idea might save the maintainer time but it wastes ours.
I think it's a majordomo feature ... you need misdelivered or undelivered emails not to come back to the list, so the return-path: is set to the owner list (so they can be removed from the email list).
In theory, a mailer should never reply to the return path, so how are you getting this in your reply path?
James
Quoted 11 lines · James Bottomley
Quoted 9 lines · Douglas Gilbert
Seems I'm not the only one sending posts to the
[email protected] bit bucket.Could the maintainer of lsml either:
- get rid of [email protected]
- or forward posts in there to lsmlThat bright idea might save the maintainer time but it wastes ours.
Quoted 8 lines
I think it's a majordomo feature ... you need misdelivered or undelivered emails not to come back to the list, so the return-path: is set to the owner list (so they can be removed from the email list).
In theory, a mailer should never reply to the return path, so how are you getting this in your reply path?
James
No, linux-scsi -list does not set that as "Reply-To:"
That behaviour is seen commonly in LAN "email" systems, which are unable to differentiate information carried in SMTP level transport vs. what is in the visible headers.
I let you figure out yourself whose email server "product" should not be connected into the Internet because it is unable to handle these fundamental differentiations in the internet email..
/Matti Aarnio