Re: Domain Change Notification

2 msg	SQL query as alias
3 msg	Mailfrom restriction and SASL clients
4 msg	How to inform outside users that domain soon wi...
31 msg	ASSP and NOOP
9 msg	Double restrictions for SMTP Authen question ?
5 msg	Resend 'virus' mails
3 msg	message_size_limit exceptions
53 msg	about greylist.pl and alternatives
7 msg	failing to send a large mail
1 msg	Re: Another weird cert question
2 msg	Restrict sending to one address from one IP?
6 msg	Forcing PIX workarounds?
4 msg	header checks are not working
9 msg	recipient_delimiter
3 msg	Documenting alias expansion in mails

Domain Change Notification
\ Kidney, Brian (28 May 2007)
. \ Tony Earnshaw (28 May 2007)
. \ (Wietse Venema) (28 May 2007)
. . \ Victor Duchovni (28 May 2007)
. . . \ (Wietse Venema) (28 May 2007)

4 msg	How to do a defer_if_permit with a SMTP code 451?
4 msg	virtual: mbox fine, maildir generates 'fatal: g...
5 msg	Multiple relays and rate control with anvil
19 msg	550

Subject:	Re: Domain Change Notification
Group:	Postfix-users
From:	(Wietse Venema)
Date:	28 May 2007

Victor Duchovni:
> On Mon, May 28, 2007 at 05:38:51PM -0400, Wietse Venema wrote:
>
> > /etc/postfix/master.cf:
> > example-notify unix - n n - - pipe
> > flags=q user=nobody argv=/some/where/example-notify $sender $user
> >
> > This invokes a script called /some/where/example-notify with as
> > arguments the envelope sender and the username. the script then
> > pipes a message into /usr/sbin/sendmail. Writing the script is an
> > exercise for the reader.
> >
> > See also: virtual(5), transport(5), pipe(8).
> >
> > Caution: $sender and $user my contain hostile information. Take
> > all the usual countermeasures to prevent command injection.
> > For example, this is risky:
> >
> > open(MAIL, "|/usr/sbin/sendmail $sender") || die "can't run sendmail: $!\n";
> >
>
> In addition to security concerns, auto-responders need to handle RFC
> 3834 recommendations and avoid responding to lists, auto-responses,
> legacy "Precedence: bulk", ...
>
> A decent auto-responder requires a good deal of care, try to re-use
> code from a known-correct version.

If someone could post a working solution based on vacation or
whatever, instead making vague suggestions that don't help anyone,
then we might actually be able to put something into the Postfix
docs and make progress.

Note that this tool sends to the list administrative address not
the list distribution address. The casual reader might confuse
this with an out-of-office application, but it's not.

Wietse