Alessandro Vesely writes:Yes. It is a dsn for unknown user; its first entity says:
This is completely broken.--B57772158E.1035822756/svpegasus1.flur.zuerich.ubs.ch --B57772158E.1035822756/svpegasus1.flur.zuerich.ubs.ch --B57772158E.1035822756/svpegasus1.flur.zuerich.ubs.ch --0__=jbWsAZXFFywhcPE7ZWjoR0lMsv0mxbsnaYbTYfU3d3D7h4Ch2ESN3wfy --0__=jbWsAZXFFywhcPE7ZWjoR0lMsv0mxbsnaYbTYfU3d3D7h4Ch2ESN3wfy --B57772158E.1035822756/svpegasus1.flur.zuerich.ubs.ch-- --0__=jbWsAZXFFywhcPE7ZWjoR0lMsv0mxbsnaYbTYfU3d3D7h4Ch2ESN3wfy-- --B57772158E.1035822756/svpegasus1.flur.zuerich.ubs.ch--
"This is the Postfix program at host svpegasus1.flur.zuerich.ubs.ch."
(actually uranus.ubs.com) The original message had an attachment and
somehow the remote server garbled the boundaries.
My filter complains it cannot understand such MIME structure,
it dumps a copy of the message and blocks it. So I have to
manually look at it, run reformime -r and send it over again.
Reformime returns a valid MIME structure.
I am wondering if I should automatically invoke it whenever my
filter can't parse a message. In general, it is not cool to block
a message only because its body happens to mimic MIME. On the
other hand, my filter scans for viruses, and it doesn't want to
get fooled by codes it cannot understand. For example, a base64
encoded virus could be smuggled into a text/plain entity where
the anti-virus engine does not recognize it.
Hmmm... any idea?
TIA
Ale
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
courier-users mailing list
[EMAIL PROTECTED]
Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
