Davide wrote: >On Tue, 11 Feb 2003, Rob Arends wrote: >> >> I did some investigation here and gave up because I'm not skilled enough to >> do the programming shim between Xmail and UW-imap. >> >> The other thing is that it is a stdout application - not very useful in a >> w32 environment.
>The author gives also an inetd-like application to be used with the win32 >port. Doing this on win32 with a short-session kind of protocol like POP3 >will make performance to suck badly, but with IMAP you shoulb be fine >since its session is typically long. Yes, but I am not sure about the security of such an application. I'd rather not use the UW implementation anyway. Instead waiting for Xmail's IMAP. >> The correct thing here would be to disable Xmail's pop3 and use UW-imap to >> serve both pop3 and imap. >Users that adopt IMAP is very unlikely that will use POP3, for the simple >reason that once you fetch messages with POP3 you won't be able to manage >them with IMAP. So, it's better that you leave POP3 handled by XMail. In >this way you'll have a 'uniform' system to administer when XMail's IMAP >will come. Yes, but if I do not dictate what client they use, I must support both POP3 and IMAP. In this case I would have two data stores - one in xmail and one in UW-imap. My thinking was that you could drop all the incoming mail from xmail into uw-imap and then you have one data store and xmail is just transitory mail. >- Davide >- Rob :-) - To unsubscribe from this list: send the line "unsubscribe xmail" in the body of a message to [EMAIL PROTECTED] For general help: send the line "help" in the body of a message to [EMAIL PROTECTED]
