Hi
i want to trigger hook when email come to t...@example.com or
workroom-*@example.com.
Problem: Regex not work in work access table
(http://www.postfix.org/access.5.html)
my /postfix/access file content is :
t...@example.com FILTER myhook:dummy #(its working)
/^workroom-.*@example\.com/ FILTE
On 2013-10-27 1:13 PM, Charles Marcus wrote:
Based on Noel's suggestion above I currently have:
# submission_clients_banned
linkedin.com REJECT Intro hijacker not welcome here
rapportive.com REJECT Intro hijacker not welcome here
Just added blackberry.net and rim.net, but I'm still very (extr
On 10/28/2013 2:42 AM, alizaheer wrote:
> Hi
>
> i want to trigger hook when email come to t...@example.com or
> workroom-*@example.com.
>
> Problem: Regex not work in work access table
> (http://www.postfix.org/access.5.html)
>
> my /postfix/access file content is :
>
> t...@example.com FILTER
Hi
Thanks for pointing out issue. Your solution works perfectly.
Regards
Ali
--
View this message in context:
http://postfix.1071664.n5.nabble.com/check-recipient-access-with-access-table-Filter-hooks-regex-tp62603p62606.html
Sent from the Postfix Users mailing list archive at Nabble.com.
Hello!
Have the similar problem:
Oct 22 17:12:12 awtech postfix/smtp[17586]: warning: TLS library
problem: 17586:error:1408F10B:SSL routines:SSL3_GET_RECORD:wrong version
number:s3_pkt.c:337:
Oct 22 17:12:12 awtech postfix/smtp[17586]: 034C0B14237: lost connection
with mail.trialtolatvia.lv[109
On Mon, Oct 28, 2013 at 05:54:51PM +0200, KSB wrote:
> Hello!
> Have the similar problem:
It is exactly the same problem, with exactly the same solution.
> Oct 22 17:12:12 awtech postfix/smtp[17586]: warning: TLS library
> problem: 17586:error:1408F10B:SSL routines:SSL3_GET_RECORD:wrong
> versio
On Mon, Oct 28, 2013 at 04:17:13PM +, Viktor Dukhovni wrote:
> > What else info I need to supply, to figure out what is wrong?
>
> tls_policy:
> # opportunistic, season to taste
> trialtolatvia.lv may exclude=3DES:aNULL
>
> main.cf:
> indexed = ${default_database_ty
Attached is the postconf -n
I've also been reading the link that Dr. Venema sent me. Could it be that the
mydestination is incorrect? Could it be:
mydestination = timothy.com, localhost.localdomain, localhost
myhostname = timothylegg.com
I haven't tried that yet, but I'm willing to try anyt
Tim Legg:
> Attached is the postconf -n
>
> I've also been reading the link that Dr. Venema sent me. Could it
> be that the mydestination is incorrect? Could it be:
>
> mydestination = timothy.com, [other stuff]
This is necessary to deliver mail for "usern...@timothy.com"
with mailbox_co
On 28/10/2013 19:36, Tim Legg wrote:
> Attached is the postconf -n
>
> I've also been reading the link that Dr. Venema sent me. Could it be
> that the mydestination is incorrect? Could it be:
>
> mydestination = timothy.com, localhost.localdomain, localhost
However, your configuration co
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 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
"REJECT" or "HOLD". But it would
also work with "FILTER" (override routing) and other access map
actions.
I have a patch that should also work with other Postfix releases at
ftp://ftp.porcupine.org/mirrors/postfix-release/experimental/feature-patches/20131028-check-sasl-access-patch
Wietse
13 matches
Mail list logo
