 |
| Prev-20 | Home | Next-20 |
| Prev-20 | Home | Next-20 |
| Prev-Msg | Prev-Thread | Postfix-users | Jul-2007 | Next-Thread | Next-Msg |
| Subject: | Re: Vacation Message - request for comment on implementation |
| Group: | Postfix-users |
| From: | mouss |
| Date: | 24 Jul 2007 |
> Hello,
>
> I know that most people on this list hate vacation/auto-responder type
> messages, but I also know that the same people care even more about
> them working properly when they are used.
>
> With that in mind, I'd like comments (criticism, suggestions to make
> it better behaved) on the one that works with dovecot. From the wiki
> (http://tinyurl.com/2lxwr8):
>
> ****************************************
>
> Vacation auto-reply
>
> The vacation replies are sent to the envelope sender. Currently this
> is taken from the Return-Path: header in the message.
or from the command line if this is supproted.
if the envelope sender is not available, no reply is sent.
>
> List of autoreplied senders is stored in .dovecot.lda-dupes file in
> user's home directory. When you're testing the vacation feature, it's
> easy to forget that the reply is sent only once in the number of
> configured days. If you've problems getting the vacation reply, try
> deleting this file. If that didn't help, make sure the problem isn't
> related to sending mails in general by trying the "reject" Sieve command.
if you support extensions, you can test using a unique sender each time:
foo+12345.
>
> The automatic replies aren't sent if any of the following is true:
>
> * Auto-Submitted: header exists with any value except "no"
> * Precedence: header exists with value "junk", "bulk" or "list"
> * The envelope sender
> o begins with "MAILER-DAEMON" (case-insensitive)
> o begins with "LISTSERV" (case-insensitive)
> o begins with "majordomo" (case-insensitive)
> o begins with "owner-" (case-sensitive)
replace with:
starts with "${token}-" (not case sensitive), where token is one of:
owner, request, bounces
It is safer to send nothing than send a risky one.
> o contains the string "-request" anywhere within it
> (case-sensitive)
replace with
contains "-${token}@" (not case sensitive), where token is one of:
owner, request, bounces
> * The envelope sender and envelope recipient are the same
> * The envelope recipient is not found in the message To:, Cc: or
> Bcc: fields.
>
* There is a "Sender:" header containing one of the tokens listed above.
* There is a List-Id or List-Post header
* There is no header suggesting that this is possible spam
Unlike delivery, safety here is to not send a reply if the message may
be spam. so you don't rely on recipient preferences, and you don't fear
flase positives too much (the guy who receives your auto-rep may have a
better filter, and besides annoying him, would find you stupid to miss
an obvious spam ;-p)
> The envelope sender is taken from a Return-Path: header in the
> message. The envelope recipient is taken from the recipient user (-d
> parameter with virtual user setup). A bare username without a domain
> gets canonicalised by the libsieve code to
> "<username>@unspecified-domain", which means it is highly unlikely to
> pass the last two tests in the list above.
the enveleope recipient can also be retrieved in the Delivered-To header
if this is available ('D' flag).
| Prev-Msg | Prev-Thread | Postfix-users | Jul-2007 | Next-Thread | Next-Msg |