Alternatives for vexim, perfectly integrated into debian?

Hello,


at first let me express I am very thankful to the people that made vexim to=
 what it is. Thanks for your work.

I have used vexim a lot of years and now, that I am setting up another mail=
server, I am looking for a different solution.


Let me explain that:
I dislike how vexim "breaks" the configuration that comes with my debian or=
 ubuntu. The exim configuration, as installed by the distribution DVD, is j=
ust kind of "overwritten" (not in filesystem terms) by vexim. =

So, what I win here are the features of vexim, but what I lose are the ones=
 of debian. The system is a mixture of both, and often I have problems simi=
lar to:

- I change something in spamassassin. Nothing changes. Why? After an hour I=
 find out that I have changed a file that is relevant to plain installation=
, but not to vexim.

- exim out-of-the-debian-box has features like SSL-support with keys genera=
ted by "the system". vexim is not doing that for me. So I have to search th=
e net for something exim already was able to do, before vexim "downgraded" =
that feature. The same is true for SPF or other debian-enhancements.

- Often I cannot even find out what the problem is to debug "irritating" pr=
oblems. For example, I found out that our outgoing(!) mail is spam-checked,=
 and in case of a false positive the report in the X-header may contain ger=
man umlauts is irritating the remote mailserver crazy. I am pretty sure the=
 original debian exim will not behave that way, since it "knows" which doma=
ins are local ones. So where=B4s the problem? exim? vexim? spamd? spamassas=
sin? See "existing, but not used configuration files" above.

- I=B4ve installed original debian clamav. Vexim never used it. Did never f=
ind out why. For sure it can be done, but it does not integrate itself from=
 alone like "original" exim+clamav.


So, I am really interested in a solution that doesn=B4t fit "any system", b=
ut fit debian 100%. For example, uses the values from the apt-framework to =
find out it=B4s own domain etc., like exim.deb does, immediately uses clama=
v because it "knows" it is installed, the same with spamassassin,=85



BTW, I am aware of exim4U, and it looks for me like it has the same "proble=
m": You are overwriting the whole debian configuration to death. Stuff like=
 this is horrible:

> Copy Exim4U's exim configuration files from etc/exim/* to the target mach=
ine:
> cp -r * /etc/exim

A good integration should be, for example, a patchfile to the original conf=
ig, or, even better, a .deb-package supported by official debian.

Does such a tool exist?


Bye,
J=F6rg