Ben Morrow <b...@morrow.me.uk> wrote: > At 9PM +0100 on 15/12/12 Andreas Meyer wrote: > > Ben Morrow <b...@morrow.me.uk> wrote: > > > > > Before you go any further, please put the virtual_mailbox_maps parameter > > > back with a map of the valid virtual addresses. Otherwise you'll become > > > a backscatter source. > > > > Do you mean the old virtual_mailbox_maps = hash:/etc/postfix/vmailbox ? > > But wouldn't that mean I have to care for two user files? vmailbox and > > the passwd-file of dovecot? > > It doesn't matter how you do it, but you need to reject invalid users > during the SMTP transaction rather than allowing the mail to bounce > later. (This is really basic stuff: have you read through the Postfix > documentation? It make this pretty clear.)
Yes, this is clear to me and I also read through the dovecot-wiki a bit and especially LDA and LDA-Posfix. ;) > If you're using a passwd-file userdb in Dovecot, you need to write a > script to convert it to a Postfix map, and make sure that script gets > run whenever the source file is updated. (Makefiles are good for that > sort of thing.) Alternatively, you could switch to keeping your userdb > in an SQL or LDAP database, and have Postfix query it directly. If all > else fails, you can arrange to pass the output of 'doveadm user "*"' to > postmap, though depending on your Dovecot setup you may need to append a > domain. Thank you for your hints, Ben! I am glad I have that thing up and running at least. And I already converted the old vmailbox file that postfix used to a new one with the valid users so postfix knows them too. Thinking about SQL or LDAP database is one of the next steps I am considering. We don't have that much users and taking care of them is not that much work. Next thing is I want to implement Quota. We are running users with maildir and mboxes. And of course I want to realize sieve filtering soon or later. I am glad I got this right now with your help. And learned much again. > > Ben > Andreas
