InterIMAP Work Item Rss Feed

Created Issue: Exchange 2010 IMAP [7979]

SearchForTheCode — Tue, 25 Jan 2011 10:58:02 GMT

When connection on a exchange server 2010 i get the following IMAP exception.

InterIMAP.IMAPException: Error in the Application.
bei InterIMAP.IMAPBase.SendAndReceive(String command, ArrayList& sResultArray)
bei InterIMAP.IMAP.ProcessFolders(String rootFolder)
bei InterIMAP.IMAPClient.Logon()

Worked with other Exchange Versions over IMAP without any problem.
I can access the mailbox over outlook perfectly.

Created Issue: Attachment problem [7766]

pdfforge — Mon, 13 Dec 2010 23:09:13 GMT

My attachments are not detected on the server. After some hacking the proper body parts are recognized, but the filename is missing. I can create a test account if requested. The server uses dovecot.

Commented Issue: IMAPConnection Infinite Loop [6307]

garnerbri — Tue, 08 Jun 2010 02:07:30 GMT

There is a major bug in the IMAPConnection Class.
Since the ReadLine Method ignores the IOException, the ExecuteCommand Method can end up stuck in an infinite loop filling up the memory.

If the connection is lost, the ReadLine Method always returns an Empty String, resulting in the ExecuteCommand looping infinite and filling up the memory by adding empty strings to the resultArray.
Comments: ** Comment from web user: garnerbri **

Attached is a fix that makes the app crash instead of hang, which is better but not ideal. The issue still needs a better resolution. The attached changes cause a crash in our app instead of a hang, as well as some other minor changes.

Created Issue: IMAPConnection Infinite Loop [6307]

nvollmar — Mon, 31 May 2010 06:46:00 GMT

Created Issue: MessageStructureProcessor.ProcessResult() throws an exception when processing a "* 3 FETCH (FLAGS (\\Seen))" result. [5905]

GreenLeaf — Fri, 30 Apr 2010 20:52:08 GMT

I occasionally receive an ArgumentOutOfRangeException in InterIMAP.Common.Processors.MessageStructureProcessor.ProcessResult() when using a FullMessageRequest instance to download a message. I am using Revision 43840.

The exception occurs when looping over CmdResult.Results. The exception occurs when when the message being downloaded includes the following entry in the CmdResult.Results property:

"* 3 FETCH (FLAGS (\\Seen))"

The ProcessResult() method assumes that all CmdResult.Results entries will contain the text "BODYSTRUCTURE" which in this case it doesn't. I'm not yet familiar enough with the code, or the IMAP protocol, to write my own patch -- I'm not sure what the correct way to handle this situation is.

Created Issue: Date not being parsed correctly. Resulting in Null Date for IMAPMessage [5787]

connormurphy — Thu, 15 Apr 2010 10:06:02 GMT

Jason,

I have isolated a consistent email that causes this error. The date field in IMAPMessage also equates to Null {_date = {01/01/0001 00:00:00} when I receive messages from Capital One.
I've included the raw header below for your reference.

Connor

Delivered-To: XXX@gmail.com
Received: by 10.204.32.143 with SMTP id c15cs100995bkd;
Mon, 12 Apr 2010 05:42:43 -0700 (PDT)
Received: by 10.223.143.67 with SMTP id t3mr2643652fau.16.1271076162051;
Mon, 12 Apr 2010 05:42:42 -0700 (PDT)
Return-Path: <1ad488872layfivciaqq2alaaaaaabtalkwmbcwx5tqyaaaaa@email.capitalone.com>
Received: from bigfootinteractive.com (arm-ei65.bigfootinteractive.com [216.33.63.65])
by mx.google.com with SMTP id 1si8334427fkt.11.2010.04.12.05.42.36;
Mon, 12 Apr 2010 05:42:41 -0700 (PDT)
Received-SPF: pass (google.com: domain of 1ad488872layfivciaqq2alaaaaaabtalkwmbcwx5tqyaaaaa@email.capitalone.com designates 216.33.63.65 as permitted sender) client-ip=216.33.63.65;
Authentication-Results: mx.google.com; spf=pass (google.com: domain of 1ad488872layfivciaqq2alaaaaaabtalkwmbcwx5tqyaaaaa@email.capitalone.com designates 216.33.63.65 as permitted sender) smtp.mail=1ad488872layfivciaqq2alaaaaaabtalkwmbcwx5tqyaaaaa@email.capitalone.com; dkim=pass header.i=@email.capitalone.com
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=email.capitalone.com;
s=ei; t=1271075908; bh=8mvgOj8ZRXaLeyJ1iZkTeC8judo=; h=From:Subject:
To; b=Qd1Yi4JDkCBbObZtD0GkBPWRRpv7ekF/wK+PQnGRvnnL2+MC1Tw/c2Uo1RcE
v65SyRE1FxigfqRChyYSsS/sjVzVzUDkA+esUV2fk0b9CcQf++sP9qc6UxI0Aip42gR
CF3COvgqLVQWQkaaWTGLCBHU+wsaGxwnnBU4/jjQSS9c=
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
s=bfi; d=email.capitalone.com;
b=COt3U8alm/63h5ryTf4+ilPqgxwAGPugEmvaSbDebw9/Jlp2ZFclpHhy3EbeBb9T;
Reply-To: "capitalone" <1ad488872layfivciaqq2alaaaaaabtalkwmbcwx5tqyaaaaa@email.capitalone.com>
Bounces_to: capitalone.1ad488872layfivciaqq2alaaaaaabtalkwmbcwx5tqyaaaaa@email.capitalone.com
Message-ID: <1ad488872layfivciaqq2alaaaaaabtalkwmbcwx5tqyaaaaa.6399.27544.pimailer53.DumpShot.1@email.capitalone.com>
X-SS: 1-1-9250280-518933058
X-BFI: 1ad488872layfivciaqq2alaaaaaabtalkwmbcwx5tqyaaaaa
Date: Mon, 12 Apr 2010 08:38:28 EDT
From: Capital One <capitalone@email.capitalone.com>
Subject: XXX, here's your April rewards update
To: XXX@gmail.com
MIME-Version: 1.0
Content-Type: multipart/alternative;
boundary="ABCD-1ad488872layfivciaqq2alaaaaaabtalkwmbcwx5tqyaaaaa-EFGH"

--ABCD-1ad488872layfivciaqq2alaaaaaabtalkwmbcwx5tqyaaaaa-EFGH
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable

Commented Issue: MessageHeader EmailAddress list not being parsed correctly [5210]

connormurphy — Tue, 13 Apr 2010 09:50:31 GMT

Some email addresses are not being parsed correctly in the TO, CC, BCC collections.

In one example the parser cannot break up the 3 addresses on the TO field.
The parsed message returns 1 email address rather than the expected 3 in the TO field collection. The actual result looks like am address string = 'dave@yahoo.com, steve@hotmail.com, brian@gmail.com' and display name = <'dave@yahoo.com, steve@hotmail.com, brian@gmail.com'>. Another side effect is that it also returns an empty email address in the BCC collection.

I'm not sure what the root cause is yet, but I suggest that the Parser checks to ensure that only one @ can exist in an email address. Equally an error should be handled when an email address is empty of poorly formated.
Comments: ** Comment from web user: connormurphy **

Hi Jason,

Here is how I'm currently trying to connect. It sort of works... but I get some very inconsistent behaviours and the afterdate filter does not appear to work correctly as it usually returns a collection of Null messages. Could you give an example of how to do this correctly using async? This would be really appreciated

Connor

public IMAPMessageCollection getMessages(EmailLogin emailLogin)
{
IMAPConfig config = new IMAPConfig("imap.gmail.com", emailLogin.Username, emailLogin.Password, true, true, "");
IMAPClient client = null;
client = GetClient(config, client);

IMAPMessageCollection collection = new IMAPMessageCollection();
IMAPSearchQuery query = new IMAPSearchQuery();
query.AfterDate = emailLogin.LastUpdated.AddMilliseconds(1).ToString();

IMAPFolder InboxFolder = client.GetSingleFolder("INBOX");
IMAPFolder SentFolder = client.GetSingleFolder("[Gmail]");
IMAPFolder SentSubFolder = SentFolder.SubFolders["Sent Mail"];

collection.AddRange(InboxFolder.Search(query).Messages);
collection.AddRange(SentSubFolder.Search(query).Messages);

return collection;
}

Commented Issue: MessageHeader EmailAddress list not being parsed correctly [5210]

connormurphy — Mon, 12 Apr 2010 16:13:45 GMT

Hi Jason,

I'm trying to reproduce it right now but I'm having difficulties connecting to Gmail using the newer Async methods.
Could you post an end to end example where a user would connect to Gmail, and return a collection of messages for the Inbox and Sent sub folder.
The example would also need to have a query that limited the search using an 'after date' i.e. get me all emails since date X

Once I get that up and working I will be able to send on the specific To,CC, and BCC texts. I've also had bugs around the date format as the odd email data returns null.

Thanks again,
Connor

Closed Issue: misspelling code. [5700]

JasonMiesionczek — Wed, 07 Apr 2010 18:42:32 GMT

Very small bug, but I noticed in the IMAPConfig.cs line: 200 the param being passed in for password is spelled passowrd, instead of password.
Comments:

Thanks for point that out. Parameter name has been updated and will be available in the next build.

Commented Issue: MessageHeader EmailAddress list not being parsed correctly [5210]

JasonMiesionczek — Wed, 07 Apr 2010 18:39:41 GMT

Yeah, the Async client is currently the only supported client.

In regards to your original issue, would you be able to provide the actual text that is returned by the server for the TO, CC, and BCC fields? i would like to see how it looks and make the necessary adjustments to account for this variance.

Thanks.

P.S. I will be adding some more documentation within the next few days as time permits. Is there any specific topic you would like me to cover?

Created Issue: misspelling code. [5700]

jtstroup — Wed, 07 Apr 2010 17:51:46 GMT

Very small bug, but I noticed in the IMAPConfig.cs line: 200 the param being passed in for password is spelled passowrd, instead of password.

Commented Issue: MessageHeader EmailAddress list not being parsed correctly [5210]

connormurphy — Tue, 06 Apr 2010 16:31:38 GMT

Hi Jason,

I'm using Async. Is that the best version to use? I presumed this was the most up to date version of the code.
Also do you think there will be anymore documentation soon. I'm struggling to find good async examples and I don't want to change libraries :)

Thanks,
Connor

Closed Issue: CreateFolder - _client not instantiated [2181]

JasonMiesionczek — Mon, 05 Apr 2010 18:11:18 GMT

Trying to do some more advanced InterIMAP stuff, I ran into the following issue:

I create a new folder (folderX) using client.CreateFolder.

Then I want to add 2 subfolders to that but I get an error:

IMAPClient client = new IMAPClient(config, null, 5);
client.CreateFolder("FolderX");
//this fails because IMAPFolder._client is not instantiated:
client.Folders["FolderX"].CreateFolder("Processed", false);
client.Folders["FolderX"].CreateFolder("Unknown", false);

it fails because the _client property of the new folder FolderX is null while it should point to client (as fas as I could figure out)

I updated the code in IMAPClient to this and now it works for me:

public void CreateFolder(string name)
{
if (OfflineMode)
{
Log(IMAPBase.LogTypeEnum.WARN, "Cannot create folders in offline mode.");
return;
}

string cmd = "CREATE \"{0}\"\r\n";
ArrayList result = new ArrayList();
string newFolder = String.Format("{0}", name);
_imap.SendAndReceive(String.Format(cmd, newFolder), ref result);
if (result[0].ToString().Contains("OK"))
{
IMAPFolder oNewFolder = new IMAPFolder();
oNewFolder.FolderName = name;
oNewFolder.FolderPath = newFolder;
oNewFolder.ParentFolder = null;
oNewFolder.ParentFolderName = String.Empty;

//MODIFIED:
oNewFolder.SetClient(this);
//END MODIFICATION

_folders.Add(oNewFolder);
UpdateCache(true);
Log(IMAPBase.LogTypeEnum.INFO, String.Format("Folder {0} created successfully.", name));
}
else
{
_imap.Log(IMAPBase.LogTypeEnum.ERROR, "Folder could not be created (" + result[0].ToString()+")");
}

}

and in the IMAPFolder.CreateFolder version:

if (this._client != null)
oNewFolder.SetClient(this._client);

Is this a real bug or did I use the library in a way I shouldn't use it?
Comments:

This issue relates to the Synchronous client which is no longer supported. If you are still actively developing a project that uses this library, please consider switching to the Async client.

Closed Issue: Error in Getxml Method of IMAPMessage [2225]

JasonMiesionczek — Mon, 05 Apr 2010 18:10:08 GMT

Sorry My english is a Poor
In IMAP.cs Line 1473 is posible content.binarydata is null
if (disp.ToLower().Contains("inline") && (content.ContentId != null || content.ContentDescription != null ))
{
if (content.BinaryData == null)
continue;
It's OK
Thanks
Enrique de la Calle
enrique at delacalle.net
Comments:

This issue is related to the Synchronous client which is no longer supported. If you are still using the library in a project, please consider switching to the Async client.

Closed Issue: Exception generated on messages that have extra space in date [3814]

JasonMiesionczek — Mon, 05 Apr 2010 18:05:53 GMT

Some dates on messages aren't well-formed which causes an exception in the MessageHeaderProcessor. An example might be a date that starts with "Tue, 20", notice the double space between the comma and number.
Comments:

Thank you for your feedback. I have implemented a more robust and safer date parser which should support more possible date formats and won't throw any exceptions. It will be included in the next release.

Closed Issue: Message.DateReceived not populated correctly [3815]

JasonMiesionczek — Mon, 05 Apr 2010 16:00:20 GMT

This property seems to always be a copy of DateSent and isn't properly populated.
Comments:

This is because in many cases, the message header information only contains a single "Date:" field, which doesn't specify whether it's the sent date or the received date.

Closed Issue: MessageHeaderCommand should use BODY.PEEK [4254]

JasonMiesionczek — Mon, 05 Apr 2010 12:24:25 GMT

I had an issue with Gmail recently where all messages I was receiving had the \Seen flag set. It seems sometime in August they changed their IMAP implementation to implicitly set the \Seen flag when the FETCH (FLAGS BODY[HEADER]) command is sent. I changed my code to FETCH (FLAGS BODY.PEEK[HEADER]) and this fixed the issue. According to the IMAP spec this is the correct way to do this:

BODY.PEEK[<section>]<<partial>>
An alternate form of BODY[<section>] that does not
implicitly set the \Seen flag.

http://james.apache.org/server/rfclist/imap4/rfc2060.txt (Search for "[Page 43]")
Comments:

MessageHeaderCommand has been updated to reflect this. Thanks for your contribution.

Commented Issue: MessageHeader EmailAddress list not being parsed correctly [5210]

JasonMiesionczek — Mon, 05 Apr 2010 12:17:09 GMT

Which client are you using and seeing this problem, synchronous or asynchronous?

Closed Issue: Invalid Attachment Name Handling [5220]

JasonMiesionczek — Mon, 05 Apr 2010 12:14:00 GMT

For whatever reason, I seem to get messages with a colon (@":") in the attachment file name. This caused an exception on writing the file to disk with a filestream. Clearly, this was a filename issue, as my operating system, Windows, does not accept file names with colons (@":") in the file name. I was using the async IMAPMailboxManger to save attachments. There are a ton of ways to handle this exception. The best would probably be to handle this at the point that the data goes into the program -- when the attachment file name is parsed, but I chose to change the code in the IMAPMailboxManager save method. One fix for this is to change the code in the InterIMAP.Asynchronous.Client.IMAPMailboxManager.SaveAttachment()

Here is my updated code for the method that fixes file name issue when saving the file:

public void SaveAttachment(IMessageContent content, string path)
{
string fn = content.ContentFilename;
//MUST ERROR-PROOF INCOMING PARAMETER "content.ContentFilename" STRING PROPERTY VALUE:
fn = fn.Replace(@"\", @"_");
fn = fn.Replace(@"/", @"_");
fn = fn.Replace(@":", @"_");
fn = fn.Replace(@"*", @"_");
fn = fn.Replace(@"?", @"_");
fn = fn.Replace("\"", @"_");
fn = fn.Replace(@"<", @"_");
fn = fn.Replace(@">", @"_");
fn = fn.Replace(@"|", @"_");

//CONSTRUCT FILE PATH STRING, BUT ONLY AFTER ERROR CHECKING INCOMING PARAMETERS
string p = String.Format("{0}\\{1}", path.TrimEnd('\\'), fn);

//CREATE AND WRITE THE FileStream
FileStream fstream = new FileStream(p, FileMode.Create);
fstream.Write(content.BinaryData, 0, content.BinaryData.Length);
fstream.Close();
}
Comments:

i included your fix into the library, but i wrote the replace logic as this:

string fn = content.ContentFilename;
fn = Regex.Replace(fn, "[\\/:\*?\"<>|]+", "_");

Closed Issue: InterIMAPGUITest fails - if email does not contain a "Content-Type" [5430]

JasonMiesionczek — Mon, 05 Apr 2010 02:19:35 GMT

Was testing InterIMAP-Async - using InterIMAPGUITest. but did get an exception when reading a mail that was a non-deliverable message (From Exchange server).
The mail contained the original email - and did not contain any Content-Type charset parameter:

Dirty fix in MessagePartProcessor.cs - method ProcessResult

Line 100 - 110
<code>
if (isHTML)
content.HTMLData = sb.ToString().Trim().TrimEnd(')');
else
{
string preEncoded = sb.ToString().Trim().TrimEnd(')');
// Dirty Fix - START
if (string.IsNullOrEmpty(content.Charset))
content.Charset = "utf-8";
// Dirty Fix - END
content.TextData = Decode(preEncoded, Encoding.GetEncoding(content.Charset));
}

</code>
Comments:

thank you for your contribution. i will put this in for now and see if there is a better way to detect and account for this scenario.