Andreas Thienemann:
> Hi,
>
> On Wed, 20 Sep 2017, Wietse Venema wrote:
>
> > > > If you have a virtual alias that rewrites an address to the spam
> > > > sink, specify that address in the SMTP daemon acces rules instead.
> > >
> > [,,,]
> > > That would work. A bit of a hack though and I t
Hi,
On Wed, 20 Sep 2017, Wietse Venema wrote:
> > If you have a virtual alias that rewrites an address to the spam
> > sink, specify that address in the SMTP daemon acces rules instead.
>
[,,,]
> That would work. A bit of a hack though and I think it would only work for
> virtual aliases
> On Sep 19, 2017, at 8:39 PM, Andreas Thienemann wrote:
>
> That would work. A bit of a hack though and I think it would only work for
> virtual aliases with one level of redirection but not for something like
> i...@example.com -> i...@example.net -> spam-mails.
Some SQL implementations sup
Andreas Thienemann:
> Hi,
>
> On Tue, 19 Sep 2017, Wietse Venema wrote:
>
> > > During migration of an inherited mail system I have the situation that I
> > > would like to reject certain recipient address _after_ they have been
> > > rewritten through the virtual_alias_maps.
> >
> > The SMTP
Hi,
On Tue, 19 Sep 2017, Wietse Venema wrote:
> During migration of an inherited mail system I have the situation that I
> would like to reject certain recipient address _after_ they have been
> rewritten through the virtual_alias_maps.
The SMTP daemon acces rules currently do not have acc
Andreas Thienemann:
> Hi,
>
> During migration of an inherited mail system I have the situation that I
> would like to reject certain recipient address _after_ they have been
> rewritten through the virtual_alias_maps.
The SMTP daemon acces rules currently do not have access to that
information
Hi,
During migration of an inherited mail system I have the situation that I
would like to reject certain recipient address _after_ they have been
rewritten through the virtual_alias_maps.
The old system had a spam sink where users could redirect certain local
parts. e.g. a user has a catcha