On Tue, Nov 16, 2010 at 07:29:07PM +0100, Daniel Hahler wrote:
> Victor Duchovni wrote:
>
> > On Thu, Sep 02, 2010 at 08:38:20PM -0400, Wietse Venema wrote:
> >
> >>> Perhaps an improved error logging could save somebody the effort
> >>> of troubleshooting.
> >>
> >
> > I think Mark is looking
Victor Duchovni wrote:
> On Thu, Sep 02, 2010 at 08:38:20PM -0400, Wietse Venema wrote:
>
>>> Perhaps an improved error logging could save somebody the effort
>>> of troubleshooting.
>>
>
> I think Mark is looking for improved logging in the SMTP server when
> connections to the proxy fail. Perh
On Thu, Sep 02, 2010 at 08:38:20PM -0400, Wietse Venema wrote:
> > Perhaps an improved error logging could save somebody the effort
> > of troubleshooting.
>
I think Mark is looking for improved logging in the SMTP server when
connections to the proxy fail. Perhaps something along the lines of:
> > All I got was a '451 4.3.0 Error: queue file write error' for the
> > client, and just a disconnect and a double bounce in the log.
> > Turning on verbosity on smtpd did not help to explain the issue.
> > (version: postfix-current-2.8.20100728 from ports @ FreeBSD 8.1)
>
> By design, Postfix d
Mark Martinec:
> I'd like to report a rather minor/cosmetic problem - namely a lack of
> useful logging when an smtpd service tries to connect to a proxy content
> filter over a Unix socket which is too heavily protected - but which took
> me far longer to understand than necessary (the strong prot
I'd like to report a rather minor/cosmetic problem - namely a lack of
useful logging when an smtpd service tries to connect to a proxy content
filter over a Unix socket which is too heavily protected - but which took
me far longer to understand than necessary (the strong protection was on
a parent
