On 01/-10/-28163 08:59 PM, lst_hoe02(a)kwsoft.de wrote:
Zitat von Martijn Brinkers
On 01/-10/-28163 08:59 PM, lst_hoe02(a)kwsoft.de
today i discovered that a mail was moved by Djigzo/James to the error
spool and not get delivered. It is obvious some malformed spam but i
don't like mail to dissapear at all.
The error simply was
02 May 2011 05:11:10 | ERROR **** Message is stored in ERROR spool ****
| MailID: 256ee399-8e31-4a15-b7f1-ccf7c8784ada; Originator: <>; Sender:
(mitm.application.djigzo.james.mailets.Log) [Spool Thread #2]
Messages should only be stored in the error spool when a message is so
badly malformed that Javamail cannot handle them.
Are you sure the message is not stored in the error spool? (see Queues
-> MPA error)
Of course it is stored in the error spool but for normal operation no
one is looking at the logs to see if something was moved out of the way.
I prefer that Djigzo/James would simply pass it on to Postfix if
Javamail is not able to do anything useful with it. Maybe it is possible
to generate a alert per mail to some admin account in this case?
Normally every email should be delivered even if it's badly malformed.
The error handler is a last resort for cases that are not handled. If I
know what content of the email actually caused this I can perhaps fix
why it didn't handle the email more gracefully.
Can you send me the contents of the email?
Maybe it is possible to generate a alert per mail to
account in this case?
Yes this is something I considered to to. However, the reason I did not
do this yet is that normally no email should ever reach the error spool
and if an email is stored in the error spool than it means that
something unexpectedly has happened. Sending email when something
something unexpectedly has happened can lead to bigger problems. For
example a message can be send to error because of hardware or OS problems.
Djigzo open source email encryption