Wietse Venema via Postfix-users:
> Dmytro Alieksieiev:
> > The negative pattern
> > if !/(.{300})/
> > /(.+)/ $1
> > ENDIF
> >
> > never rewrites the key. It returns the whole, unmodified string when it
> > is under the limit, and no result for anything at or above 300 bytes, at
> > which point pipemap short-circuits and the socketmap is never queried.
> > Because the key is never truncated, there is no encoding hazard
> > regardless of where a multibyte character sits. Side note: I changed
> > (.*) to (.+) as empty string result is not allowed in maps.
>
> Good. It would make sense to implement a socketmap_max_query_size
> feature that forces a "not found" result for long queries. This can
> be a Postfix 3.12 feature.
Implemented for Postfix 3.12:
https://www.postfix.org/postconf.5.html#socketmap_max_query_size
socketmap_max_query_size (default: 10000)
The maximum allowed query size for a socketmap client, not
including the socketmap and netstring encapsulation. A
request that exceeds the limit generates a warning and a
'not found' result.
This feature is implemented in Postfix >= 3.12. The docuentation
is almost complete.
With older Postfix versions, use pipemap to suppress queries that
the socketmap-based SRS server does not support.
Wietse
_______________________________________________
Postfix-users mailing list -- [email protected]
To unsubscribe send an email to [email protected]
