Giuliano Gavazzi wrote:
may I make 2 or 3 observations?
Of course! :) OK, I'll use the new format you posted for the Question
part when I wiki it here in a little bit, thanks.
I do not see any measure to stop it from mailing mailing lists or other
message that should not be replied to. These can be taken from standard
autoresponder filters, but should be included in this filter before it
is published. Also, I would recommend that any of these aliases have a
lower spam threshold. Maybe I am too careful...
Understood, I hadn't really thought of that -- in my use-case scenario
of this, the only persons emailing it would be actual job seekers (how
would it end up on a mailing list?).
I think a good compromise is to use the same condition in the router
that is for the Vacation:
condition = "${if or {{match {$h_precedence:} {(?i)junk|bulk|list}} \
{eq {$sender_address} {}}} {no} {yes}}"
So that in full it looks like:
jobclosed_router:
driver = redirect
local_parts = jobclosed
condition = "${if or {{match {$h_precedence:} {(?i)junk|bulk|list}} \
{eq {$sender_address} {}}} {no} {yes}}"
allow_filter
file = /etc/mail/jobcfilter.txt
reply_transport = address_reply
user = mail
How does that look to you as a small anti-maillist prevention idea?
Would you have other suggestions to add?
-te
--
Troy Engel | Systems Engineer
Fluid, Inc | http://www.fluid.com
--
## List details at http://www.exim.org/mailman/listinfo/exim-users
## Exim details at http://www.exim.org/
## Please use the Wiki with this list - http://www.exim.org/eximwiki/
