Re: Logging suggestion

2018-12-30 Thread John Fawcett
On 30/12/2018 01:19, Wietse Venema wrote: > John Fawcett: >>> I would not log this for EVERY command. Especially because the >>> logged text size by far exceeds the command size (each logfile >>> record takes ~100 bytes, while the client needs to send only four >>> characters plus CRLF. >>> >>> For

Re: Logging suggestion

2018-12-30 Thread Wietse Venema
John Fawcett: > On 30/12/2018 01:19, Wietse Venema wrote: > > John Fawcett: > >>> I would not log this for EVERY command. Especially because the > >>> logged text size by far exceeds the command size (each logfile > >>> record takes ~100 bytes, while the client needs to send only four > >>> charact

Re: Logging suggestion

2018-12-30 Thread John Fawcett
On 30/12/2018 18:05, Wietse Venema wrote: > John Fawcett: >> On 30/12/2018 01:19, Wietse Venema wrote: >> Here's a revised patch implementing the above logging. >> >> I did not take out the existing pipelining logging since it provides >> additional info over the new error summary in the disconnect

Re: Local delivery to mbox / inode issue

2018-12-30 Thread Dominic Raferd
On Fri, 7 Dec 2018 at 10:22, Dominic Raferd wrote: > On Fri, 7 Dec 2018 at 09:15, Matus UHLAR - fantomas > wrote: > >> On 06.12.18 15:45, Dominic Raferd wrote: >> >I am using incrond to monitor an mbox file (in /var/mail) for changes, >> >> I think I have it working now. The problem was not post