 | Start a set with this search |
 | Include this search in one of my sets |
 | Exclude this search from one of my sets |
 | Permalink to these results Paste this link in email or IM: |
 | Atom feed for tracking future search results Paste this URL into your reader: |
4 messages in net.sourceforge.lists.courier-users[courier-users] Re: Using Courier 0.3...| From | Sent On | Attachments |
|---|---|---|
| Steve Mitchell | Nov 15, 2001 6:19 pm | |
| Steve Mitchell | Nov 15, 2001 6:24 pm | |
| Sam Varshavchik | Nov 15, 2001 7:17 pm | |
| Steve Mitchell | Nov 15, 2001 9:33 pm |
| Permalink for this message Paste this link in email or IM: |
| Permalink for this thread Paste this link in email or IM: |
| Atom feed for this thread Paste this URL into your reader: |
| Subject: | [courier-users] Re: Using Courier 0.36.0 with vpopmail | Actions... |
|---|---|---|
| From: | Sam Varshavchik (mrs...@courier-mta.com) | |
| Date: | Nov 15, 2001 7:17:40 pm | |
| List: | net.sourceforge.lists.courier-users | |
Steve Mitchell writes:
I am a long time qmail user, and would like to switch a number of my production
boxes over to the full blown courier mail server.
I already use courier-imap and courier-pop3 with qmail to serve clients mail. I
also use sqwebmail for webmail access. So since I'm using most of the
components in the courier family, it makes some sense to switch over to the
entire suite as a solution.
However, I'm concerned about the integration with vpopmail. I have a lot of
domains with folks who are already using qmailadmin to administer their virtual
domains hosted via vpopmail. They have mailing lists, forwards, autoreplies,
etc.
I would not recommend using the vpopmail module with the entire courier tree. It's there, and it'll compile, but that's about it. vpopmail is tightly coupled to qmail, and getting rid of qmail is probably going to mess up vpopmail.
I know that the majority of these things should work with courier, but I have
not been able to find anyone on this list who has done this for a while. I
searched the archives and all I can find references to are folks running
courier-imap with vpopmail.
You are forging ahead into uncharted territory. If you insist, the safe thing to do is to compile and install courier separately. Do not get rid of the existing courier-imap and sqwebmail installs. Manually copy over their configuration, by hand, to Courier's tree. After installing Courier, tell it to read .qmail files instead of .courier files: echo "qmail"
/usr/lib/courier/etc/dotextension. Disable sqwebmail, disable
courier-imap, disable qmail, bring up courier, and see how it goes.
If something breaks, it's only a matter of shutting down courier, and then bringing back your previous courier-imap and sqwebmail install, with qmail.
This is how qmail migrations should be done in any case, with or without vpopmail. If this is done right there won't be any file conflicts, except perhaps for PAM configuration files, if PAM authentication is being used. It might even be possible to run both systems at the same time, in parallel, by binding one set of imap/pop3/smtp servers to listen on non-standard ports, and by renaming one of the sqwebmail binaries.
My main concern is the .qmail files for ezmlm mailing lists, which I assume I
could continue using, and the .qmail files for fowards, etc. I still wish to
use qmailadmin since my users are used to that.
ezmlm will not work with Courier. qmail only.
I also cannot find references (perhaps I haven't looked hard enough) as to how
to configure the virtual domains in courier to point at my vpopmail accounts.
Same exact way as courier-imap, if it works at all. It's the same exact code.
-- Sam