Author: Paul B. Johnson Date: To: exim-users Subject: [Exim] problem with exim <-> mailagent
I'm a new Exim user with a problem for which I have not been able to find
any reference in the exim-users list archives.
I just upgraded my Debian linux box (which previously used smail and
mailagent without any problems) to Debian 2.2. The Debian upgrade
instructions state that smail has problems with Debian 2.2, and that was
indeed the case. After looking around at the various alternatives I decided
on Exim (version 3.12-10 from the official Debian package). Installation
was straight-forward. Getting Exim to work with mailagent (Debian package
3.68-9.potato) was accomplished by modifying the syntax of the .forward file
which feeds mail to mailagent (I had to remove the 'exec' command for it to
work with Exim).
At this point all was good ... or so I thought. I now have the problem that
large attachments are corrupted when I use the Exim <-> mailagent
combination. Exim by itself seems to work fine. Smail with the same
mailagent configuration (except for the above-noted change to the .forward
file) worked fine.
The corruption I am seeing is illustrated in the two blocks of
base64-encoded data below.
These corruptions seem to appear at approximate 10KB intervals (although not
at *every* 10KB interval). The same message sent multiple times will not
necessarily have the corruptions in the same locations.
Except for this one problem, I am very favorably impressed with Exim and
would like to continue using it. Unfortunately the built-in filtering in
Exim is not quite powerful enough for my needs, so I need something with the
capabilities of mailagent. Do I need to learn how to use procmail?
