well, apparently still some problems with 6.2.3 wrt processing
incorrect headers:
.
.
.
.
reading message scoffin(_at_)mail(_dot_)comcast(_dot_)net:34 of 127 (2875
octets) .. flushed
reading message scoffin(_at_)mail(_dot_)comcast(_dot_)net:35 of 127 (5524
octets) ..... flushed
reading message scoffin(_at_)mail(_dot_)comcast(_dot_)net:36 of 127 (5370
octets) ..... flushed
reading message scoffin(_at_)mail(_dot_)comcast(_dot_)net:37 of 127 (3859
octets) ... flushed
reading message scoffin(_at_)mail(_dot_)comcast(_dot_)net:38 of 127 (8957
octets) ........ flushed
reading message scoffin(_at_)mail(_dot_)comcast(_dot_)net:39 of 127 (9280
octets) fetchmail: incorrect header line found while scanning headers
fetchmail: message delimiter found while scanning headers
flushed
fetchmail: client/server protocol error while fetching from mail.comcast.net
fetchmail: Query status=4 (PROTOCOL)
=S.Coffin
GV Computing
scoffin(_at_)comcast(_dot_)net