On 1/14/11 12:24 AM, Mark (Lunatechnologies) wrote:
Thanks Jeroen,
Finally cracked it tonight. You're right - the content filter itself
was unnecessary and was being run against every mail in and out.
so removed that and just left the vacation transport to handle
anything with an @autoreply.domain.com address (which I create in the
alias table with a custom script)
That is fine as far as it goes, but you need to be aware that it changes
the delivery address.
Depending on your scenario, that may actually be desirable, since you
can reject that autoresponder domain at ingress so replies TO the
autoresponder will not be processed unnecessarily.
mail from joe -> autoresponder "joe isn't here!" -> reply to joe ->
"still not here!" -> particularly braindead end-user replies again ->
"not gonna be here because you want me to be!"
Your solution can prevent this scenario by rejecting the autoreply
domain outright.
There's more than one way to crack these nuts.
--
J.
