Messaging Gateway

 View Only

  • 1.  NetBotz Cannot Send Messages to SBG - Enhanced Status Codes?

    Posted Feb 16, 2011 05:00 PM
    I've posted this over at the APC forums, however, I expect I may get better help here (that's a compliment :D)
     
    My SBG is running software version 9.0.2-9.  Is there a way to force enhanced status codes?  I see that the SBG is advertising it, but the NetBotz appliance is not explicitly requesting them.  Any other thoughts or advice would be most welcome.
     
    Thanks,
     
     
     
     
     
    I'm trying to configure a NetBotz appliance to deliver email through our Symantec Brightmail Gateway. The NetBotz is running OS version 3.3.0. When configuring the email server in Advanced View, and sending a test message, I receive an error that the message could not be delivered and to check the appliance log. I increased the logging level for the test message CGI script and received the following output:

    Feb 16 12:58:48 probe1 daemon.info nbTestEmailCGI: READ :220 xxxsbg.domain.com ESMTP Symantec Brightmail Gateway
    Feb 16 12:58:48 probe1 daemon.info nbTestEmailCGI: WRITE:EHLO probe1
    Feb 16 12:58:48 probe1 daemon.info nbTestEmailCGI: READ :250-xxxxsbg.domain.com says EHLO to a.a.a.a:2943
    Feb 16 12:58:48 probe1 daemon.info nbTestEmailCGI: READ :250-ENHANCEDSTATUSCODES
    Feb 16 12:58:48 probe1 daemon.info nbTestEmailCGI: READ :250-PIPELINING
    Feb 16 12:58:48 probe1 daemon.info nbTestEmailCGI: READ :250 8BITMIME
    Feb 16 12:58:48 probe1 daemon.info nbTestEmailCGI: WRITE:MAIL FROM:<probe1@domain.com>
    Feb 16 12:58:48 probe1 daemon.info nbTestEmailCGI: READ :250 MAIL FROM accepted
    Feb 16 12:58:48 probe1 daemon.info nbTestEmailCGI: WRITE:QUIT
    Feb 16 12:58:48 probe1 daemon.info nbTestEmailCGI: READ :221 xxxxsbg.domain.com closing connection

    A packet capture has confirmed what the log is telling me: The mail gateway is responding with "250 MAIL FROM accepted" and the NetBotz then sends a QUIT command to terminate the connection.

    This gets more interesting when I send a message directly to our Microsoft Exchange 2007 server.

    Feb 16 12:59:00 probe1 daemon.info nbTestEmailCGI: READ :220 xxxxxxx.domain.com Microsoft ESMTP MAIL Service ready at Wed, 16 Feb 2011 11:58:59 -0800
    Feb 16 12:59:00 probe1 daemon.info nbTestEmailCGI: WRITE:EHLO probe1
    Feb 16 12:59:00 probe1 daemon.info nbTestEmailCGI: READ :250-xxxxxxx.domain.com Hello http://b.b.b.b
    Feb 16 12:59:00 probe1 daemon.info nbTestEmailCGI: READ :250-SIZE
    Feb 16 12:59:00 probe1 daemon.info nbTestEmailCGI: READ :250-PIPELINING
    Feb 16 12:59:00 probe1 daemon.info nbTestEmailCGI: READ :250-DSN
    Feb 16 12:59:00 probe1 daemon.info nbTestEmailCGI: READ :250-ENHANCEDSTATUSCODES
    Feb 16 12:59:00 probe1 daemon.info nbTestEmailCGI: READ :250-STARTTLS
    Feb 16 12:59:00 probe1 daemon.info nbTestEmailCGI: READ :250-X-ANONYMOUSTLS
    Feb 16 12:59:00 probe1 daemon.info nbTestEmailCGI: READ :250-AUTH NTLM
    Feb 16 12:59:00 probe1 daemon.info nbTestEmailCGI: READ :250-X-EXPS GSSAPI NTLM
    Feb 16 12:59:00 probe1 daemon.info nbTestEmailCGI: READ :250-8BITMIME
    Feb 16 12:59:00 probe1 daemon.info nbTestEmailCGI: READ :250-BINARYMIME
    Feb 16 12:59:00 probe1 daemon.info nbTestEmailCGI: READ :250-CHUNKING
    Feb 16 12:59:00 probe1 daemon.info nbTestEmailCGI: READ :250-XEXCH50
    Feb 16 12:59:00 probe1 daemon.info nbTestEmailCGI: READ :250 XRDST
    Feb 16 12:59:00 probe1 daemon.info nbTestEmailCGI: WRITE:MAIL FROM:<probe1@domain.com>
    Feb 16 12:59:00 probe1 daemon.info nbTestEmailCGI: READ :250 2.1.0 Sender OK
    Feb 16 12:59:00 probe1 daemon.info nbTestEmailCGI: WRITE:RCPT TO:<first.last@domain.com>
    Feb 16 12:59:00 probe1 daemon.info nbTestEmailCGI: WRITE:DATA
    Feb 16 12:59:00 probe1 daemon.info nbTestEmailCGI: READ :250 2.1.5 Recipient OK
    Feb 16 12:59:00 probe1 daemon.info nbTestEmailCGI: READ :354 Start mail input; end with <CRLF>.<CRLF>
    Feb 16 12:59:00 probe1 daemon.info nbTestEmailCGI: WRITE:Subject: NetBotz Test E-mail
    Feb 16 12:59:00 probe1 daemon.info nbTestEmailCGI: WRITE:From: probe1@domain.com
    Feb 16 12:59:00 probe1 daemon.info nbTestEmailCGI: WRITE:To: first.last@domain.com
    Feb 16 12:59:00 probe1 daemon.info nbTestEmailCGI: WRITE:MIME-Version: 1.0
    Feb 16 12:59:00 probe1 daemon.info nbTestEmailCGI: WRITE:Content-Type: text/plain; charset=UTF-8
    Feb 16 12:59:00 probe1 daemon.info nbTestEmailCGI: WRITE:Content-Transfer-Encoding: 8bit
    Feb 16 12:59:00 probe1 daemon.info nbTestEmailCGI: WRITE:Date: Wed, 16 Feb 2011 12:59:00 -0700
    Feb 16 12:59:00 probe1 daemon.info nbTestEmailCGI: WRITE:Message-Id: <1297886340.12349@probe1>

    I then receive the message normally.

    What this is telling me is that the NetBotz appliance doesn't like the response from the mail server to its "MAIL FROM" command. The responses are:

    Brightmail Gateway:
    250 MAIL FROM accepted

    Exchange Server:
    250 2.1.0 Sender OK

    My theory is that the NetBotz gateway is expecting an enhanced status code beyond the simple 250. Is there any way to modify this behaviour? I could investigate whether or not the Brightmail Gateway can send enhanced status codes, but I would prefer to reconfigure the NetBotz device as no other devices connecting to the gateway experience this problem. Also, I could send directly to the Exchange server, but I would prefer to route all my SMTP traffic through my mail gateway.

    Any advice or guidance would be appreciated.

    Thank you in advance, 


  • 2.  RE: NetBotz Cannot Send Messages to SBG - Enhanced Status Codes?

    Posted Feb 17, 2011 01:25 PM

    Hello,

    as you noticed SBG is advertising the enhanced status codes but not using them on the current release. It is being considered for implementation on a future release though. At the moment it is not possible to make those work AFAIK, however, there could be a workaround to have the MTA not to advertise the "250-ENHANCEDSTATUSCODES". If that's a possible solution to your problem please contact support in order to work on that.

    thanks,

    Federico



  • 3.  RE: NetBotz Cannot Send Messages to SBG - Enhanced Status Codes?

    Posted Mar 20, 2011 09:34 PM

    When I first setup SBG 9 I had problems with some of my network devices not being able to send email to/through it. Some of those were Netbotz devices. This may well be what the problem was!

    Where does one disable the enhanced status codes? (Using 9.02-9 now, but may upgrade to 9.5 soon)