On Fri, Aug 06, 2010 at 03:34:18PM +0200, Stevan Baji?? wrote: > On Fri, 6 Aug 2010 08:12:42 -0500 > Kenneth Marshall <k...@rice.edu> wrote: > > [...] > > One thing that would help to debug this problem is to save the mail that > > is sent to DSPAM to a folder unadulterated. Otherwise, it will be impossible > > to figure out where the problem lies. I have chased similar bugs in the > > past and they have not ended up being in postfix, but in one of the other > > mail transports. If we have a copy of the original message, we can see where > > it is mangled in transport and find the problem. > > > Looking at the position where the DSPAM headers are inserted I would say that > the message arrived correctly at Postfix and where processed correctly by > DSPAM. Else I can not explain why DSPAM was in the position to correctly > place it's X-DSPAM headers into the message. But somehow they end wrongly in > the quarantine or get wrongly transmitted from the quarantine. >
It helps to see the way the message looks at each stage is for things like .-escaping or to see if there is another contributing factor. Without knowing the original message going into DSPAM, the message passed out of DSPAM to the quarantine, ... it is all a guessing game. Would it be possible to see the message before DSPAM gets it and after it has been processed and is in the quarantine. Obviously, if it has a bad format it will not be re-deliverable. Cheers, Ken ------------------------------------------------------------------------------ This SF.net email is sponsored by Make an app they can't live without Enter the BlackBerry Developer Challenge http://p.sf.net/sfu/RIM-dev2dev _______________________________________________ Dspam-devel mailing list Dspam-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspam-devel
