[EMAIL PROTECTED]:/etc/postfix# cat rr.pcre
/(?!(smtp)|(biz))(?=dhcp.*).*\.rr\.com/ 554 Go away

[EMAIL PROTECTED]:/etc/postfix# postmap -q - pcre:rr.pcre
ms-smtp-01.texas.rr.com

[EMAIL PROTECTED]:/etc/postfix# postmap -q - pcre:rr.pcre
dhcp-whatever.rr.com
dhcp-whatever.rr.com    554 Go away

Seems to work 



-----Original Message-----
From: Tom Baker|Netsmith Inc [mailto:[EMAIL PROTECTED] 
Sent: Saturday, September 13, 2003 4:23 PM
To: '[EMAIL PROTECTED]'
Subject: [IMGate] Re: are we lazy as he says ?



Damn I need to grab the manpages so I can test this shit

..
The following works with a test in perl

/(?!(smtp)|(biz))(?=dhcp.*).*\.rr\.com/


-----Original Message-----
From: Tom Baker|Netsmith Inc [mailto:[EMAIL PROTECTED] 
Sent: Saturday, September 13, 2003 4:02 PM
To: '[EMAIL PROTECTED]'
Subject: [IMGate] Re: are we lazy as he says ?



Do zero width tests work?

How do you force a string to test a pcre from command line? (I'm forgetful
and don't have my pdf man pages around)


I would think something like this might work.

/(?!(smtp.*)|(biz))(?=<subscribers>)\.rr\.com/ 554 ACL



-----Original Message-----
From: Len Conrad [mailto:[EMAIL PROTECTED] 
Sent: Saturday, September 13, 2003 10:24 AM
To: [EMAIL PROTECTED]
Subject: [IMGate] Re: are we lazy as he says ?




>Anybody know how to put make negate work in postfix pcre: ??

unlike hash: files, the pcre: files are "first match wins", so :

/smtp.*\.rr\.com$/        ok
/biz\.rr\.com$/           ok
/<subscribers>\.rr\.com/  554 ACL .....

The problem with this approach is that "ok" means we whitelist them from 
thta point on and do not apply any later smtpd restrictions to them, so a 
single /pcre/ that excludes !biz and !smtp is still desired, if 
possible.  anybody know?

Len


Reply via email to