Sept. 19, 2010
7:17 a.m.
On 09/18/10 15:49, Odhiambo Washington wrote: <snip>
hello Mark, thank you for your answer! very helpful as always; please excuse my very late reply... i did the test with sending a test message to a bogus alias - the good thing is that in the returned message there is some info: ----- Transcript of session follows ----- post script, list not found: bogus 554 5.3.0 unknown mailer error 1 this is nice since it says... "no such list here" and i am also able to see all failed posts in mailman's error log. the negative thing is that the returned mail exposes my mailman installation path: The original message was received at Fri, 17 Sep 2010 17:35:10 +0300 (EEST) from myhost.mydomain.dom [192.192.192.192] ----- The following addresses had permanent fatal errors ----- "|/my/real/path/to/mailman/mail/mailman post bogus" <snip> Final-Recipient: RFC822; mybogus-alias@mydomain.dom X-Actual-Recipient: X-Unix; |/my/real/path/to/mailman/mail/mailman post bogus <snip> <http://mail.python.org/mailman/options/mailman-users/odhiambo%40gmail.com>That, I see no problem with! It's a good "diagnostic" message. I know you don't see it as such, but if your server isn't secured is what you need to worry about. Nobody will access that path if server is secured properly.
hello Odhiambo,
thanks for your comment. the machine is fairly secured, however i do prefer not to expose any such information in "returned mail" messages.
greetings,
Stoyan