/dev/rob0 thank you you are right! I did not type space before -o
On Fri, Jun 28, 2013 at 3:40 PM, Dejan Doder <dode...@gmail.com> wrote: > "_timeout"? it my fault in typing > I edited this in vi editor.. > > > > On Fri, Jun 28, 2013 at 3:31 PM, /dev/rob0 <r...@gmx.co.uk> wrote: > >> On Fri, Jun 28, 2013 at 03:22:58PM +0200, Michael P. Demelbauer wrote: >> > On Fri, Jun 28, 2013 at 03:04:29PM +0200, Dejan Doder wrote: >> > > i have this message in tail -f /var/log/maillog >> > > >> > > bad transport type : lmtp_data_done_tiemeout=1200 >> >> Correct spelling DOES count here, "_timeout"? >> >> > > I dont know where is problem >> > > >> > > /etc/postfix.master.cf >> > > >> > > # >> ========================================================================== >> > > # service type private unpriv chroot wakeup maxproc command + args >> >> The transport type is the second field. >> >> > > # (yes) (yes) (yes) (never) (100) >> > > # >> ========================================================================== >> > > >> > > ... >> > > >> > > amavisfeed unix - - n - 2 lmtp >> > > -o lmtp_data_done_timeout=1200 >> >> This suggests that Postfix, when parsing master.cf, did not see the >> whitespace at the beginning of this line. Did you edit this in a Unix >> editor? I'd also suspect non-breaking spaces, which AFAIK are not >> going to be recognized as legitimate whitespace characters. >> >> > > -o lmtp_send_xforward_command=yes >> > > -o disable_dns_lookups=yes >> > > -o max_use=20 >> > >> > is it possible that this has to be >> > >> > lmtp_data_done_timeout=1200s >> > >> > ? >> > >> > At least when reading >> > >> > http://www.postfix.org/postconf.5.html >> > >> > it appears like that to me. Nonsense? >> >> The default time unit is s (seconds), so "1200" and "1200s" are the >> same thing. >> -- >> http://rob0.nodns4.us/ -- system administration and consulting >> Offlist GMX mail is seen only if "/dev/rob0" is in the Subject: >> > >
