[EMAIL PROTECTED] 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.
pgpt9sU4ea32a.pgp
Description: PGP signature
------------------------------------------------------------------------- SF.Net email is sponsored by: Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace
_______________________________________________ courier-users mailing list [email protected] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
