Hi,
I'm currently migrating an old instance of OpenSMTPD (6.3) on OpenBSD to
current.
This setup uses Postgres as backend for the user database. Now, it seems
the Postgres backend is gone, because smtpd claims there is no such
backend. Then I've installed the opensmtpd-extras package to no
Hi,
when an envelope contains several recipient addresses which themself
resolve to one specific mailbox, e.g. a personal address and an alias,
emails are being delivered twice - two copies of the same email in the
mailbox.
Is this intended, or a lack of "AI" in the "de-aliasing" process?
Best
On Wed Jun 14 2017 16:21, Bruno Pagani wrote:
> Le 14/06/2017 à 15:36, Norman Golisz a écrit :
>
> > listen on egress port 10020 tag SPAM_IN
> > listen on egress port 10023 tag SPAM_OUT
> (*)
> > accept tagged SPAM_IN \
> > for any \
> >
On Fri May 30 2014 16:38, Clint Pachl wrote:
[...]
I still think that the 550 Invalid recipient error isn't intuitive when a
client doesn't have the locality or the credentials required by the mail
server.
Let's see it from the rule processors point of view. With a ruleset like
yours,
accept
On Mon May 19 2014 14:40, K-Ray wrote:
On 16-05-14 22:36, Norman Golisz wrote:
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
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
