Summary | Inconsistent vacation excludes |
Queue | Ingo |
Queue Version | HEAD |
Type | Enhancement |
State | Assigned |
Priority | 2. Medium |
Owners | jan (at) horde (dot) org |
Requester | jan (at) horde (dot) org |
Created | 12/07/2007 (6368 days ago) |
Due | |
Updated | 07/28/2008 (6134 days ago) |
Assigned | 12/14/2007 (6361 days ago) |
Resolved | |
Milestone | |
Patch | No |
top as soon as it is enabled the other maildrop rules do not get
processed. Perhaps the vacation rule needs to be at the very bottom
or the script changed slightly?
different headers and with Ingo it's really easy to have a spam
filter rule *before* the vacation rule, so this is redundant. In the
worst case it even applies a different spam rule than what the user
usually does.
in the mean time there could be a warning that the vacation will go to
all lists and spam and a suggestion to create and enable a spam rule
and move it before the vacation rule? I know I would have appreciated
that information. I already have settings in sam and in a global
.mailfilter but vacation replies were still sent to spam which I did
not expect.
If the spam rule should be "*before*" the vacation rule then why not
make that the default? Thanks.
State ⇒ Assigned
Assigned to Jan Schneider
different headers and with Ingo it's really easy to have a spam
filter rule *before* the vacation rule, so this is redundant. In the
worst case it even applies a different spam rule than what the user
usually does.
I'm against using the Spam header because different spam filters use
different headers and with Ingo it's really easy to have a spam filter
rule *before* the vacation rule, so this is redundant. In the worst
case it even applies a different spam rule than what the user usually
does.
Some additional information: procmail's FROM_DAEMON is a shortcut for:
(^(Mailing-List:|Precedence:.*(junk|bulk|list)|To: Multiple
recipients of |(((Resent-)?(From|Sender)|X-Envelope-From):|>?From
)([^>]*[^(.%@a-z0-9])?(Post(ma?(st(e?r)?|n)|office)|(send)?Mail(er)?
|daemon|m(mdf|ajordomo)|n?uucp|LIST(SERV|proc)|NETSERV|o(wner|ps)
|r(e(quest|sponse)|oot)|b(ounce|bs\.smtp)|echo|mirror|s(erv(ices?|er)
|mtp(error)?|ystem)|A(dmin(istrator)?|MMGR|utoanswer))(([^).!:a-
z0-9][-_a-z0-9]*)?[%@>\t ][^<)]*(\(.*\).*)?)?$([^>]|$)))
Author's comment: how's that for a regular expression :-)
missing something I'd vote for the combination of all of those.
Priority ⇒ 2. Medium
Type ⇒ Enhancement
Summary ⇒ Inconsistent vacation excludes
Queue ⇒ Ingo
State ⇒ Feedback
We should agree on a common policy for all drivers.
imap: doesn't have vacation at all
sieve: excludes list-help", "list-unsubscribe", "list-subscribe",
"list-owner", "list-post", "list-archive", "list-id" headers and
"precedence" headers if "list", "bulk". It used to to exclude if
X-Spam-Flag header is YES. I removed that before I noticed that we are
so inconsistent.
procmail: excludes X-Spam-Flag: YES (introduced with the timed
vacation patch) and FROM_DAEMON
maildrop: doesn't exclude anything.
ticket #5912add excludes forList-Id:|Prececence:.*(bulk|junk|list)|From:.*(postmaster|administrator)