> 1. Accepting NUL senders is correct. > 2. Accepting NUL senders on legit messages is needed. > Example, user sends to someone, but misspells. If you do not > accept NUL sender, how will the user get the notice. > (Assuming at some point it goes through a S&F or gateway.) 3. > Accepting NUL senders can be usefull for the admin, as it can > show when a joe job is under way and can show if there is a > problem occurring.
Thats why I've suggested: 1. Create an external test that moves all <> Nullsender messages in a temporary folder on the Imail-server. (separated for each domain or at least virtual Mailserver) 2. Check this folder regulary if there are more then x messages for the last y hours 3a. If no then requeue all files older then y-1 hours. 3b. If yes then move all files older then y-1 hours in the "ndr-hold" folder on the server. This can't be a 100% solution but it will work dinamically and hold most unwanted messages durring joe job periods but let pass occassional NDRs. A special case can be if a (legit!) NDR contains the original header from the (legit!) message that the local user has send to a non existant or mispelled remote address. So if the body of a NDR contains a string like "X-Note: Processed by eServicesforyou Virus/Spamfilter" it is very likely that this is a legit NDR because it was send out from your own server. In this case the external test could skip this messages and so avoid the delay that would be created by step 1-3 explained above. Markus --- [This E-mail was scanned for viruses by Declude Virus (http://www.declude.com)] --- This E-mail came from the Declude.JunkMail mailing list. To unsubscribe, just send an E-mail to [EMAIL PROTECTED], and type "unsubscribe Declude.JunkMail". The archives can be found at http://www.mail-archive.com.
