4 messages in net.sourceforge.lists.courier-usersRe: [courier-users] About a multiple ...
FromSent OnAttachments
fuk...@f28.sytes.netDec 13, 2007 5:06 pm 
Sam VarshavchikDec 13, 2007 5:30 pm 
fuk...@f28.sytes.netDec 13, 2007 7:57 pm 
Sam VarshavchikDec 13, 2007 8:05 pm 
Actions with this message:
Paste this link in email or IM:
Paste this link in email or IM:
Atom feed for this thread
Paste this URL into your reader:
Subject:Re: [courier-users] About a multiple receptionActions...
From:Sam Varshavchik (mrs@courier-mta.com)
Date:Dec 13, 2007 8:05:53 pm
List:net.sourceforge.lists.courier-users

fuk@f28.sytes.net writes:

Thank you for the relpy.

'MailspoolA' is running an older version of Courier. Upgrade both machines to run the same version.

We assure you that they both are running on same versions(3.0.8). However, yes, they'er running older version of Courier-IMAP.

We did not find anything related on regarding matter on release note from ver.4.0 up to current 4.3.0. Will this problem be solved if we did in fact upgrade both server? Considering it wasn't a problem with operating on different versions.

If your original diagram indicates that both MailspoolA and MailspoolB are accessing the same underlying mailboxes, then MailspoolA must be running Courier-IMAP version 2.0, or earlier, if I reviewed the changelogs correctly. The UIDL format you show for MailspoolA is only generated by Courier-IMAP 2.0. Later versions report this UIDL only for existing pre-2.1 mail. But since your MailspoolB UIDLs are from Courier-IMAP 2.1+, then, as long as both A and B are accessing the same spool, MailspoolA running Courier-IMAP 2.0 is the only possible explanation, as far as I can see.

Updating now to 4.3.0 will make sure that you are running the exact same version on both servers. There have been many bugs fixed since then, and the IMAP server runs much faster now.