Hi folks,
I just interrupted a mail loop in which a DirectAdmin "vacation message" was participating. I broke the loop by removing the "vacation message", waiting a few minutes, and then recreating it.
The incoming mails were not from the "<>" null sender (which is bad - envelope sender for autoresponses should be "<>"), although I see that the autoreplies going out from DirectAdmin/exim *were* from "<>" - that's good.
I'm pretty sure I remember the old unix "vacation" program kept a database of addresses to which it had autoreplied and would not autoreply to an address it had seen within the last n days (n=7 by default, IIRC). I would suggest that DirectAdmin's "vacation messages" and "autoresponders" features should use something similar to prevent forwarding loops like this.
Thanks.
I just interrupted a mail loop in which a DirectAdmin "vacation message" was participating. I broke the loop by removing the "vacation message", waiting a few minutes, and then recreating it.
The incoming mails were not from the "<>" null sender (which is bad - envelope sender for autoresponses should be "<>"), although I see that the autoreplies going out from DirectAdmin/exim *were* from "<>" - that's good.
I'm pretty sure I remember the old unix "vacation" program kept a database of addresses to which it had autoreplied and would not autoreply to an address it had seen within the last n days (n=7 by default, IIRC). I would suggest that DirectAdmin's "vacation messages" and "autoresponders" features should use something similar to prevent forwarding loops like this.
Thanks.