POP3 client: MS Exchange 2000 server, using POP3
connector (I know, but this is a customer site!!)
Gateway/Firewall: P4 3GHz, 512MB, NetBSD 1.6.2, ipf,
ipnat (redirects o/b POP sessions to POP3filter)
Symptoms:
Only with certain messages, POP3filter seems to be
failing to pass thru the last few lines of an e-mail.
For example, if the last 7 lines are:
wuQx8+L2rv8l9uC0oPzhvDAsxMWorMjNsw7bysOrwOcx+8P
F4/Ps4Ht1Bvnh9+XgOqkwJTMv+vjj
5cbtMfPi9qP//OXmoKT496b8MhcLpaXNzaHYxckYp8znMfjM
1Tk3Jue1sRM7N+X//vxq6vUm5e/7
JPfK5+cq9vGs+Ori6Ll6OCVm5vzTz6+lCQplBd3Y2L/B5ef7
--=====fcb6dd4c5136e73c8bddab4--
.
(including the single dot above), the client (even
command line telnet) only gets:
wuQx8+L2rv8l9uC0oPzhvDAsxMWorMjNsw7bysOrwOcx+8P
F4/Ps4Ht1Bvnh9+XgOqkwJTMv+vjj
5cbtMfPi9qP//OXmoKT496b8MhcLpaXNzaHYxckYp8znMfjM
1Tk3Jue1sRM7N+X//vxq6vUm5e/7
with the next line (starting with "JPF..." in the above
example) sitting in the buffer. The client eventually
times out, and the message never makes it through. If I
connect directly to the POP3 server the message can be
downloaded directly.
Thanks!
Kevin@kevcom.ca
Logged In: YES
user_id=1099990
I also stumbled over this problem in my installation. I
traced the problem down to the fact that there were null
characters in the mail, i.e. hex 00. These null byte
sequences are not visible once the mail is downloaded with
other programs. When popfilter comes accross these it just
stops. I sent this info to the programmer, however was never
resolved. I had to make a workaround in scripting by
actually killing the running process if it timed out. Only
HEX downloading through Telnet showed the culprit. Usually
only Spam messages contained such null bytes.
georg@ragaz.net