Suddenly postfix is refusing to relay email

Discussion in 'General' started by hairydog2, Jun 12, 2009.

  1. hairydog2

    hairydog2 Member

    This morning, postfix is refusing to send email to external address. I can send to local addresses, but nowhere external:

    12/06/2009, 12:19:03: SEND - Message has not been sent. Server reply - 4.7.1 <[email protected]>: Relay access denied

    It was fine yesterday, and nothing has changed, except maybe an apt-get upgrade.

    I'm not sure the master.cf is right, though. I've had this problem with sending via port 587 and tried to work out why, but now is is not working on port 25.

    # ==========================================================================
    # service type private unpriv chroot wakeup maxproc command + args
    # (yes) (yes) (yes) (never) (100)
    # ==========================================================================
    smtp inet n - - - - smtpd
    587 inet n - n - - smtpd
    #submission inet n - - - - smtpd
    # -o smtpd_etrn_restrictions=reject
    #628 inet n - - - - qmqpd
    pickup fifo n - - 60 1 pickup
    cleanup unix n - - - 0 cleanup
    qmgr fifo n - - 300 1 qmgr
    #qmgr fifo n - - 300 1 oqmgr
    rewrite unix - - - - - trivial-rewrite
    bounce unix - - - - 0 bounce
    defer unix - - - - 0 bounce
    trace unix - - - - 0 bounce
    verify unix - - - - 1 verify
    flush unix n - - 1000? 0 flush
    proxymap unix - - n - - proxymap
    smtp unix - - - - - smtp
    relay unix - - - - - smtp
    # -o smtp_helo_timeout=5 -o smtp_connect_timeout=5
    showq unix n - - - - showq
    error unix - - - - - error
    local unix - n n - - local
    virtual unix - n n - - virtual
    lmtp unix - - n - - lmtp
    anvil unix - - n - 1 anvil
    #
    # Interfaces to non-Postfix software. Be sure to examine the manual
    # pages of the non-Postfix software to find out what options it wants.
    #
    # maildrop. See the Postfix MAILDROP_README file for details.
    #
    maildrop unix - n n - - pipe
    flags=DRhu user=vmail argv=/usr/local/bin/maildrop -d ${recipient}
    uucp unix - n n - - pipe
    flags=Fqhu user=uucp argv=uux -r -n -z -a$sender - $nexthop!rmail ($recipient)
    ifmail unix - n n - - pipe
    flags=F user=ftn argv=/usr/lib/ifmail/ifmail -r $nexthop ($recipient)
    bsmtp unix - n n - - pipe
    flags=Fq. user=bsmtp argv=/usr/lib/bsmtp/bsmtp -d -t$nexthop -f$sender $recipient
    scalemail-backend unix - n n - 2 pipe
    flags=R user=scalemail argv=/usr/lib/scalemail/bin/scalemail-store ${nexthop} ${user} ${extension}

    # only used by postfix-tls
    #tlsmgr fifo - - n 300 1 tlsmgr
    #smtps inet n - n - - smtpd -o smtpd_tls_wrappermode=yes -o smtpd_sasl_auth_enable=yes
    #587 inet n - n - - smtpd -o smtpd_enforce_tls=yes -o smtpd_sasl_auth_enable=yes
    tlsmgr unix - - - 1000? 1 tlsmgr
    scache unix - - - - 1 scache
    discard unix - - - - - discard
    retry unix - - - - - error
     
  2. till

    till Super Moderator Staff Member ISPConfig Developer

    Have you asked your access provider if they are blocking any ports? Did you cjeck if your IP got blacklisted?
     
  3. hairydog2

    hairydog2 Member

    It isn't a problem sending emails on: the ispconfig server's instance of postfix is refusing the connection from the email client. Some users get asked to enter their smtp authentication password, but that is rejected - even though it is correct.

    Mails addressed to domains hosted on the server are accepted OK.

    I wonder if an apt-get upgrade changed some sasl library or similar, becasue that is the only thing that changed at the time the problem started.
     
  4. till

    till Super Moderator Staff Member ISPConfig Developer

    You should go trough the mail part of the perfect setup guide again and check if all sasl settings are correct.
     
  5. hairydog2

    hairydog2 Member

    I followed the perfect setup when I set the machine up about three or four years ago, and it was working fine until yesterday.

    I'm worried that if I mess with a setup that was working, I may break something else.

    Is there anything in particular that might be worth checking?

    [Later:]

    Fixed it!

    Although apt-get had claimed to upgrade some libraries, using "aptitude safe-upgrade" found some installed but not configured packages. It fixed them for me, and now all is working just fine.

    Thanks for the help.
     
    Last edited: Jun 13, 2009

Share This Page