2 May
2011
2 May
'11
10:17 a.m.
Hello
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: "internetteam@"@standardbank.co.za;
(mitm.application.djigzo.james.mailets.Log) [Spool Thread #2]
Regards
Andreas
2 May
2 May
10:22 a.m.
On 01/-10/-28163 08:59 PM, lst_hoe02(a)kwsoft.de wrote:
Hello
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:
"internetteam@"@standardbank.co.za;
(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)
Kind regards,
Martijn
--
Djigzo open source email encryption
10:29 a.m.
Zitat von Martijn Brinkers <martijn(a)djigzo.com>om>:
On 01/-10/-28163 08:59 PM, lst_hoe02(a)kwsoft.de wrote:
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?
Regards
Andreas
Hello
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:
"internetteam@"@standardbank.co.za;
(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)
10:37 a.m.
On 01/-10/-28163 08:59 PM, lst_hoe02(a)kwsoft.de wrote:
Zitat von Martijn Brinkers
<martijn(a)djigzo.com>om>:
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?
On 01/-10/-28163 08:59 PM, lst_hoe02(a)kwsoft.de
wrote:
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? Hello
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:
"internetteam@"@standardbank.co.za;
(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) Maybe it is possible to generate a alert per mail to
some admin
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.
Kind regards,
Martijn
--
Djigzo open source email encryption
10:47 a.m.
On 01/-10/-28163 08:59 PM, Martijn Brinkers wrote:
On 01/-10/-28163 08:59 PM, lst_hoe02(a)kwsoft.de wrote:
I have a test gateway which receives lots (thousands a day) of spam (all
incoming email is immediately delivered to /dev/null) to test the
gateway against all kinds of malformed email. In 1.5 years time no email
has ever been stored in the error spool. That's why I am curious what
the email looked like :)
Kind regards,
Martijn
--
Djigzo open source email encryption
Zitat von Martijn Brinkers
<martijn(a)djigzo.com>om>:
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. On 01/-10/-28163 08:59 PM, lst_hoe02(a)kwsoft.de
wrote:
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? Hello
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:
"internetteam@"@standardbank.co.za;
(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)
10:31 a.m.
On 01/-10/-28163 08:59 PM, lst_hoe02(a)kwsoft.de wrote:
Hello
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:
"internetteam@"@standardbank.co.za;
(mitm.application.djigzo.james.mailets.Log) [Spool Thread #2]
It's strange that that is the only error message you can find. Can you
search for 256ee399-8e31-4a15-b7f1-ccf7c8784ada (a unique identifier
given to the message when the message first enters the system) in the
MPA logs (using the GUI or on the command line using grep) and send me
the results?
Kind regards,
Martijn
--
Djigzo open source email encryption
1:15 p.m.
On 01/-10/-28163 08:59 PM, Martijn Brinkers wrote:
On 01/-10/-28163 08:59 PM, lst_hoe02(a)kwsoft.de wrote:
It turned out to be caused by an upstream virus scanner that somehow
didn't accept the message. This does not happen with the default install
of Djigzo since it does not internally deliver email to an external
virus scanner.
Messages are only stored in the error spool on exceptional situations.
Sending warning 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. I think it's therefore better to use
external monitoring tools like Nagio, Cati etc. to check the spool,
back-end etc.
A script is available that can be used to check the spools and
functionality of the back-end. The script to use is:
djigzo/scripts/check_backend.sh
For example to check the number of items in the error spool, you should
call:
$ check_backend.sh mpasize error
and for the outgoing spool use:
$ check_backend.sh mpasize outgoing
The script contains some notes on how to setup a port with xinetd to
make it possible to query the settings via the network. This can then be
used by your monitoring tool to monitor the setting and send warnings on
a certain level.
Kind regards,
Martijn
--
Djigzo open source email encryption
Hello
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:
"internetteam@"@standardbank.co.za; ./check_backend.sh mpasize outgoing
(mitm.application.djigzo.james.mailets.Log) [Spool Thread #2]
It's strange that that is the only error message you can find. Can you
search for 256ee399-8e31-4a15-b7f1-ccf7c8784ada (a unique identifier
given to the message when the message first enters the system) in the
MPA logs (using the GUI or on the command line using grep) and send me
the results?
3917
days inactive
3917
days old
6 comments
2 participants
participants (2)
-
lst_hoe02＠kwsoft.de -
Martijn Brinkers