Hi,
On Fri May 16 2014 16:32, K-Ray wrote:
[...]
> Any one who can tell me how I can make a good working ruleset so every alias
> gets delivered to the correct mailmap and no '550 Invalid recipient' is
> generated.
> I have a 'domains', 'aliases' and 'vusers' file but with all I tried I
> haven't got a clue where to use virtual <aliases> or userbase <vusers>.
>
> this is my modified smtpd.conf
> # opensmtpd config
> #### security ####
> pki mail.mydomain.tld certificate "/etc/ssl/private/domaincert.crt"
> pki mail.mydomain.tld key "/etc/ssl/private/domainkey.key"
> pki mail.mydomain.tld ca "/etc/ssl/ca_startssl.pem"
>
> #### tables #####
> table domains file:/etc/smtpd/domains
> table myalias file:/etc/smtpd/virtual
> table vusers file:/etc/smtpd/vusers
> table credentials file:/etc/smtpd/credentials
>
> #### interfacing ####
> listen on lo
> listen on myIP port 25 tls pki mail.mydomain.tld
> listen on myIP port 587 tls-require pki mail.mydomain.tld auth <credentials>
>
> #### rules ####
> # accept from any for domain <domains> virtual <myalias>
> # accept from any for domain <domains> userbase <vusers> deliver to maildir
> accept from any for domain <domains> virtual { "@" => mainuser } deliver to
> maildir
> accept from local for any relay
>
> Almost everything works (incoming mail on 25, outgoing mail on 587 for
> authorised users), but filtering the incoming mail with aliases to the
> correct mailbox.
> Mail can be read with a dovecot imaps setup on port 993 with the same
> virtual users. Also that works fine after a lot of reading and trying.
>
> I hope someone here can help me out for the last step.
indeed, "alias" is not part of the matching process, it's actually
processed after the mail has already been accepted. That's why you've
got three rules all having the same matching criteria, from the matching
processors point of view.
I think what you're looking for is "recipient". See also smtpd.conf(5).
Norman
--
You received this mail because you are subscribed to [email protected]
To unsubscribe, send a mail to: [email protected]
