timeout waiting for input during message collect
Harald ARNOLD
Till now I have always for one mailer (mail.pointec.de [213.39.248.214]).
From all other mail-servers I receive everything correct and in time:
Protocol (SuSE 10.0: /var/log/mail)
===================================
Nov 13 00:14:01 sauron sm-mta-rx[5137]: jACLDvvP005137: timeout waiting for
input from [213.39.248.214] during message collect
Nov 13 00:14:01 sauron sm-mta-rx[5137]: jACLDvvP005137:
from=<info.a...@actebis.at>, size=0, class=0, nrcpts=1,
msgid=<200511122114....@sauron.arnold.at>, proto=ESMTP,
daemon=MTA, relay=[213.39.248.214]
Nov 13 00:14:01 sauron sm-mta-rx[5137]: jACLDvvP005137:
to=<off...@arnold.at>, delay=02:00:00, pri=30000, stat=timeout waiting for
input during message collect
Please help me, Harald
Harald ARNOLD
> sendmail 8.13.5
>
> Till now I have always for one mailer (mail.pointec.de [213.39.248.214]).
> From all other mail-servers I receive everything correct and in time:
I read in one article that special ICMP protokols are neccesary for MTU
detection. I am using SuSE V 9.0 on mail server over a DSL connection. Has
anyone an idea about this ICMP name ?
Thanks Harald
Tilman Schmidt
> I read in one article that special ICMP protokols are neccesary for MTU
> detection. I am using SuSE V 9.0 on mail server over a DSL connection. Has
> anyone an idea about this ICMP name ?
ICMP Type 3 "Destination unreachable", Code 4 "Fragmentation Needed".
IMHO you should allow all ICMP Type 3 packets, anyway. Blocking any of
them doesn't increase security at all, but only makes life difficult
for yourself and for others trying to communicate with you.
Some PMTUD strategies also use Type 8 "Echo Request" and Type 0 "Echo
Reply", more commonly known as "ping". Personally I see no harm in
allowing those from/to a publicly reachable mail server, either.
--
Tilman Schmidt t.sc...@phoenixsoftware.de
Phoenix Software GmbH Tel. +49 228 97199 0
Adolf-Hombitzer-Str. 12 Fax +49 228 97199 99
53227 Bonn, Germany http://www.phoenixsoftware.de