OSEC

Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com
 
Re: .forward DSN is confusing

From: Wietse Venema (wietseporcupine.org)
Date: Fri Apr 16 2004 - 06:58:16 CDT


martin f krafft:
-- Start of PGP signed section.
> Hi there,
>
> If a user employs a .forward file, and the message cannot be
> delivered, postfix's DSN will alert the original sender that the
> email address specified in the .forward file is not reachable. e.g,

At least you're not asking if this can be reported to the .forward
owner :-)

> if A sent B a message, and B has a .forward to C, then postfix will
> deliver the following error to A:
>
> <C>: host relay[xxx.xx.xx.xx] said: 550 <C>: User unknown in local
> recipient table (in reply to RCPT TO command)
>
> This is potentially confusing. I've seen MTAs returning a message
> like "... expanded from <B>". Could postfix be made to do that?

Forwarding via .forward (and aliases) is recursive. What now? Should
the first expand from... be reported? The last? There can be only one.
Do we care about giving away system internal info to random strangers?

> Are there any means to control the text in the DSN?

Not until this whole part is redesigned. Note, DSNs give away
potentially lots of system internal info to random strangers. It
probably means that Postfix must maintain two versions of each
problem, one for local logging and problem resolution and one
censored version that is given out via email.

        Wietse