[Dovecot] Overloading IMAP Server

[Harford, Ken]

The correct delivery.

The error message is generated by the script. This is a set of perl
scripts from Nagios

check_email_delivery
check_imap_receive
check_smtp_send

I am going to see if I can delay the IMAP portion of the main script,

Thanks for the suggestion Steffen

Ken

On 1/22/13 4:04 AM, "Steffen Kaiser" <skdovecot at smail.inf.fh-brs.de> wrote:

>-----BEGIN PGP SIGNED MESSAGE-----
>Hash: SHA1
>
>On Mon, 21 Jan 2013, Harford, Ken wrote:
>
>>            I am having an issue with dovecot IMAP reading and writing
>>to 
>> one specific mailbox. I have a check email delivery script that sends
>
>What's the purpose of the verification:
>
>+ The prompt delivery?
>
>+ The delivery at all?
>
>+ The correct delivery?
>
>> out a email and then logs into dovecot to check if the mailbox that the
>> message has been delivered to. However, the servers that send these
>> messages send them in bunches depending on how many postfix spools it
>>is 
>> checking. So I could get 60 messages all being sent to 1 mailbox and
>> then having to read that same mailbox to check if the message actually
>> got delivered.
>>
>> I am getting a lot of  errors such as the following:
>>
>> Could not connect to IMAP server
>> imap failed: IMAP RECEIVE CRITICAL - Could not select INBOX
>
>Is this an error logged by Dovecot?
>
>> Any ideas as to what I can tweak in dovecot to allow these messages to
>>be verified.
>
>a)
>Wait a bit before logging into the IMAP server and check the messages
>sequentionally, not in parallel. E.g. your script could synchronize
>itself 
>with other parallel instances by a shared lock.
>
>b)
>Use mail_log and a script on the mail server monitoring Dovecot logs and
>register delivered message ids and/or recipient. Then figure out a good
>way to probe, if one pariticular message has been seen.
>- -or-
>make note of message id/recipient on the sender side, somehow push (ssh
>or 
>something) that information on regular basis to the mail server, where a
>script verifies that data.
>
>c) To verify the correct delivery: use some sort of checksumming.
>
>Kind regards,
>
>- -- 
>Steffen Kaiser
>-----BEGIN PGP SIGNATURE-----
>Version: GnuPG v1.4.11 (GNU/Linux)
>
>iQEVAwUBUP5WEF3r2wJMiz2NAQIatAgAjwZR1VGnyURuncLRNeeY0dBaqWzAUcNK
>g4YoiXB6NLxP6Xr/QO6Pw+6Q3sECJ0CJdwImOz56FVFNuiOygUMQ1dCdZ+Tpy9Wu
>xeAdobrkOo2uzgRnUh7+WLeZ8k32gZZztCAQA90uTvB3MBox+7J/P8/mApp+8/tr
>JKyhUy8RJIYXH+yrw/ZkbjmOSEEkf/wTPnBQcMKw5/4odha4lu+yEKx766mm0YCe
>3USL7eVqN0Q9FwUH+iCjnRJAdKRETP4CnfQpjVp7eiJX7HD0iNwhucDwf037Ev2N
>PG173M40pMllRyesjiV8gwOu8mAHu6V3QUiFJkYAKFOotUVO6xMrNQ==
>=SeaP
>-----END PGP SIGNATURE-----