Re: Courier-imap Outlook problem - RE: Imap && imap-ssl && pop3-ssl
On February 12, 2004 11:31 pm, Debian ISP wrote: > One problem we keep having involves M$ Outlook clients. It seems that > something breaks with the communication between the server and Outlook > clients (or posssible corrupts the pst files created for each maildir). I haven't heard of that but most clients I have won't let go of pop3. When imap is used Outlook (and other mail clients) like to make quite a few connections to the server, it could be that some connections are getting refused. I've run into this and it's not an obvious problem. I usually increase MAXPERIP to 10, it's default is 4. The parameter is found in /etc/courier/imapd -- Fraser Campbell <[EMAIL PROTECTED]> http://www.wehave.net/ Georgetown, Ontario, Canada Debian GNU/Linux
Re: Courier-imap Outlook problem - RE: Imap && imap-ssl && pop3-ssl
On February 12, 2004 11:31 pm, Debian ISP wrote: > One problem we keep having involves M$ Outlook clients. It seems that > something breaks with the communication between the server and Outlook > clients (or posssible corrupts the pst files created for each maildir). I haven't heard of that but most clients I have won't let go of pop3. When imap is used Outlook (and other mail clients) like to make quite a few connections to the server, it could be that some connections are getting refused. I've run into this and it's not an obvious problem. I usually increase MAXPERIP to 10, it's default is 4. The parameter is found in /etc/courier/imapd -- Fraser Campbell <[EMAIL PROTECTED]> http://www.wehave.net/ Georgetown, Ontario, Canada Debian GNU/Linux -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Imap && imap-ssl && pop3-ssl
On Thu, Feb 12, 2004 at 07:16:26PM -0600, Jose Alberto Guzman wrote: > Jonathan Matthews wrote: [...] > >I need to offer imap, imapssl and pop3ssl services. FWIW, imap would be > >localhost only, but -ssl services would be publically accessible. > > > >My reading thus far leads me towards Courier-imap with Exim 4 > >backported to stable so I can interface with ClamAV, but feel free to > >point out something important that I've missed. > > > >Do I need to have a different instance of the server running for each > >protocol? i.e. one listening on each port that the three services use > >as standard? > > > >Is there a server that would do the job with just one instance listening > >on all three ports? Would there be any advantages or disadvantages to > >this? I'm thinking locking/concurrency/that-sorta-thing. [...] > What we run here, is standard uw-imap and popa3d, with stunnel. Works > like a charm. I use postfix+uw-imap+ipopd from "testing" which supports ssl directly. We then use shorewall firewalling to limit access to the non-ssl ports. This uses inetd for the pop and imap servers, and mbox mailboxes. It works fine, and seems to be the "best" set up for mbox mailboxes. On another machine I use postfix+courier-imap-ssl+courier-pop-ssl+procmail. Procmail is used with a global /etc/procmailrc to make postfix deliver into Maildir mailboxes. Courier uses a heap of it's own daemons for everything, which I didn't like, but it seems to work OK. This seems to be the "best" setup for Maildir (flame suit on), with the possible exception of using something else instead of procmail for delivery. The big problem I found with Maildir is everything else seems to assume mbox (including the "you have mail" notification at the command line), and it's hard work to find and configure everything for it. I documented this stuff ages ago on the debian wiki last time I went through this; http://wiki.debian.net/index.cgi?EmailConfiguration http://wiki.debian.net/index.cgi?MaildirConfiguration Feel free to update these as you go :-) -- Donovan Baardahttp://minkirri.apana.org.au/~abo/
Re: Imap && imap-ssl && pop3-ssl
On Thu, Feb 12, 2004 at 07:16:26PM -0600, Jose Alberto Guzman wrote: > Jonathan Matthews wrote: [...] > >I need to offer imap, imapssl and pop3ssl services. FWIW, imap would be > >localhost only, but -ssl services would be publically accessible. > > > >My reading thus far leads me towards Courier-imap with Exim 4 > >backported to stable so I can interface with ClamAV, but feel free to > >point out something important that I've missed. > > > >Do I need to have a different instance of the server running for each > >protocol? i.e. one listening on each port that the three services use > >as standard? > > > >Is there a server that would do the job with just one instance listening > >on all three ports? Would there be any advantages or disadvantages to > >this? I'm thinking locking/concurrency/that-sorta-thing. [...] > What we run here, is standard uw-imap and popa3d, with stunnel. Works > like a charm. I use postfix+uw-imap+ipopd from "testing" which supports ssl directly. We then use shorewall firewalling to limit access to the non-ssl ports. This uses inetd for the pop and imap servers, and mbox mailboxes. It works fine, and seems to be the "best" set up for mbox mailboxes. On another machine I use postfix+courier-imap-ssl+courier-pop-ssl+procmail. Procmail is used with a global /etc/procmailrc to make postfix deliver into Maildir mailboxes. Courier uses a heap of it's own daemons for everything, which I didn't like, but it seems to work OK. This seems to be the "best" setup for Maildir (flame suit on), with the possible exception of using something else instead of procmail for delivery. The big problem I found with Maildir is everything else seems to assume mbox (including the "you have mail" notification at the command line), and it's hard work to find and configure everything for it. I documented this stuff ages ago on the debian wiki last time I went through this; http://wiki.debian.net/index.cgi?EmailConfiguration http://wiki.debian.net/index.cgi?MaildirConfiguration Feel free to update these as you go :-) -- Donovan Baardahttp://minkirri.apana.org.au/~abo/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Imap && imap-ssl && pop3-ssl
Hello, Have a look at SSLwrap. It enables SSL for the outside world but locally no encryption is used. Brian > [Sorry for the cross-post - I think it's applicable to both -isp and > -user.] > > I need to offer imap, imapssl and pop3ssl services. FWIW, imap would be > localhost only, but -ssl services would be publically accessible. > > My reading thus far leads me towards Courier-imap with Exim 4 > backported to stable so I can interface with ClamAV, but feel free to > point out something important that I've missed. > > Do I need to have a different instance of the server running for each > protocol? i.e. one listening on each port that the three services use > as standard? > > Is there a server that would do the job with just one instance listening > on all three ports? Would there be any advantages or disadvantages to > this? I'm thinking locking/concurrency/that-sorta-thing. > > How do you deal with this situation? Are there any gotchas I need to > know about? I'm guessing that using Maildirs will alleviate many of the > problems that mboxes would create ... > > Any pointers/suggestions/cluebats appreciated! > > jc > > -- > Have a nice cup of tea and a biscuit. Fifty-five million Britons can't > be wrong. Ooo - jammy dodgers!! > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact > [EMAIL PROTECTED]
Re: Imap && imap-ssl && pop3-ssl
Hello, Have a look at SSLwrap. It enables SSL for the outside world but locally no encryption is used. Brian > [Sorry for the cross-post - I think it's applicable to both -isp and > -user.] > > I need to offer imap, imapssl and pop3ssl services. FWIW, imap would be > localhost only, but -ssl services would be publically accessible. > > My reading thus far leads me towards Courier-imap with Exim 4 > backported to stable so I can interface with ClamAV, but feel free to > point out something important that I've missed. > > Do I need to have a different instance of the server running for each > protocol? i.e. one listening on each port that the three services use > as standard? > > Is there a server that would do the job with just one instance listening > on all three ports? Would there be any advantages or disadvantages to > this? I'm thinking locking/concurrency/that-sorta-thing. > > How do you deal with this situation? Are there any gotchas I need to > know about? I'm guessing that using Maildirs will alleviate many of the > problems that mboxes would create ... > > Any pointers/suggestions/cluebats appreciated! > > jc > > -- > Have a nice cup of tea and a biscuit. Fifty-five million Britons can't > be wrong. Ooo - jammy dodgers!! > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact > [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Courier-imap Outlook problem - RE: Imap && imap-ssl && pop3-ssl
We are using courier-imap in the configuration outlined on the marlow.dk website. One problem we keep having involves M$ Outlook clients. It seems that something breaks with the communication between the server and Outlook clients (or posssible corrupts the pst files created for each maildir). Has anyone else been faced with this problem? Since we are unable to convince our clients to move to Debian desktops with KMail or some other OSS alternative, some workaround for this issue would be greatly appreciated! Googling has not proven very helpful (only confirmed this as a problem). Thanks in advance, Hal -Original Message- From: Jose Alberto Guzman [mailto:[EMAIL PROTECTED] Sent: Thursday, February 12, 2004 8:16 PM To: Jonathan Matthews Cc: debian-user@lists.debian.org; debian-isp@lists.debian.org Subject: Re: Imap && imap-ssl && pop3-ssl Jonathan Matthews wrote: > [Sorry for the cross-post - I think it's applicable to both -isp and > -user.] > > I need to offer imap, imapssl and pop3ssl services. FWIW, imap would be > localhost only, but -ssl services would be publically accessible. > > My reading thus far leads me towards Courier-imap with Exim 4 > backported to stable so I can interface with ClamAV, but feel free to > point out something important that I've missed. > > Do I need to have a different instance of the server running for each > protocol? i.e. one listening on each port that the three services use > as standard? > > Is there a server that would do the job with just one instance listening > on all three ports? Would there be any advantages or disadvantages to > this? I'm thinking locking/concurrency/that-sorta-thing. > > How do you deal with this situation? Are there any gotchas I need to > know about? I'm guessing that using Maildirs will alleviate many of the > problems that mboxes would create ... > > Any pointers/suggestions/cluebats appreciated! > > jc > What we run here, is standard uw-imap and popa3d, with stunnel. Works like a charm. I know courier could handle everything with a single hand and half the overhead, maybe someday I'll migrate every mbox into maildir and set that up, but in the mean time, it does a pretty job. José PS please reply to debian-isp -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Courier-imap Outlook problem - RE: Imap && imap-ssl && pop3-ssl
We are using courier-imap in the configuration outlined on the marlow.dk website. One problem we keep having involves M$ Outlook clients. It seems that something breaks with the communication between the server and Outlook clients (or posssible corrupts the pst files created for each maildir). Has anyone else been faced with this problem? Since we are unable to convince our clients to move to Debian desktops with KMail or some other OSS alternative, some workaround for this issue would be greatly appreciated! Googling has not proven very helpful (only confirmed this as a problem). Thanks in advance, Hal -Original Message- From: Jose Alberto Guzman [mailto:[EMAIL PROTECTED] Sent: Thursday, February 12, 2004 8:16 PM To: Jonathan Matthews Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED] Subject: Re: Imap && imap-ssl && pop3-ssl Jonathan Matthews wrote: > [Sorry for the cross-post - I think it's applicable to both -isp and > -user.] > > I need to offer imap, imapssl and pop3ssl services. FWIW, imap would be > localhost only, but -ssl services would be publically accessible. > > My reading thus far leads me towards Courier-imap with Exim 4 > backported to stable so I can interface with ClamAV, but feel free to > point out something important that I've missed. > > Do I need to have a different instance of the server running for each > protocol? i.e. one listening on each port that the three services use > as standard? > > Is there a server that would do the job with just one instance listening > on all three ports? Would there be any advantages or disadvantages to > this? I'm thinking locking/concurrency/that-sorta-thing. > > How do you deal with this situation? Are there any gotchas I need to > know about? I'm guessing that using Maildirs will alleviate many of the > problems that mboxes would create ... > > Any pointers/suggestions/cluebats appreciated! > > jc > What we run here, is standard uw-imap and popa3d, with stunnel. Works like a charm. I know courier could handle everything with a single hand and half the overhead, maybe someday I'll migrate every mbox into maildir and set that up, but in the mean time, it does a pretty job. José PS please reply to debian-isp -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Imap && imap-ssl && pop3-ssl
Jonathan Matthews wrote: [Sorry for the cross-post - I think it's applicable to both -isp and -user.] I need to offer imap, imapssl and pop3ssl services. FWIW, imap would be localhost only, but -ssl services would be publically accessible. My reading thus far leads me towards Courier-imap with Exim 4 backported to stable so I can interface with ClamAV, but feel free to point out something important that I've missed. Do I need to have a different instance of the server running for each protocol? i.e. one listening on each port that the three services use as standard? Is there a server that would do the job with just one instance listening on all three ports? Would there be any advantages or disadvantages to this? I'm thinking locking/concurrency/that-sorta-thing. How do you deal with this situation? Are there any gotchas I need to know about? I'm guessing that using Maildirs will alleviate many of the problems that mboxes would create ... Any pointers/suggestions/cluebats appreciated! jc What we run here, is standard uw-imap and popa3d, with stunnel. Works like a charm. I know courier could handle everything with a single hand and half the overhead, maybe someday I'll migrate every mbox into maildir and set that up, but in the mean time, it does a pretty job. José PS please reply to debian-isp
Re: Imap && imap-ssl && pop3-ssl
Jonathan Matthews wrote: [Sorry for the cross-post - I think it's applicable to both -isp and -user.] I need to offer imap, imapssl and pop3ssl services. FWIW, imap would be localhost only, but -ssl services would be publically accessible. My reading thus far leads me towards Courier-imap with Exim 4 backported to stable so I can interface with ClamAV, but feel free to point out something important that I've missed. Do I need to have a different instance of the server running for each protocol? i.e. one listening on each port that the three services use as standard? Is there a server that would do the job with just one instance listening on all three ports? Would there be any advantages or disadvantages to this? I'm thinking locking/concurrency/that-sorta-thing. How do you deal with this situation? Are there any gotchas I need to know about? I'm guessing that using Maildirs will alleviate many of the problems that mboxes would create ... Any pointers/suggestions/cluebats appreciated! jc What we run here, is standard uw-imap and popa3d, with stunnel. Works like a charm. I know courier could handle everything with a single hand and half the overhead, maybe someday I'll migrate every mbox into maildir and set that up, but in the mean time, it does a pretty job. José PS please reply to debian-isp -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Imap && imap-ssl && pop3-ssl
[Sorry for the cross-post - I think it's applicable to both -isp and -user.] I need to offer imap, imapssl and pop3ssl services. FWIW, imap would be localhost only, but -ssl services would be publically accessible. My reading thus far leads me towards Courier-imap with Exim 4 backported to stable so I can interface with ClamAV, but feel free to point out something important that I've missed. Do I need to have a different instance of the server running for each protocol? i.e. one listening on each port that the three services use as standard? Is there a server that would do the job with just one instance listening on all three ports? Would there be any advantages or disadvantages to this? I'm thinking locking/concurrency/that-sorta-thing. How do you deal with this situation? Are there any gotchas I need to know about? I'm guessing that using Maildirs will alleviate many of the problems that mboxes would create ... Any pointers/suggestions/cluebats appreciated! jc -- Have a nice cup of tea and a biscuit. Fifty-five million Britons can't be wrong. Ooo - jammy dodgers!!
Imap && imap-ssl && pop3-ssl
[Sorry for the cross-post - I think it's applicable to both -isp and -user.] I need to offer imap, imapssl and pop3ssl services. FWIW, imap would be localhost only, but -ssl services would be publically accessible. My reading thus far leads me towards Courier-imap with Exim 4 backported to stable so I can interface with ClamAV, but feel free to point out something important that I've missed. Do I need to have a different instance of the server running for each protocol? i.e. one listening on each port that the three services use as standard? Is there a server that would do the job with just one instance listening on all three ports? Would there be any advantages or disadvantages to this? I'm thinking locking/concurrency/that-sorta-thing. How do you deal with this situation? Are there any gotchas I need to know about? I'm guessing that using Maildirs will alleviate many of the problems that mboxes would create ... Any pointers/suggestions/cluebats appreciated! jc -- Have a nice cup of tea and a biscuit. Fifty-five million Britons can't be wrong. Ooo - jammy dodgers!! -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
