4.0a6, ACLs don't like very short rcpt regexes?
2007-07-18 by Matt Kettler
I've been running 4.0a6, and I tried to add a very short regex for a some of my accounts. Two of those accounts were three-letter names, and those lines caused syntax errors. ie this causes an error: (exact username changed) acl whitelist rcpt /\<foo@evi/ this does not: (exact username changed) acl whitelist rcpt /\<some@evi/ Is there some rule that rcpt regexes need to be at least 9 chars long? AFAIK the ones I added today are the shortest regexes I've ever used. For reference, this is what I got in my logs when the service re-loaded the file automatically: milter-greylist: config error at line 411: syntax error So I commented it out, and tried to start it again, and got an error on 413. Both of the error lines were 3-character usernames, and were added copy-paste-edit at the same time as several other entries. If you want to see the structure of everything, this is lines 411-416, which I just added. 411 and 413 are now commented out to avoid errors. I've changed all the usernames to 12345, etc to match the exact length of the actual address. #acl whitelist rcpt /\<123@evi/ acl whitelist rcpt /\<123456@evi/ flushaddr #acl whitelist rcpt /\<123@evi/ flushadr acl whitelist rcpt /\<123456@evi/ flushaddr acl whitelist rcpt /\<1234@evi/ flushaddr acl whitelist rcpt /\<1234@evi/ flushaddr (and yes, the first one didn't have a flushaddr, as it's not a reliable spamtrap. The others are.)