Re: [fetchmail-users] feedback on failed delivery

[Matthias A. <mat...@gm...>]

Thomas Wolff schrieb am 2005-11-17:

> Now it's:
> > 1 message for deblnss01a/demsn702 at blnss35a.
> > reading message deblnss01a/demsn702@blnss35a:1 of 1 (3257 header octets) ... (2542 body octets) ..fetchmail: MDA returned nonzero status 255
> >  not flushed
> which is fine. Just make it better visible by putting the error notice 
> on a new line.

Well - fetchmail is actually behaving as was originally intended. It
prints the error message at the earliest possible time, and the "not
flushed" is a consequence of the error.

> Actually, running remotely (rsh ... fetchmail), the output turns into:
> > fetchmail: MDA returned nonzero status 255
> > 1 message for deblnss01a/demsn702 at blnss35a.
> > reading message deblnss01a/demsn702@blnss35a:1 of 1 (3257 header octets) ... (2542 body octets) .. not flushed
> which indicates that stdout and stderr gets merged in an unsynchronised 
> way. Probably a flush at some point (flush stdout before any error output) 
> would fix this.

Do you perhaps use a different verbosity with rsh than on your local
computer? I'm asking because verbosity would make a difference on your
local computer, too. We need to be sure we use absolute identical
settings for silent vs. verbose on both machines before we can start
debugging.

Could you double-check this?

-- 
Matthias Andree