> my > customers are looking to me for a solution, imperfect as it > may be in the end. I'm not by far sure about what to do.
Matt, In this case maybe it's a solution to define a separated filter file (BLOCKBOUNCES) and put in this filter file as much bounce error strings as you can find. Then if a customer asks you if it's possible to block all this bounces you can explain him that this is possible, but this can also block "real" error messages. If your customer agree's you can create a per-user or per-domain junkmail file that does something with it. (add weight, block, routeto, ...) Maybe it would be an idea to create something between John's Autowhite and Scott's Hijack: Hold any messages identified as NDR in a separated user directory. Then requeue them only if there are not more then X such messages in a certain time range. This would allow "regular" error reports going trough and dinamically filter all of them during Joe-Job periods. Maybe a problem can occur if a customer sends out a large number of e-mails and there are several bounces. But if this happens I assume that the addresses was not aquired "regulary" ;-) 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.
