Alan Gerhard wrote:
There shouldn't be any risk of loop. You get past isLocalHost, then you notifySender... that message is sent to [EMAIL PROTECTED] with a sender of <>, because it is a server-side generated notice. This message then gets sent to you, it again goes through and fails isLocalHost, and then reaches notifySender which will swallow the message since it can't send a failure notice to <>.an email was sent to [EMAIL PROTECTED] with a sender of [EMAIL PROTECTED] but [EMAIL PROTECTED] does not exist so after the isLocalHost fails, i want to notifySender that the address does not exist, but in this case, i get this loop that goes on forever ...over the holidays, 100,000 mails took down my James 20A3 - yes James2100 is now up and running... i want to notify the sender that the address they used is faulty but do not want to be caught with the endless loop any suggestions on ways to process this ?? alan
I don't know how to configure the notify sender mailet off-hand, but that's logically how this situation is resolved.
Serge Knystautas
Loki Technologies
http://www.lokitech.com/
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
