| Author |
|
InnoDev
Newbie
Joined: 02 July 2008
Location: United States
Online Status: Offline
Posts: 1
|
| Posted: 02 July 2008 at 7:16am | IP Logged
|
|
|
Hello,
Whenever an exception occurs will using MailBee.ImapMail.Imap.DownloadEntireMessage() and the response is not what was expected, MailBee seems to automatically disconnect from the server, even tho I'm catching the exceptions and I'm not calling the Disconnect() method in the catch.
I couldn't find anything in the documentation that indicates that this is intentional or normal behavior, nor did I find anything that discussed how to disable that behavior.
My problem with this is that when download a number of messages (by ID) in batch using a For/Next loop (for example), this disconnect causes the rest of the messages to fail to download. If a message causes an exception, I'd rather just skip that particular message, log that action along with the exception, and keep going.
Is there anyway to disable the automatic disconnect? Or do I have to add additional code log that user back on each iteration of the loop if it's been disconnected?
Here is an excerpt from the log:
[17:33:49.61] [INFO] [000D] [IMAP-00................] Will download envelopes.
[17:33:49.61] [SEND] [000D] [IMAP-00................] MBN00000010 FETCH 7 (UID RFC822.SIZE BODY[])\r\n
[17:33:49.65] [INFO] [000D] [IMAP-00................] Warning: The particular item of the response data cannot be parsed. The response string: (UID 51799 RFC822.SIZE 1492 BODY[] {1492}\r\nReturn-Path: <wfxrqipylhm@bowlingfans.com> Tue Jul 01 01:55:19 2008\r\nReceived: from p54900871.dip0.t-ipconnect.de [84.144.8.113] by mail.innomarkcom.com with SMTP;\r\n Tue, 1 Jul 2008 01:55:19 -0400\r\nReceived: from [84.144.8.113] by bowlingfans.com; Tue, 1 Jul 2008 06:53:23 +0100\r\nDate: Tue, 1 Jul 2008 06:53:23 +0100\r\nFrom: "Burl Keen" <wfxrqipylhm@bowlingfans.com>\r\nX-Mailer: The Bat! (v3.0.1.33) Educational\r\nReply-To: wfxrqipylhm@bowlingfans.com\r\nX-Priority: 3 (Normal)\r\nMessage-ID: <685469007.43957404271301@bowlingfans.com>\r\nTo: blaird@prestigedisplay.com\r\nSubject: X-SPAM-LOW: Be the King\r\nMIME-Version: 1.0\r\nContent-Type: text/plain;\r\n charset=windows-1250\r\nContent-Transfer-Encoding: 7bit\r\nX-RBL-Warning: SORBS-DUHL: "Dynamic IP Addresses See: http://www.sorbs.net/lookup.shtml?84.144.8.113"\r\nX-DECLUDE -SPAM-SNIFFER: (FAILED) - Message failed SNIFFER: 52.\r\nX-DECLUDE-SPAM-WEIGHT10: (FAILED) - Weight of 16 reaches or exceeds the limit of 10.\r\nX-DECLUDE-SPAM-WEIGHT14: (FAILED) - Weight of 16 reaches or exceeds the limit of 14.\r\nX-Declude-Sender: wfxrqipylhm@bowlingfans.com [84.144.8.113]\r\nX-Declude-Spoolname: 41162080.eml\r\nX-Declude-Note: Scanned by Declude 4.2.20 for spam. "http://www.declude.com/x-note.htm"\r\nX-Declude-Scan: Incoming Score [16] at 01:55:33 on 01 Jul 2008\r\nX-Declude-Fail: SORBS-DUHL [4], SNIFFER [12], WEIGHT10 [10], WEIGHT14 [14], ZEROHOUR [0]\r\nX-Country-Chain: GERMANY->destination\r\n\r\nConquer and rule woman's love!\r\nThe best remedy ever!\r\n\r\nhttp://naperik.com/v/.
[17:33:49.67] [RECV] [000D] [IMAP-00................] * 7 FETCH (UID 51799 RFC822.SIZE 1492 BODY[] {1492}\r\n
[17:33:49.67] [RECV] [000D] [IMAP-00................] [Literal of length 1492.]
[17:33:49.67] [RECV] [000D] [IMAP-00................] k.com/v/\r\n [Total 1555 bytes received.]
[17:33:49.67] [INFO] [000D] [IMAP-00................] Error: Status line of the server response contains no status code. The response string: .
[17:33:49.67] [INFO] [000D] [IMAP-00................] Will disconnect from host "<IP removed for security reasons>".
[17:33:49.67] [INFO] [000D] [IMAP-00................] Disconnected from host "<IP removed for security reasons>".
|
| Back to Top |
|
| |
Alex
AfterLogic Support
Joined: 19 November 2003
Online Status: Offline
Posts: 2206
|
| Posted: 03 July 2008 at 4:24am | IP Logged
|
|
|
There are two kinds of MailBee exceptions. The first type corresponds to recoverable exceptions (like the server responded with negative reply). They do not cause automatic disconnect. Some exceptions, however, indicate something is so wrong that the mail session cannot continue because the response cannot be parsed and it's not possible to find out where the current response ends so that subsequent responses could be processed properly.
Could you provide us with the test account so that we would be able to check what's going on there? We'll check how this message is downloaded in Thunderbird/Outlook Express and in MailBee). You can send this info using our Request Support Form.
Regards,
Alex
|
| Back to Top |
|
| |
MailBee.NET Objects 
MailBee.NET Queue 
MailBee Objects 
WebMail Pro PHP 
AfterLogic Aurora 
MailSuite Pro for Linux 
Unified Messaging Solution 
Search
Register
Login
Topic: DownloadEntireMessage Exception
Privacy policy |
Refund policy