sday
Verified User
Hi
I installed DA in Debian 5 with custombuild 1.1 and everything seemed ok. But it turns out exim has been using the da-unaware exim.conf that's included in the da_exim-4.69.deb package and rejecting email. I fixed it by enabling eximconf=yes in custombuilds options file.
Why the heck does the directadmin provided da_exim-4.69.deb file come with a non-da aware configuration file? And since it does why doesn't custombuild overwrite the exim.conf by default?
Also, I mentioned some time ago that the debian package contained in da_exim-4.69.deb should be named "da-exim" and marked as conflicting against "exim". "exim" is provided by debian and it will be upgraded when the exim in debian has a newer version than da_exim. Perhaps this needs its own thread to get directadmins attention. Same with proftpd.
I don't mean to come across as a crumpy old man. I love directadmin, but the installation scripts are a programmers nightmare.
Cheers
Shane
I installed DA in Debian 5 with custombuild 1.1 and everything seemed ok. But it turns out exim has been using the da-unaware exim.conf that's included in the da_exim-4.69.deb package and rejecting email. I fixed it by enabling eximconf=yes in custombuilds options file.
Why the heck does the directadmin provided da_exim-4.69.deb file come with a non-da aware configuration file? And since it does why doesn't custombuild overwrite the exim.conf by default?
Also, I mentioned some time ago that the debian package contained in da_exim-4.69.deb should be named "da-exim" and marked as conflicting against "exim". "exim" is provided by debian and it will be upgraded when the exim in debian has a newer version than da_exim. Perhaps this needs its own thread to get directadmins attention. Same with proftpd.
I don't mean to come across as a crumpy old man. I love directadmin, but the installation scripts are a programmers nightmare.
Cheers
Shane