I have the same experience and support the suggestion of Jeffrey. Dick At 20:15 20-05-2004, you wrote: >On Thursday 20 May 2004 13:09, Davide Libenzi wrote: > > On Thu, 20 May 2004, Roman Dusek wrote: > > > Hi, > > > > > > according to documentation: > > > > > > [RemoveSpoolErrors] > > > Indicate if mail has to be removed or stored in 'froz' directory after a > > > failure in delivery or filtering. > > > > > > I would suppose having "RemoveSpoolErrors" set to "1" there would be no > > > "froz" messages in message spool. In spite of this, there appear some > > > frozen messages in spool, mostly undelivered error messages from > > > [EMAIL PROTECTED] > > > > There's one special class of errors that always gets frozen. If A sends a > > message to MTA, and MTA accepts the message, then MTA fails to deliver the > > message *and* fails also to deliver the notification message to A, the > > message gets frozen. > > > >Davide, I've noticed the same thing on my severs and on my systems 100% of >the >mail meeting this criteria is spam. Can you include this scenario under the >RemoveSpoolErrors switch or add another parameter to turn this behavior off? > >Jeff > >- >To unsubscribe from this list: send the line "unsubscribe xmail" in >the body of a message to [EMAIL PROTECTED] >For general help: send the line "help" in the body of a message to >[EMAIL PROTECTED]
- To unsubscribe from this list: send the line "unsubscribe xmail" in the body of a message to [EMAIL PROTECTED] For general help: send the line "help" in the body of a message to [EMAIL PROTECTED]
