On Thursday 22 April 2010 18:15:18 Phil Howard wrote:
[ ... all standard stuff that is well documented ... ]
5. Passwords stored encrypted, such as MD5. And it should be a scheme
that both Postfix and Dovecot can use so I don't have keep two different
encryption schemes.
Postfix doesn't
On 22/04/2010 17:18, Phil Howard wrote:
I have not been following this thread as closely as I probably should
have; however, I was wondering what the OP's problem was with using
MySQL? It would greatly simplify the job of constructing and
maintaining databases. It is even possible to create
P.S. The idiot who kept breaking the plain text format file in my
original setup was da da ... me ... So given I think of myself as
reasonably technical, I would claim that text format databases are way
more fragile than you might expect (good luck getting a non
technical user not to
On Wed, Apr 21, 2010 at 01:45:35PM -0400, Phil Howard wrote:
Then I think MySQL will do the job. Both postfix and dovecot support MySQL,
and you can use SASL to authenticate SMTP with Dovecot, so Dovecot would do
all the auth work. Finally, you could use Postfix's VDA patch if you want to
On 23/04/2010 10:30, Gábor Lénárt wrote:
On Wed, Apr 21, 2010 at 01:45:35PM -0400, Phil Howard wrote:
Then I think MySQL will do the job. Both postfix and dovecot support MySQL,
and you can use SASL to authenticate SMTP with Dovecot, so Dovecot would do
all the auth work. Finally, you could
On Fri, Apr 23, 2010 at 2:49 AM, Rainer Frey rainer.f...@inxmail.de wrote:
On Thursday 22 April 2010 18:15:18 Phil Howard wrote:
[ ... all standard stuff that is well documented ... ]
5. Passwords stored encrypted, such as MD5. And it should be a scheme
that both Postfix and Dovecot can
On Fri, Apr 23, 2010 at 3:45 AM, Ed W li...@wildgooses.com wrote:
You need to look at where you are going with this One way or another you
need a database - call it a banana if you prefer, but it's still a database
whether it's a flat file or a BDB file or whatever
One must be careful
On Fri, Apr 23, 2010 at 5:23 AM, Ed W li...@wildgooses.com wrote:
P.S. The idiot who kept breaking the plain text format file in my
original setup was da da ... me ... So given I think of myself as
reasonably technical, I would claim that text format databases are way
more fragile than
On Fri, 23 Apr 2010 09:03:02 -0400
Phil ttip...@gmail.com articulated:
You rsync the files an SQL database (like MySQL) works from, and don't
expect corruption? That's only safe if the database is synced and
shut down. I don't want to be doing that. If I did run a database
engine, it would
On 23/04/2010 15:51, Jerry wrote:
There are numerous ways to export/backup a live MySQL database. I have
employed several of them myself. You might want to check out this URL
for starters:
http://www.noupe.com/how-tos/10-ways-to-automatically-manually-backup-mysql-database.html
Your statement
On Fri, 23 Apr 2010 16:07:20 +0100
Ed li...@wildgooses.com articulated:
Err to be fair, I was about to reply and say that it's IS achievable,
but on the flip side I would concede that it does require a bit of
thought to make this stuff work correctly. I think you are being a
bit harsh to
On Wed, Apr 21, 2010 at 04:34:30PM -0400, Phil Howard wrote:
userdb {
args = username_format=%u /var/vmail/auth.d/%d/passwd
driver = passwd-file
}
What does it take to get Postfix to read this?
Basically these two parameters in 'main.cf':
[main.cf]
smtpd_sasl_type=dovecot
I have now created a basic How To for the desired configuration on the
2.0 Wiki. Although it has some 2.0 specifics it should work with 1.2 for
most parts too. Maybe someone with a higher privilege level on the Wiki
than I have can beautify the URL by removing the Whitespaces :)
On Wednesday 21 April 2010 21:30:12 Thomas Leuxner wrote:
I'm running a setup that should be good enough for what you are trying to
achieve. All user information is stored in flat files per domain and you
may override per user settings individually:
passdb {
args = username_format=%u
On Thu, Apr 22, 2010 at 11:18:09AM +0200, Rainer Frey wrote:
What I don't see here at all (and neither in your Wiki Howto) is how Postfix
determines the valid recipients for the domains in virtual_mailbox_domains.
Postfix will expand possible aliases first and determine the final
recipient
On Wed, Apr 21, 2010 at 5:45 PM, Heiko Schlittermann
h...@schlittermann.dewrote:
Hello Phil,
Phil Howard ttip...@gmail.com (Mi 21 Apr 2010 16:32:36 CEST):
I'm setting up a Postfix and Dovecot combination. What I want to do is
have
a user database that (1) is not running from some engine
On Thursday 22 April 2010 15:34:40 Phil Howard wrote:
So what would local_recipient_maps look like in this case?
As the suggested setup uses virtual_mailbox_domains for the mailboxes hosted
by dovecot, it would be virtual_mailbox_maps. Alternatively one could define
relay_domains,
On Thu, Apr 22, 2010 at 09:48:36AM -0400, Phil Howard wrote:
The ideal would be a complete mail server package that handled it all in one
... SMTP, submission, IMAP(S), POP3(S). But what I've seen as attempts to
do that so far were less than promising (even though I have no need for what
most
On Thu, Apr 22, 2010 at 10:43 AM, Rainer Frey rainer.f...@inxmail.dewrote:
If you can't wait for Dovecot 2.0, you need to use dovecot deliver, but you
should set it up as a pipe transport in master - see
http://wiki.dovecot.org/LDA/Postfix for virtual users. mailbox_command
again
is for
On Thu, Apr 22, 2010 at 12:12 PM, Jerry dovecot.u...@seibercom.net wrote:
On Thu, 22 Apr 2010 17:03:00 +0200
Rainer rainer.f...@inxmail.de articulated:
Well, it leaves out the *one tricky part* of using a flat file
database for virtual users with dovecot and postfix: there is no
common
On Thu, Apr 22, 2010 at 12:07 PM, Jim Trigg jtr...@spamcop.net wrote:
On Thu, Apr 22, 2010 at 09:48:36AM -0400, Phil Howard wrote:
The ideal would be a complete mail server package that handled it all in
one
... SMTP, submission, IMAP(S), POP3(S). But what I've seen as attempts
to
do
On Thu, 22 Apr 2010 12:18:41 -0400
Phil ttip...@gmail.com articulated:
The administration is going to be handed off to less technical
people, and my goal is to mimize the number of elements in this.
It's not about MySQL itself ... it's about not running yet another
server/daemon.
Excuse my
On Thu, Apr 22, 2010 at 12:40 PM, Jerry dovecot.u...@seibercom.net wrote:
On Thu, 22 Apr 2010 12:18:41 -0400
Phil ttip...@gmail.com articulated:
The administration is going to be handed off to less technical
people, and my goal is to mimize the number of elements in this.
It's not about
Phil Howard put forth on 4/22/2010 11:18 AM:
On Thu, Apr 22, 2010 at 12:12 PM, Jerry dovecot.u...@seibercom.net wrote:
On Thu, 22 Apr 2010 17:03:00 +0200
Rainer rainer.f...@inxmail.de articulated:
Well, it leaves out the *one tricky part* of using a flat file
database for virtual users
On Thu, Apr 22, 2010 at 3:12 PM, Stan Hoeppner s...@hardwarefreak.comwrote:
With this many lookup table types supported by Postfix, is it true that it
has no simple table type in common with Dovecot?
There are some ... like mysql for example. The ones I call simple are
ones that have a
Phil Howard skrev:
On Thu, Apr 22, 2010 at 12:12 PM, Jerry dovecot.u...@seibercom.net wrote:
On Thu, 22 Apr 2010 17:03:00 +0200
Rainer rainer.f...@inxmail.de articulated:
Well, it leaves out the *one tricky part* of using a flat file
database for virtual users with dovecot and
On Thu, Apr 22, 2010 at 4:31 PM, Arne K. Haaje a...@drlinux.no wrote:
Have you looked into Postfix Admin? http://postfixadmin.sourceforge.net/
It might be a good solution for you. I'm using it for a a growing database
of users and I'm very happy with it. The setup with postfix, dovecot and
On Thu, Apr 22, 2010 at 5:19 PM, Stan Hoeppner s...@hardwarefreak.comwrote:
One nice thing about Postfix is that the documentation is _very_ thorough,
even if sometimes hard to digest.
Yes, I would agree. Sometimes a twisty maze of passages, but you can
eventually find things.
Good luck,
I'm setting up a Postfix and Dovecot combination. What I want to do is have
a user database that (1) is not running from some engine (so not LDAP or SQL
or such) ... and (2) is completely disassociated from system users (e.g.
most email users are not in /etc/passwd and most /etc/passwd users are
build as passdb ( http://wiki.dovecot.org/AuthDatabase/PasswdFile )
and write a sript which builds an valid postfix lookuptable usable as
local_recipient_maps.
Andreas
Am 21.04.2010 10:32 schrieb Phil Howard:
I'm setting up a Postfix and Dovecot combination. What I want to do is have
a user
I think /etc/passwd is as close as it gets to your requirements... why not just
add the users as system users, and set their shell to /bin/false?
Patrick
Phil Howard ttip...@gmail.com wrote:
I'm setting up a Postfix and Dovecot combination. What I want to do is have
a user database that (1)
postfix:
smtpd_sasl_type = dovecot
smtpd_sasl_path = private/auth
dovecot:
auth default {
socket listen {
client {
path = /var/spool/postfix/private/auth
user = _postfix
group = wheel
mode = 0660
}
}
}
Then configure your favorite auth mechanism for
Set up the users in /etc/dovecot/passwd for Dovecot authentication and
/etc/postfix/vmailbox for postfix users. Not possible to use one file for two
of them because the formats are markedly different.
Alexander
- Original Message -
From: Phil Howard ttip...@gmail.com
To:
On Wed, Apr 21, 2010 at 10:32:36AM -0400, Phil Howard wrote:
Ideal would be a one-file solution, which can be managed by
text editing or simple command line tools. But what I want is ONE file that
both Postfix (for valid recipients) and Dovecot (for user login
authentication) can use
On Wed, Apr 21, 2010 at 10:47 AM, Patrick Nagel m...@patrick-nagel.netwrote:
I think /etc/passwd is as close as it gets to your requirements... why not
just add the users as system users, and set their shell to /bin/false?
There would be conflicts in this, especially with multiple domain
Phil Howard escribió:
On Wed, Apr 21, 2010 at 10:47 AM, Patrick Nagel m...@patrick-nagel.netwrote:
I think /etc/passwd is as close as it gets to your requirements... why not
just add the users as system users, and set their shell to /bin/false?
There would be conflicts in this, especially
On Wed, Apr 21, 2010 at 10:58 AM, Peter Hessler phess...@theapt.org wrote:
postfix:
smtpd_sasl_type = dovecot
smtpd_sasl_path = private/auth
dovecot:
auth default {
socket listen {
client {
path = /var/spool/postfix/private/auth
user = _postfix
group = wheel
On Wed, Apr 21, 2010 at 1:30 PM, Rodolfo Gonzalez rgonza...@gnt.cc wrote:
Phil Howard escribió:
On Wed, Apr 21, 2010 at 10:47 AM, Patrick Nagel m...@patrick-nagel.net
wrote:
I think /etc/passwd is as close as it gets to your requirements... why
not
just add the users as system users,
I'm running a setup that should be good enough for what you are trying to
achieve. All user information is stored in flat files per domain and you may
override per user settings individually:
passdb {
args = username_format=%u /var/vmail/auth.d/%d/passwd
driver = passwd-file
}
userdb {
On Wed, Apr 21, 2010 at 3:30 PM, Thomas Leuxner t...@leuxner.net wrote:
I'm running a setup that should be good enough for what you are trying to
achieve. All user information is stored in flat files per domain and you may
override per user settings individually:
passdb {
args =
Hello Phil,
Phil Howard ttip...@gmail.com (Mi 21 Apr 2010 16:32:36 CEST):
I'm setting up a Postfix and Dovecot combination. What I want to do is have
a user database that (1) is not running from some engine (so not LDAP or SQL
or such) ... and (2) is completely disassociated from system users
On 04/22/10 00:58, Peter Hessler wrote:
postfix:
smtpd_sasl_type = dovecot
smtpd_sasl_path = private/auth
dovecot:
auth default {
socket listen {
client {
path = /var/spool/postfix/private/auth
user = _postfix
group = wheel
mode = 0660
}
}
}
Then
42 matches
Mail list logo
