Am 29.07.2015 um 00:01 schrieb Viktor Dukhovni:
On Tue, Jul 28, 2015 at 11:37:19PM +0200, Dominik Chilla wrote:
Sorry, but it still doesnt work. I took a "vanilla" 3.1-20150721 and patched
it again, checked if the patch applied correctly (searching for
register_maps_byname() in smtpd_check.c etc.) and compiled the sources.
When I leave out the leading "{" and the ending "}" it seems to work, but
only if
check_mumble_access inline:{send...@zwackl.de=OK},static:{REJECT BAD SENDER}
That's wrong, it parses as:
check_mumble_access inline:{send...@zwackl.de=OK},
<implicit check_mumble_access> static:{REJECT BAD SENDER}
which is very different.
Got it! It was a kind of an act of desperation :(
When I specify
check_mumble_access inline:{send...@zwackl.de=DUNNO},static:{REJECT BAD
SENDER}
the static map applies but ends with a reject.
How would you test it? My ideas are running low :-/
You need to combine the two maps into one logical map:
check_mumble_access {
inline:{send...@zwackl.de=DUNNO},
static:{REJECT BAD SENDER}
}
Yes, and that´s what I wanted to do.
Then if the first map returns DUNNO, the second should not be
consulted, unless the implementation is not yet quite right.
I don´t know why, but it works now!? The config is the same as before
(checked by diff).
As Wietse already pointed out, postconf doesn´t cover this case yet:
/usr/sbin/postconf: warning: main.cf: syntax error after '}' in
"{send...@zwackl.de=DUNNO},static:{REJECT BAD SENDER}}"
/usr/sbin/postconf: warning: main.cf: syntax error after '}' in
"{recipie...@zwackl.de=DUNNO},static:{REJECT BAD RECIPIENT}}"
Thank you very much for your help and the very fast solution!
... and sorry for my blindness ;)
Dominik
