From: martin f krafft (postfix-users=postfix.orgmass.madduck.net)
Date: Fri Apr 16 2004 - 07:51:09 CDT

• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

also sprach Wietse Venema <wietseporcupine.org> [2004.04.16.1358 +0200]:
> > 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 :-)

hehe. that's actually the reason i started to investigate this.
a user put an undeliverable address in a .procmailrc forward rule
and created a massive mail loop as the DSN was not deliverable.
adding

  SENDMAILARGS="$SENDMAILARGS -f $1"

to /etc/procmailrc

and changing mailbox_command to `procmail -a $SENDER`

solved that. However, the DSN is just as confusing as the .forward
DSN.

> 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?

The address to which some users decides to forward isn't exactly
system internal, right; /etc/aliases is, to a certain degree.

I didn't consider the recursive nature of alias expansion, but now
that you mention it, it makes perfect sense.

It's good that the original message down at the bottom contains the
RFC822 headers with the original recipient, which is far more
relevant than the envelope data. However, I wonder if it's possible
to change the following:

  "I'm sorry to have to inform you that the message returned
   below could not be delivered to one or more destinations."

  s/below/at the bottom of this mail/

I feel that this would make it easier for the home user.

On a related note, is it possible to change the <postmaster> value
in the DSN to a custom parameter? $bounce_notice_recipient does not
seem to do it...
  
> > 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.

You could go a template approach and let the sysadmin decide what
can be spouted to strangers and what not.

Thanks,

--
martin; (greetings from the heart of the sun.)
  \____ echo mailto: !#^."<*>"|tr "<*> mailto:" netmadduck
 
invalid/expired pgp subkeys? use subkeys.pgp.net as keyserver!
 
"the husbands of very beautiful women
 belong to the criminal classes."
                                                        -- oscar wilde

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFAf9a9IgvIgzMMSnURAphTAJ0Tu0FydXdQaxHAJR68HKx3q7VsAwCg0AcJ
eLzkXyODteeW4L6OV+4WVyc=
=t8fa
-----END PGP SIGNATURE-----

• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]