Topic: IMAP and Pegasus and bug reports

[Benny Nissen]

Hi all

Have been unable to get IMAP access from Pegasus for some time now. Have looked in the forum and seen that to install courier was the solution. I desided to report it as a bug to both the Pegasus group and the SME development team because I belive this is a bug that need to be fixed very soon. It shall work out of the box!

The response from Pegasus was quick and informative, They know about the problem but they strickly follow the IMAP RPC guidelines and they will not make special version to fix misbehaving servers.

The responce from SME was slow and had the following message:
"According to our records, the following request has been resolved" and then a link to my bug report track number.

This is not true in my belive - running 5.6 with update2. Outlook express is working with no problems!

Anyone have more information about this issue?
Benny

[Andrew Hodgson]

Hi,

I am also not totally satisfied with the Imap implementation in SME 5.6, and also found much grater responsed with Currier IMAP.  I did not report it as a bug, because I thought they already knew about the problem, but was dismayed to find no solution in update 2.

Thanks,
Andrew.

[Dan Brown]

Andrew, I really don't think Mitel would make such a major change as completely replacing the IMAP daemon as just an "update".  They are aware of bugs in the current version (though they seem to be fewer and less severe than in the version shipped with 5.5), and appear to be looking at alternative IMAP servers, but I wouldn't expect to see that change until they release a new version.

[Benny Nissen]

Actually They have release an update that allow Pegasus to work - sort of. I am unable to delete any mail, but I have a OK connection.

ftp://ftp.e-smith.org/pub/e-smith/CharlieBrady/5.6-imap/

As far as I remember the link is broken, you have to add "Contribs" or something like it

Benny

[Rich Lafferty]

Looks to be

ftp://ftp.e-smith.org/pub/e-smith/contrib/CharlieBrady/5.6-imap/

The "contrib" is important there; that's not (yet, at least) an SME Server
update, but rather a replacement RPM that Charlie put together while
working on the problem.