Page 2 of 2 FirstFirst 12
Results 11 to 16 of 16

Thread: Issue with setting up mail server

  1. #11
    Join Date
    Mar 2010
    Location
    Squidbilly-Land
    Beans
    13,550
    Distro
    Lubuntu 14.04 Trusty Tahr

    Re: Issue with setting up mail server

    Any chance you could use normal code tags, not html? Most Unix config files care about line wrap and sometimes they care about spacing.

  2. #12
    Join Date
    Jun 2014
    Beans
    21

    Re: Issue with setting up mail server

    Hello!

    This seems to be your config:

    Code:
    cat dovecot.conf | grep -v "#"
    service pop3-login {  inet_listener pop3 {    
    service lmtp {  unix_listener lmtp {    
    service imap {  
    service pop3 {  
    service auth {  
    service auth-worker {  
    service dict {  
    }
    }
    You are opening { but not closing them.

    Here you can find an example:
    https://www.dovecot.org/doc/dovecot-example.conf

    Code:
    $ cat dovecot-example.conf | grep -v "#" | awk /./
    
    
    protocol imap {
    }
      
    protocol pop3 {
    }
    protocol lda {
    }
    auth default {
      mechanisms = plain
      passdb pam {
      }
      userdb passwd {
      }
      user = root
    }
    dict {
    }
    plugin {
    }
    Last edited by lisati; June 25th, 2017 at 01:39 AM. Reason: Replaced [QUOTE] with [CODE] for readability

  3. #13
    Join Date
    Mar 2010
    Location
    Squidbilly-Land
    Beans
    13,550
    Distro
    Lubuntu 14.04 Trusty Tahr

    Re: Issue with setting up mail server

    # is a comment start character. This extremely common in Unix config files. Anything after that on a line is not parsed.

    Check your {} open/close blocks.

  4. #14
    Join Date
    Jul 2011
    Beans
    7

    Re: Issue with setting up mail server

    Quote Originally Posted by TheFu View Post
    # is a comment start character. This extremely common in Unix config files. Anything after that on a line is not parsed.

    Check your {} open/close blocks.

    Sorry for the delay in response...I did not see page 2 and I would not have, had my son not pointed it out to me

    I will attempt to put the file in an editor that checks for quotes...I will get back to you on the results thank you.

  5. #15
    Join Date
    Jun 2007
    Location
    Porirua, New Zealand
    Beans
    Hidden!
    Distro
    Ubuntu

    Re: Issue with setting up mail server

    Quote Originally Posted by TheFu View Post
    Check your {} open/close blocks.
    Quote Originally Posted by Hugo_Serrano View Post
    You are opening { but not closing them.
    This is what I am seeing too.

    A quick count can be helpful. If you start at 0 (zero), adding 1 for every {, and taking off for every }, you should arrive at zero by the time you reach the end of the file.
    Last edited by lisati; June 25th, 2017 at 01:44 AM.
    Forum DOs and DON'Ts
    Please use CODE tags
    Including your email address in a post is not recommended
    My Blog

  6. #16
    Join Date
    Jul 2011
    Beans
    7

    Re: Issue with setting up mail server

    Quote Originally Posted by lisati View Post
    This is what I am seeing too.

    A quick count can be helpful. If you start at 0 (zero), adding 1 for every {, and taking off for every }, you should arrive at zero by the time you reach the end of the file.
    My apologies, I have gone over the file 3 or 4 times with another set of eyes that was counting separately...and since I have been programming for 30 years, I have become quite accustomed to finding just these kinds of errors...I can only find the exact number of open brackets for closed brackets...and I don't use the entire file...I treat a section (similar to a function) as one section, since using the entire file as a guide can run into problems...for example...

    Code:
    service auth {  <---- Opening bracket for service auth
      # auth_socket_path points to this userdb socket by default. It's typically
      # used by dovecot-lda, doveadm, possibly imap process, etc. Users that have
      # full permissions to this socket are able to get a list of all usernames and
      # get the results of everyone's userdb lookups.
      #
      # The default 0666 mode allows anyone to connect to the socket, but the
      # userdb lookups will succeed only if the userdb returns an "uid" field that
      # matches the caller process's UID. Also if caller's uid or gid matches the
      # socket's uid or gid the lookup succeeds. Anything else causes a failure.
      #
      # To give the caller full permissions to lookup all users, set the mode to
      # something else than 0666 and Dovecot lets the kernel enforce the
      # permissions (e.g. 0777 allows everyone full permissions).
      unix_listener auth-userdb { <---- Opening bracket for unix_listener auth-userdb
        mode = 0666
        user = vmail
        group = mail
      } <---- Closing bracket for unix_listener auth-userdb
    
    
      # Postfix smtp-auth
      unix_listener /var/spool/postfix/private/auth { <---- Opening bracket for unix_listener /var/spool/postfix/private/auth
        mode = 0666
      }  <---- Closing bracket for unix_listener /var/spool/postfix/private/auth
    
    
      # Auth process is run as this user.
      user = postfix
      group = postfix
    }  <---- Closing bracket for service auth
    This is how I systematically eliminate the problem of the brackets...and I am only seeing the exact number of open brackets that I am closed brackets...those that are not commented out I might add...please, if you are seeing something that I am missing, please point it out.

Page 2 of 2 FirstFirst 12

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •