Bug#1003399: Correct configuration of Exim

[karsten]

Hello Marc,

thank you for the response.

Am 09.01.22 um 19:05 schrieb Marc Haber:
>> Yes - the other possibility is to prevent upgrades of this package.
> 
> That is a decidedly bad idea. Exim is a huge suid binary (a design one
> out never choose today, the concept was valid 25 years ago) and you need
> security updates for that.

That's of course true.
Hopefully the version of Exim will not change until the configuration could be adapted.
Security updates will not need a new version of Exim within this stable distribution?

>> But there are additional other problems like spamassasin does not work any more,
>> so the configuration must be updated in many kinds.
> 
> Spamassassin in YOUR configuration doesn't work any more. My systems
> using spamassassin via exiscan-ACL have not even ridden a bump during
> the upgrade.

Maybe you are so kind to provide an example how you have included Spamassassin in Exim,
so that it will run with the packages of Debian 11?

>> Is there a default configuration for a private virtual mail server on dynamic IP's ?
> 
> Not that I am aware of. But if you roll yourself, you need to be able to
> take care of it. I think there might be solutions that might be better
> suited to your needs than Exim.

Indeed i am thinking that maybe Postfix is a better choice as MTA, because Exim seems to be
more and more complicated to configure?

> btw, this triggers me, as "virtual mail" does not have a definition, it
> leaves like ten way to interpret the task at hand.

I would define an virtual mail system as email server for different domains,
that can ideally be managed with entries in an database like Mariadb.

Greetings
karsten