Greeting message check for STARTTLS/AUTH availability

[tuxillo]

dma does not read the server greeting to determine whether STARTTLS or AUTH are available (minor problem as this probably is just a configuration problem because only one "smarthost" is contacted).

Spotted in : http://bugs.dragonflybsd.org/issues/953

[bigon]

Hi,

Just to add that regarding the detection of AUTH mechanisms, when CRAM-MD5 is not available on the server, dma is currently printing a quite scary (from a user point of view) in the logs

smarthost authentication: AUTH cram-md5 not available: 535 5.7.8 Error: authentication failed: no mechanism available

[renini]

Should this just being ignored "AUTH cram-md5 not available" or can i config dma to not output this?

[corecode]

You can ignore it.

On 12/08/2014 10:24 PM, renini wrote:

Should this just being ignored "AUTH cram-md5 not available" or can i config dma to not output this?

— Reply to this email directly or view it on GitHub https://github.com/corecode/dma/issues/15#issuecomment-66189972.

[mtremer]

I worked on a patch to implement this. Are you interested in merging this upstream?

http://git.ipfire.org/?p=people/ms/dma.git;a=commitdiff;h=54af6a9684f21d799de17d49f8b985d95f121080

[corecode]

Thanks for the patch. Could you please submit a pull request - I have some comments I'd like to share with you.

[mtremer]

Thank you. Please see #34.

[jjakob]

Debian Buster still has version 0.11 which does not include the patch from #34. I was able to download the 0.13-1 deb package from https://packages.debian.org/sid/dma and install it with dpkg, luckily all the dependencies were the same. This fixed the error messages and I'm not getting banned by fail2ban on the mail server any more after it sees the failed login attempts.

[corecode]

Thanks for confirming!