Skip to content

Greeting message check for STARTTLS/AUTH availability #15

Closed

Description

@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

Activity

  1. bigon commented on Jul 5, 2013

    @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

  2. renini commented on Dec 8, 2014

    @renini

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

  3. corecode commented on Dec 9, 2014

    @corecode
    Owner

    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
    #15 (comment).

  4. mtremer commented on Nov 9, 2015

    @mtremer
    Contributor

    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

  5. corecode commented on Nov 10, 2015

    @corecode
    Owner

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

  6. mtremer commented on Nov 10, 2015

    @mtremer
    Contributor

    Thank you. Please see #34.

  7. jjakob commented on Apr 8, 2021

    @jjakob
    Contributor

    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.

  8. corecode commented on Apr 8, 2021

    @corecode
    Owner

    Thanks for confirming!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions