Viktor Dukhovni:
> On Thu, Aug 09, 2018 at 06:52:48PM +0200, Tom Sommer wrote:
>
> > So I can do a "Please look at
> > http://example.com/smtp.php?code=$smtp_code"; and do some magic on that
> > page with the error code and/or error description to help the customer.
>
> Seems like overkill. Will you be documenting all the Postfix
> built-in error codes? If the error is from an access map, you can
> already put an URL in the text.
>
> That said, it is now clear what you're looking for. Presumably you
> mostly want the enhanced status code, since otherwise it is mostly
> just 554 for pretty much everything. Someone would have to write
> the that, and cycles are rather limited. Unless you're able to
> contribute a high-quality patch with updated documentation, this
> is unlikely to appear soon...
I suggested using a lookup table (smtpd_reply_footer_maps) which
is queried with the original Postfix response, and which can
dynamically return a filled-in template based on the content of the
query string. A pcre map would be fine for that.
The only new code needed is to get the reply_footer from a table
instead of a main.cf variable. There are already lots of examples
of doing that in Postfix, so anyone could write that.
Wietse
