Tom Sommer:
> On 2018-08-09 19:52, Wietse Venema wrote:
> > Tom Sommer:
> >> On 2018-08-09 19:31, Wietse Venema wrote:
> >> > 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 te
On 2018-08-09 19:52, Wietse Venema wrote:
Tom Sommer:
On 2018-08-09 19:31, Wietse Venema wrote:
> 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
Tom Sommer:
> On 2018-08-09 19:31, Wietse Venema wrote:
> > 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
On 2018-08-09 19:31, Wietse Venema wrote:
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 custom
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. Wi
On 2018-08-09 19:07, Viktor Dukhovni wrote:
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 ove
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 P
On 2018-08-09 18:17, Wietse Venema wrote:
Tom Sommer:
On 2018-08-09 14:57, Wietse Venema wrote:
> Tom Sommer:
>> I still fail to see how to inject the $smtp_code for the stream into
>> the
>> string at a precise position, but I gather it's possible somehow so I
>> will keep digging.
>
> One more
On 2018-08-09 18:24, Viktor Dukhovni wrote:
On Thu, Aug 09, 2018 at 11:07:33AM +0200, Tom Sommer wrote:
It would be nice if smtpd_reject_footer could include variables such
as
the 4.x.x/5.x.x response code or even the full postfix error message,
this way one could make more helpful errors mess
On Thu, Aug 09, 2018 at 11:07:33AM +0200, Tom Sommer wrote:
> It would be nice if smtpd_reject_footer could include variables such as
> the 4.x.x/5.x.x response code or even the full postfix error message,
> this way one could make more helpful errors messages with more helpful
> links.
Why wo
Tom Sommer:
> On 2018-08-09 14:57, Wietse Venema wrote:
> > Tom Sommer:
> >> I still fail to see how to inject the $smtp_code for the stream into
> >> the
> >> string at a precise position, but I gather it's possible somehow so I
> >> will keep digging.
> >
> > One more time:
> > YOU don't insert
On 2018-08-09 14:57, Wietse Venema wrote:
Tom Sommer:
I still fail to see how to inject the $smtp_code for the stream into
the
string at a precise position, but I gather it's possible somehow so I
will keep digging.
One more time:
YOU don't insert status codes into the footer.
POSTFIX inserts
Tom Sommer:
> On 2018-08-09 14:10, Wietse Venema wrote:
> > Tom Sommer:
> >> On 2018-08-09 14:01, Wietse Venema wrote:
> >> > Tom Sommer:
> >> >> It would be nice if smtpd_reject_footer could include variables such
> >> >> as
> >> >> the 4.x.x/5.x.x response code or even the full postfix error mess
On 2018-08-09 14:10, Wietse Venema wrote:
Tom Sommer:
On 2018-08-09 14:01, Wietse Venema wrote:
> Tom Sommer:
>> It would be nice if smtpd_reject_footer could include variables such
>> as
>> the 4.x.x/5.x.x response code or even the full postfix error message,
>> this way one could make more hel
Tom Sommer:
> On 2018-08-09 14:01, Wietse Venema wrote:
> > Tom Sommer:
> >> It would be nice if smtpd_reject_footer could include variables such
> >> as
> >> the 4.x.x/5.x.x response code or even the full postfix error message,
> >> this way one could make more helpful errors messages with more h
On 2018-08-09 14:01, Wietse Venema wrote:
Tom Sommer:
It would be nice if smtpd_reject_footer could include variables such
as
the 4.x.x/5.x.x response code or even the full postfix error message,
this way one could make more helpful errors messages with more helpful
links.
Better: smtpd_rejec
Tom Sommer:
> It would be nice if smtpd_reject_footer could include variables such as
> the 4.x.x/5.x.x response code or even the full postfix error message,
> this way one could make more helpful errors messages with more helpful
> links.
Better: smtpd_reject_footer_maps. Then you can use a lo
It would be nice if smtpd_reject_footer could include variables such as
the 4.x.x/5.x.x response code or even the full postfix error message,
this way one could make more helpful errors messages with more helpful
links.
Thanks
--
Tom
18 matches
Mail list logo
