Otherwise, postfwd and the like could be configured for a rate limit
of zero (can't send mail).
Sorry, for the late answer, but no zero rate limits are required here.
With postfwd simply use:
id=SASLDROP
sasl_username==barrak
sasl_username==vladimir
sasl_username==mao
action
On 2013.10.28 21:54:00 +0100, Rudy Gevaert wrote:
> Quoting wie...@porcupine.org (Wietse Venema), Fri, 25 Oct 2013:
> >Adding check_sasl_sender_access support would not be difficult.
> >It just hasn't been done yet.
Not explicit, but ...
> Disabling the account is indeed a possibility, which we d
Quoting wie...@porcupine.org (Wietse Venema), Fri, 25 Oct 2013:
Rudy Gevaert:
Hello,
I was wondering if I could add a access map (to deny access in fact) for
specific sasl authenticated users?
Adding check_sasl_sender_access support would not be difficult.
It just hasn't been done yet.
E.
On 10/25/2013 04:44 PM, Rudy Gevaert wrote:
Hello,
I was wondering if I could add a access map (to deny access in fact)
for specific sasl authenticated users?
E.g. even if the login succeeds that user can't send email.
I couldn't find anything in the docs, but maybe I'm looking in the
wrong
Rudy Gevaert:
> Hello,
>
> I was wondering if I could add a access map (to deny access in fact) for
> specific sasl authenticated users?
Adding check_sasl_sender_access support would not be difficult.
It just hasn't been done yet.
> E.g. even if the login succeeds that user can't send email.
Y
Rudy Gevaert skrev den 2013-10-25 16:44:
I was wondering if I could add a access map (to deny access in fact)
for specific sasl authenticated users?
remove users is not solution ?
Hello,
I was wondering if I could add a access map (to deny access in fact) for
specific sasl authenticated users?
E.g. even if the login succeeds that user can't send email.
I couldn't find anything in the docs, but maybe I'm looking in the wrong
place.
Thanks,
Rudy
