From: Ow Mun Heng <Ow.Mun.Heng@wdc.com>
To: gentoo-server@lists.gentoo.org
Subject: [gentoo-server] Comments on IMAP Server (cyrus/courier/dovecot)
Date: Thu, 11 Aug 2005 11:46:13 +0800 [thread overview]
Message-ID: <1123731973.5878.30.camel@neuromancer.home.net> (raw)
I'm just doing some testing for setting up a virtual mailhosting
I've read the Gentoo Virt Mail Howto and quite a few others but still
have some questions.
Choosen Mail Server : Postfix
IMAP Client under consideration : Cyrus IMAP/Courier IMAP/DoveCot
Requirements.
1. Ability to do Virtual Mail Hosting
2. Ability to support local Users (see note)
3. Scalable
4. Support for flat file Passwords(/etc/passwd) or LDAP/MySQL
Note :
a. Some users will be local users. These users will have SSH/SFTP/FTP
b. Some users will need to have FTP access (NO SSH) to webhosting
The problem here is mainly due to note (a) and (b) where there is a need
for local users. What I want, what is written on postfix's site
(http://www.postfix.org/VIRTUAL_README.html) is a variation of
i) NON Postfix Store : Separate Domains, NON-Unix Accounts
and
ii) Postfix store : Separate Domains, UNIX Accounts
Can all of these be done using NON-Postfix Store
(cyrus/courier/dovecot) : Separate Domains with Unix and Non Unix
Accounts? Depending on whether there is need for note (a) and (b)
or should I just put the local users on a separate box?
What are you using? I've seen quite a lot of Howto and docs but seems like
my choice isn't one of those widely used scenerios. In addition to that,
it also doesn't seem cyrus-imapd is much used too.
--
Ow Mun Heng
Gentoo/Linux on DELL D600 1.4Ghz 1.5GB RAM
98% Microsoft(tm) Free!!
Neuromancer 11:23:21 up 3:57, 6 users, load average: 1.00, 0.81, 0.71
--
gentoo-server@gentoo.org mailing list
next reply other threads:[~2005-08-11 3:47 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-11 3:46 Ow Mun Heng [this message]
2005-08-11 4:18 ` [gentoo-server] Comments on IMAP Server (cyrus/courier/dovecot) Arturo 'Buanzo' Busleiman
2005-08-11 4:39 ` Ow Mun Heng
2005-08-11 5:31 ` Arturo 'Buanzo' Busleiman
2005-08-11 11:56 ` Ian P. Christian
2005-08-11 12:15 ` Arturo 'Buanzo' Busleiman
2005-08-11 12:27 ` Ian P. Christian
2005-08-11 13:50 ` A. Khattri
2005-08-11 14:21 ` Ian P. Christian
2005-08-11 15:09 ` A. Khattri
2005-08-11 15:41 ` Ian P. Christian
2005-08-11 16:04 ` A. Khattri
2005-08-11 16:18 ` Ian P. Christian
2005-08-11 16:28 ` A. Khattri
2005-08-11 18:45 ` Arturo 'Buanzo' Busleiman
2005-08-11 19:18 ` A. Khattri
2005-08-11 16:04 ` Jonathan Nichols
2005-08-11 16:31 ` kashani
2005-08-11 14:28 ` xyon
2005-08-11 14:49 ` kashani
2005-08-11 15:07 ` xyon
2005-08-11 16:31 ` A. Khattri
2005-08-11 14:41 ` kashani
2005-08-11 16:33 ` A. Khattri
2005-08-11 16:52 ` kashani
2005-08-11 19:16 ` A. Khattri
2005-08-11 19:27 ` kashani
2005-08-11 19:44 ` A. Khattri
2005-08-11 20:00 ` kashani
2005-08-11 21:09 ` Wendall Cada
2005-08-12 9:54 ` Ow Mun Heng
2005-08-12 14:07 ` A. Khattri
2005-08-12 17:29 ` kashani
2005-08-12 18:35 ` A. Khattri
2005-08-12 9:50 ` Ow Mun Heng
2005-08-11 8:36 ` Darko Luketic
2005-08-11 10:05 ` Ow Mun Heng
2005-08-11 10:25 ` Benjamin Smee
2005-08-12 1:37 ` Ow Mun Heng
2005-08-12 1:47 ` Dennis Allison
2005-08-11 12:48 ` Yogesh Sharma
2005-08-11 13:42 ` A. Khattri
2005-08-12 1:04 ` Ian P. Christian
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1123731973.5878.30.camel@neuromancer.home.net \
--to=ow.mun.heng@wdc.com \
--cc=gentoo-server@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox