Robert Norris:
> I've been trying to read the code, to try and find out where this
> corruption might be occuring. The only place I can see where messages
> are read a line at a time is in smtpd, when the message is actually read
> from the network. However, there doesn't seem to be any place in the
> code where a line might be magically dropped (and rightly so).

There is no such place in Postfix. I have even sent executable
files through Postfix without damage happening to them. This was
before Postfix was changed to by default break lines > 2048 bytes.

Postfix performs no complex operations on the message content.
There is far more chance for data damage by your virus scanning
component, because it does so much more with the data.

> One idea we had was to take and MD5 sum of the message body when the
> message arrives, before it is spooled to disk, and then again just
> before it leaves the system, and compare them. However, I can't see
> where to add this sort of functionality into Postfix.

This is a waste of time. Why not start with the virus scanner,
it can be tested in isolation, and it is a much more likely
candidate.

> So,
>
> 1. Where should I be starting to add this code?
>
> 2. Anyone have any ides as to what might be causing this problem,
> overall?
>
> I'd love to be able to rule Postfix out as the source of this problem.

Then start with the non-Postfix part first.

        Wietse
-
To unsubscribe, send mail to majordomopostfix.org with content
(not subject): unsubscribe postfix-users

• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]