Re: 450 response code instead of 550

From: Noel Jones (no email)
Date: Thu Mar 01 2007 - 15:52:59 EST

  • Next message: Magnus Bäck: "Re: Command output: Invalid user"

    At 10:09 PM 2/28/2007, Raal Goff wrote:
    >I have a spam filter machine setup to check all incoming mail. It
    >comes into postfix, which checks valid email addresses against a
    >mysql database, then filters the spam and looks up which server it
    >should forward the mail on via mysql again. The problem is that when
    >external servers enter a bad email address, the server returns a 450
    >status code and complains that the transport is unavailable, instead
    >of a 550 fatal status code. The behaviour i want is if the mysql
    >lookup fails, it returns 550. If I connect via sasl or from a host
    >in $mynetworks it gives to correct 550 error code. My recipient
    >restrictions are like so:
    >
    >smtpd_recipient_restrictions = permit_mynetworks,
    >permit_sasl_authenticated, reject_unauth_destination,
    >reject_unverified_recipient
    >
    >And i have also set
    >
    >unverified_recipient_reject_code = 550
    >
    >I'm not sure why it is not giving 550 status messages to external
    >clients. Below are my changes to main.cf

    We greatly prefer to see output of "postconf -n" and log entries
    demonstrating the problem rather than random main.cf snippings and
    vague descriptions.

    Your main.cf is configured with "reject_unverified_recipient" to
    query a downstream mail server to see if a recipient is valid. The
    transport to do this is apparently unavailable. The full log message
    will give more clues what the problem is.

    -- 
    Noel Jones 
    

  • Next message: Magnus Bäck: "Re: Command output: Invalid user"





    Hosted Email Solutions

    Invaluement Anti-Spam DNSBLs



    Powered By FreeBSD   Powered By FreeBSD