Ubuntu Postfix Open LDAP integration - no SASL authentication mechanisms











up vote
0
down vote

favorite












Ive followed all the steps in https://help.ubuntu.com/community/Postfix/DovecotLDAP
but I am getting a




localhost postfix/smtpd[12520]: fatal: no SASL authentication
mechanisms




in my /var/log/mail.err



Is there a way to find out more specific root cause?



Note: I have verified saslauthd is running properly using testsaslauthd. SASLAuthd is running fine. I'm struggling in trying to get deeper logs and exact cause on the postfix-sasl side, since I assume the issue will be there.










share|improve this question
















bumped to the homepage by Community 2 days ago


This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.



















    up vote
    0
    down vote

    favorite












    Ive followed all the steps in https://help.ubuntu.com/community/Postfix/DovecotLDAP
    but I am getting a




    localhost postfix/smtpd[12520]: fatal: no SASL authentication
    mechanisms




    in my /var/log/mail.err



    Is there a way to find out more specific root cause?



    Note: I have verified saslauthd is running properly using testsaslauthd. SASLAuthd is running fine. I'm struggling in trying to get deeper logs and exact cause on the postfix-sasl side, since I assume the issue will be there.










    share|improve this question
















    bumped to the homepage by Community 2 days ago


    This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.

















      up vote
      0
      down vote

      favorite









      up vote
      0
      down vote

      favorite











      Ive followed all the steps in https://help.ubuntu.com/community/Postfix/DovecotLDAP
      but I am getting a




      localhost postfix/smtpd[12520]: fatal: no SASL authentication
      mechanisms




      in my /var/log/mail.err



      Is there a way to find out more specific root cause?



      Note: I have verified saslauthd is running properly using testsaslauthd. SASLAuthd is running fine. I'm struggling in trying to get deeper logs and exact cause on the postfix-sasl side, since I assume the issue will be there.










      share|improve this question















      Ive followed all the steps in https://help.ubuntu.com/community/Postfix/DovecotLDAP
      but I am getting a




      localhost postfix/smtpd[12520]: fatal: no SASL authentication
      mechanisms




      in my /var/log/mail.err



      Is there a way to find out more specific root cause?



      Note: I have verified saslauthd is running properly using testsaslauthd. SASLAuthd is running fine. I'm struggling in trying to get deeper logs and exact cause on the postfix-sasl side, since I assume the issue will be there.







      ubuntu postfix openldap sasl






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited Apr 5 '15 at 14:23

























      asked Apr 3 '15 at 12:43









      Arjun Dhar

      1317




      1317





      bumped to the homepage by Community 2 days ago


      This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.







      bumped to the homepage by Community 2 days ago


      This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
























          1 Answer
          1






          active

          oldest

          votes

















          up vote
          0
          down vote













          I managed to fix it. RCA were:




          1. SASLauthd service was initially not running. I verified that by performing testsaslauthd


          2. dovecot service was not running: dovecot not starting : service(imap) access(/usr/lib/dovecot/imap) failed. This was preventing postfix from connecting via SASL. As a result telnet on 25 was also failing.



          Troubleshooting steps:




          1. Verify service status using service dovecot status, service postfix status, testsaslauthd. To identify and isolate the problem

          2. If SASLAuthd is using "pam" as a MECH then you may want to try a direct MECH like "ldap" in my case.E.g: Shutdown sasldservice and saslauthd -a ldap -V

          3. Look into your logs @ /var/log/mail.err and /var/log/auth.log for details

          4. Verify configs are fine by postconf -n and dovecot -n

          5. Fix individual service errors. Note: service errors will only occur when you try to start the service, not execute. So Step 1 & 3 are essential not to miss any stupid startup issues.






          share|improve this answer























            Your Answer








            StackExchange.ready(function() {
            var channelOptions = {
            tags: "".split(" "),
            id: "106"
            };
            initTagRenderer("".split(" "), "".split(" "), channelOptions);

            StackExchange.using("externalEditor", function() {
            // Have to fire editor after snippets, if snippets enabled
            if (StackExchange.settings.snippets.snippetsEnabled) {
            StackExchange.using("snippets", function() {
            createEditor();
            });
            }
            else {
            createEditor();
            }
            });

            function createEditor() {
            StackExchange.prepareEditor({
            heartbeatType: 'answer',
            convertImagesToLinks: false,
            noModals: true,
            showLowRepImageUploadWarning: true,
            reputationToPostImages: null,
            bindNavPrevention: true,
            postfix: "",
            imageUploader: {
            brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
            contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
            allowUrls: true
            },
            onDemand: true,
            discardSelector: ".discard-answer"
            ,immediatelyShowMarkdownHelp:true
            });


            }
            });














            draft saved

            draft discarded


















            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f194204%2fubuntu-postfix-open-ldap-integration-no-sasl-authentication-mechanisms%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown

























            1 Answer
            1






            active

            oldest

            votes








            1 Answer
            1






            active

            oldest

            votes









            active

            oldest

            votes






            active

            oldest

            votes








            up vote
            0
            down vote













            I managed to fix it. RCA were:




            1. SASLauthd service was initially not running. I verified that by performing testsaslauthd


            2. dovecot service was not running: dovecot not starting : service(imap) access(/usr/lib/dovecot/imap) failed. This was preventing postfix from connecting via SASL. As a result telnet on 25 was also failing.



            Troubleshooting steps:




            1. Verify service status using service dovecot status, service postfix status, testsaslauthd. To identify and isolate the problem

            2. If SASLAuthd is using "pam" as a MECH then you may want to try a direct MECH like "ldap" in my case.E.g: Shutdown sasldservice and saslauthd -a ldap -V

            3. Look into your logs @ /var/log/mail.err and /var/log/auth.log for details

            4. Verify configs are fine by postconf -n and dovecot -n

            5. Fix individual service errors. Note: service errors will only occur when you try to start the service, not execute. So Step 1 & 3 are essential not to miss any stupid startup issues.






            share|improve this answer



























              up vote
              0
              down vote













              I managed to fix it. RCA were:




              1. SASLauthd service was initially not running. I verified that by performing testsaslauthd


              2. dovecot service was not running: dovecot not starting : service(imap) access(/usr/lib/dovecot/imap) failed. This was preventing postfix from connecting via SASL. As a result telnet on 25 was also failing.



              Troubleshooting steps:




              1. Verify service status using service dovecot status, service postfix status, testsaslauthd. To identify and isolate the problem

              2. If SASLAuthd is using "pam" as a MECH then you may want to try a direct MECH like "ldap" in my case.E.g: Shutdown sasldservice and saslauthd -a ldap -V

              3. Look into your logs @ /var/log/mail.err and /var/log/auth.log for details

              4. Verify configs are fine by postconf -n and dovecot -n

              5. Fix individual service errors. Note: service errors will only occur when you try to start the service, not execute. So Step 1 & 3 are essential not to miss any stupid startup issues.






              share|improve this answer

























                up vote
                0
                down vote










                up vote
                0
                down vote









                I managed to fix it. RCA were:




                1. SASLauthd service was initially not running. I verified that by performing testsaslauthd


                2. dovecot service was not running: dovecot not starting : service(imap) access(/usr/lib/dovecot/imap) failed. This was preventing postfix from connecting via SASL. As a result telnet on 25 was also failing.



                Troubleshooting steps:




                1. Verify service status using service dovecot status, service postfix status, testsaslauthd. To identify and isolate the problem

                2. If SASLAuthd is using "pam" as a MECH then you may want to try a direct MECH like "ldap" in my case.E.g: Shutdown sasldservice and saslauthd -a ldap -V

                3. Look into your logs @ /var/log/mail.err and /var/log/auth.log for details

                4. Verify configs are fine by postconf -n and dovecot -n

                5. Fix individual service errors. Note: service errors will only occur when you try to start the service, not execute. So Step 1 & 3 are essential not to miss any stupid startup issues.






                share|improve this answer














                I managed to fix it. RCA were:




                1. SASLauthd service was initially not running. I verified that by performing testsaslauthd


                2. dovecot service was not running: dovecot not starting : service(imap) access(/usr/lib/dovecot/imap) failed. This was preventing postfix from connecting via SASL. As a result telnet on 25 was also failing.



                Troubleshooting steps:




                1. Verify service status using service dovecot status, service postfix status, testsaslauthd. To identify and isolate the problem

                2. If SASLAuthd is using "pam" as a MECH then you may want to try a direct MECH like "ldap" in my case.E.g: Shutdown sasldservice and saslauthd -a ldap -V

                3. Look into your logs @ /var/log/mail.err and /var/log/auth.log for details

                4. Verify configs are fine by postconf -n and dovecot -n

                5. Fix individual service errors. Note: service errors will only occur when you try to start the service, not execute. So Step 1 & 3 are essential not to miss any stupid startup issues.







                share|improve this answer














                share|improve this answer



                share|improve this answer








                edited Apr 13 '17 at 12:37









                Community

                1




                1










                answered Apr 6 '15 at 3:27









                Arjun Dhar

                1317




                1317






























                    draft saved

                    draft discarded




















































                    Thanks for contributing an answer to Unix & Linux Stack Exchange!


                    • Please be sure to answer the question. Provide details and share your research!

                    But avoid



                    • Asking for help, clarification, or responding to other answers.

                    • Making statements based on opinion; back them up with references or personal experience.


                    To learn more, see our tips on writing great answers.





                    Some of your past answers have not been well-received, and you're in danger of being blocked from answering.


                    Please pay close attention to the following guidance:


                    • Please be sure to answer the question. Provide details and share your research!

                    But avoid



                    • Asking for help, clarification, or responding to other answers.

                    • Making statements based on opinion; back them up with references or personal experience.


                    To learn more, see our tips on writing great answers.




                    draft saved


                    draft discarded














                    StackExchange.ready(
                    function () {
                    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f194204%2fubuntu-postfix-open-ldap-integration-no-sasl-authentication-mechanisms%23new-answer', 'question_page');
                    }
                    );

                    Post as a guest















                    Required, but never shown





















































                    Required, but never shown














                    Required, but never shown












                    Required, but never shown







                    Required, but never shown

































                    Required, but never shown














                    Required, but never shown












                    Required, but never shown







                    Required, but never shown







                    Popular posts from this blog

                    Accessing regular linux commands in Huawei's Dopra Linux

                    Can't connect RFCOMM socket: Host is down

                    Kernel panic - not syncing: Fatal Exception in Interrupt