Thanks a lot!

Konrad

Hi!

Is it possible to block the IMAP module for some mercury users. I have 10 users and 5 of them should just be able to access there mails through pop3. Is such a configuration possible?

Thanks,

Konrad

[quote user="Konrad Hammerer"]

Hi!

Is it possible to block the IMAP module for some mercury users. I have 10 users and 5 of them should just be able to access there mails through pop3. Is such a configuration possible?

Not sure this is possible via IMAP4 without blocking the port or something similar but if is there is a MAILBOXP.LCK file in the users new mail directory they will not be able to login via IMAP4.  I'd just create a zero byte mailboxp.lck file in the Mercury/32 mailbox directory of the ones I did not want to use IMAP4.

Thanks,

Konrad

Thanks!

That is what I need, but why does a file called MAILBOXP.LCK block IMAP access? POP3 will still be working, right?

Best,

Konrad

That is what I need, but why does a file called MAILBOXP.LCK block IMAP access? POP3 will still be working, right?

Mercury/32 and Pegasus Mail should never be accessing the same folders at the same time and so these is a lock file created to prevent multiple access.  This means that if you are using Pegasus Mail in the direct access it creates the lock file that is detecte by MercuryI and prevents access.  This does not affect POP3 since it's only working against the new mail directory and not Pegasus Mail folders.

Are there any side effects using TBird as mail client?

Thanks,

Konrad

[quote user="Konrad Hammerer"]

Are there any side effects using TBird as mail client?

None

Thanks,

Konrad