Thanks to all for the instructions. I am working on the flatfile
approach and making good progress.
I also set up some test MySQL options and they work too.
So I have the future plans already in my hand!
TJ
On Tue, Sep 27, 2011 at 03:14:12PM -0700, terryjames9...@mm.st wrote:
With using the Dovecot lmtp option, where does Postfix know to refuse
email for a non-existing user or domain? That also has to be shared?
Sticking to the Flatfile recipe on the Wiki, Postfix would query the
Auth Backend of
Jerry wrote:
On Wed, 28 Sep 2011 08:44:24 +0200
Jan-Frode Myklebust articulated:
On Tue, Sep 27, 2011 at 08:51:18AM -0700, terryjames9...@mm.st wrote:
I'm a little confused about: to do that sharing-in-one-place, do I
have to use SQL or can I use the flatfiles like passwd-db? I
Hello Patrick,
On Tuesday, September 27, 2011 9:41 PM, Patrick Domack
patric...@patrickdk.com wrote:
It all depends on how much time and energy you want to spend in
setting it up, vs the flexibility you in vision you need later.
This is the intersection of the decision. I still am no sure
On Tue, Sep 27, 2011 at 08:51:18AM -0700, terryjames9...@mm.st wrote:
I'm a little confused about: to do that sharing-in-one-place, do I have
to use SQL or can I use the flatfiles like passwd-db? I think for sure
someone already decided the best approach for this, and maybe I'm not
On Wed, 28 Sep 2011 08:44:24 +0200
Jan-Frode Myklebust articulated:
On Tue, Sep 27, 2011 at 08:51:18AM -0700, terryjames9...@mm.st wrote:
I'm a little confused about: to do that sharing-in-one-place, do I
have to use SQL or can I use the flatfiles like passwd-db? I
think for sure
Am 27.09.2011 17:51, schrieb terryjames9...@mm.st:
Hello,
I'm moving my mail server from Exchange to an opensource one.
After a bunch of reading, I decided on building a Dovecot2 + Postfix
server in a VirtualUsers-only + Multiple-domains configuration.
Since my messages will be stored
terryjames9...@mm.st wrote:
Hello Nick,
On Tuesday, September 27, 2011 9:47 PM, Nick Rosier
nick+dove...@bunbun.be wrote:
+1 one on PostfixAdmin. Wouldn't want to live without it. The main
advantage of using a DB is that all information is stored in 1 location
and available in the right
-Original Message-
From: dovecot-boun...@dovecot.org [mailto:dovecot-
boun...@dovecot.org] On Behalf Of terryjames9...@mm.st
Hello Patrick,
On Tuesday, September 27, 2011 9:41 PM, Patrick Domack
patric...@patrickdk.com wrote:
It all depends on how much time and energy you want to
Hello,
I'm moving my mail server from Exchange to an opensource one.
After a bunch of reading, I decided on building a Dovecot2 + Postfix
server in a VirtualUsers-only + Multiple-domains configuration.
Since my messages will be stored by Dovecot, and the documentation is
really good, I figured
Tom Hendrikx wrote:
On 27/09/11 17:51, terryjames9...@mm.st wrote:
Hello,
I'm moving my mail server from Exchange to an opensource one.
After a bunch of reading, I decided on building a Dovecot2 + Postfix
server in a VirtualUsers-only + Multiple-domains configuration.
Since my messages will
On Wed, September 28, 2011 2:51 am, terryjames9...@mm.st wrote:
I'm a little confused about: to do that sharing-in-one-place, do I have
to use SQL or can I use the flatfiles like passwd-db? I think for sure
someone already decided the best approach for this, and maybe I'm not
understanding
On Wed, September 28, 2011 6:47 am, Nick Rosier wrote:
My main concern was losing mails if the DB is unavailable but this isn't
a problem; if the DB is unavailable Postfix will return a temporarily
unavailable and the MTA should retry.
yes, that was also my biggest concern when I 1st looked
Hello Tom,
On Tuesday, September 27, 2011 7:29 PM, Tom Hendrikx
t...@whyscream.net wrote:
The problem with passwd(like) files is that they are almost never in the
correct format to fit both daemons. The easiest way to use a database.
I don't yet see using a database easier than flatfiles. I
For my personal email, I have a habit of having the sql server down
for one reason or another. I just dump the sql tables to flatfiles on
the email server, and a script runs every 15min and checks for updates
if any exist. Works well.
Another method would be to just keep it sql, but dump
Well, the info dovecot needs, it mailbox name/location, username,
password, and quota, misc info.
postfix will need email address to mailbox name mapping info.
That is the very basic things you need.
Using dovecot lda/lmtp you remove all postfix needs to know mailbox
name to directory
Hello Nick,
On Tuesday, September 27, 2011 9:47 PM, Nick Rosier
nick+dove...@bunbun.be wrote:
+1 one on PostfixAdmin. Wouldn't want to live without it. The main
advantage of using a DB is that all information is stored in 1 location
and available in the right format through SQL-queries. My
Hello Patrick,
On Tuesday, September 27, 2011 6:06 PM, Patrick Domack
patric...@patrickdk.com wrote:
Using dovecot lda/lmtp you remove all postfix needs to know mailbox
name to directory mapping, that would be duplicated.
With using the Dovecot lmtp option, where does Postfix know to refuse
Depends on how you think about it.
If you forget about email addresses. Dovecot works on mailbox's, and
it maps a mailbox to a path, username, and password.
In postfix, it only cares about email addresses (if you use dovecot
for delivery, if not then postfix also has to care about the
19 matches
Mail list logo
