On Fri, Jul 10, 2015 at 09:03:28AM -0400, James B. Byrne wrote:
> As much as I hate these things it seems that we do have a use case for
> one at the present. Ideally this would run as entry in an aliased
> :include: mailing list. I suppose I could just put a simple bash
> script together and ca
Andrew Beverley skrev den 2015-07-10 16:07:
You probably want to look at a Sieve implementation. I use one with
Dovecot, but
looks like there is one for Cyrus too:
https://cyrusimap.org/mediawiki/index.php/Cyrus_Sieve
This is the docs for Dovecot, but it gives you an idea of what you can
do:
On Fri, 2015-07-10 at 09:03 -0400, James B. Byrne wrote:
> As much as I hate these things it seems that we do have a use case for
> one at the present. Ideally this would run as entry in an aliased
> :include: mailing list. I suppose I could just put a simple bash
> script together and call that
Vytenis A:
> Hello everyone,
>
> Is there a way to do a recipient verification for emails in
> virtual_alias_maps?
Have you tried it? Note that it cannot work for aliases that expand
into multiple addresses. If some of those addresses are deliverable
and some not, then the answer depends on the
As much as I hate these things it seems that we do have a use case for
one at the present. Ideally this would run as entry in an aliased
:include: mailing list. I suppose I could just put a simple bash
script together and call that but I rather suspect this approach would
in the end prove more ti
Hello everyone,
Is there a way to do a recipient verification for emails in virtual_alias_maps?
The problem is that our clients are using "u...@localdomain.tld" ->
"u...@externaldomain.tld" aliases. This leaves me delivering SPAM
emails to, e.g. "gmail", which hang deffered in my queue.
"amavis"
