This is a discussion on Re: IMAP /etc/userdb and postfix within the mailing.postfix.users forums, part of the Mail Servers and Related category; > Postmaster wrote: > > I'll ask and duck... It appears as though several have gotten > flamed for &...
|
|||||||
| FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
|
|||
|
> Postmaster wrote:
> > I'll ask and duck... It appears as though several have gotten > flamed for > > the same question - but I'll be da**ned if I can find it. > >=20 > > I think I now have postfix mail receiving to real *nix accounts as > well > > as virtual. I used the create of /etc/userdb, manually duplicated > then > > entries for the virtual domains, and then set the password for > > each...the /etc/userdb file looks reasonable. > >=20 > > In my various trys to access the mail, other than by "cat" or > "less" of > > the /var/mail/vhost/domain-name/user, I have not implemented a > > successful retrieve. It appears as though I wish to implement > >=20 > > local_recipient_maps =3D something... > >=20 > > but "something" is not obvious. I am trying to avoid cyrus sasl > mysql > > etc., etc. I'm only talking a dozen users for each of 3 domains. > >=20 > > My apologies to Wietse...but what is the "something" if I have > > implemented the courier imap specified /etc/userdb ? > >=20 > > ducking and covering... > >=20 > > - Bill > >=20 >=20 > You will probably want to make sure you have the maildrop (the > courier > version) configured in master.cf, something like: >=20 > maildrop unix - n n - - pipe > flags=3DDRhu user=3Dmail argv=3D/usr/bin/maildrop -d > ${user}@${nexthop} > ${extension} ${recipient} ${user} ${nexthop} >=20 > Change mail to whatever user you want the maildrop to be run as... >=20 > Then in your main.cf, make sure your virtual_transport (or > local_transport for your local users) is set to: >=20 > virtual_transport =3D maildrop > # and/or > local_transport =3D maildrop >=20 > This will ensure that you are delivering the mail to the location > that > userdb is configured for. >=20 > For creating the userdb entries, I use the following: >=20 > mkdir /etc/courier/userdb/ > chown -R vmail /etc/courier/userdb/ >=20 > for (all email address for all domains) { >=20 > /usr/sbin/userdb "example.com/spamtrap@example.com" set > home=3D/var/mail/vhost/example.com/spamtrap > mail=3D/var/mail/vhost/example.com/spamtrap uid=3D8 gid=3D8 >=20 > # you will probably need to change uid and gid to what your user you > want to deliver mail as... >=20 > } >=20 > /usr/sbin/makeuserdb >=20 > As you can see the courier-maildrop on my system is configured for > /etc/courier/userdb/ rather than just /etc/userdb, YMMV. >=20 > Hope to help, >=20 > Damien >=20 =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3 D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D Thanks Damien - that explains part of it... What ties userdb, regardless of where it is, to postfix "validation"? I am using the user "vmail" from one of the examples. There does not appear to be a reference to "userdb" in main.cf or master.cf. I tried the changes anyway - and now get a=20 fatal: pipe_command: execvp /usr/local/bin/maildrop no such file or directory sigh... The maildrop courier version....is this what is implemented by the master.cf line ? How does courier know it's there ? There doesn't appear to much of imapd * imapd.cnf files in that /etc/courier directory. |
![]() |
| Thread Tools | |
| Display Modes | |
|
|