Connecting to Barracuda

Home Forums Networking Cisco Security – PIX/ASA/VPN Connecting to Barracuda

Viewing 1 post (of 1 total)
  • Author
    Posts

  • skeating
    Member
    #165904

    Hello

    I am trying to connect both inbound and outbound email from the Barracuda Email Security System to my Exchange 2010 server. Currently my Cisco 515 PIX has these two rules, which I believe are allowing mail in and out:

    XXX.XXX.XX.XX is the public IP for my Exchange server.

    access-list BORDER35 permit tcp any host XXX.XXX.XX.XX eq smtp

    static (inside,outside) tcp XXX.XXX.XX.XX smtp Exchange Server NAME smtp netmask 255.255.255.255 0 0

    access-list SMTP-OUT-I permit tcp host Exchange Server NAME any eq smtp

    I have no problem sending or receiving email.

    When I attempt to change the first rule to the following:

    access-list BORDER35 permit tcp 64.235.144.0 255.255.240.0 eq smtp host XXX.XXX.XX.XX eq smtp

    I cannot receive email sent from an external email account. When I go into Barracuda, it shows the email there, with this message:

    Recipients Action Reason Delivery Status
    Email Address Allowed Spooled (XXX.XXX.XX.XX:451 No response to HELO/EHLO)

    I also cannot do a telnet to the outbound server: telnet dXXXXX.o.ess.barracudanetworks.com 25.

    So my questions are, 1. What rules do I need (or revisions of the ones I have) in order to send and receive from Barracuda. 2. How do I open port 25 so I can telnet to the outbound server?

    I realize these maybe Cisco 101 questions, and I have researched this on the web, but I am getting nowhere at present. I appreciate any help.

Viewing 1 post (of 1 total)

You must be logged in to reply to this topic.

Don't leave your business open to attack! Come learn how to protect your AD in this FREE masterclass!REGISTER NOW - Thursday, December 2, 2021 @ 1 pm ET

Active Directory (AD) is leveraged by over 90% of enterprises worldwide as the authentication and authorization hub of their IT infrastructure—but its inherent complexity leaves it prone to misconfigurations that can allow attackers to slip into your network and wreak havoc. 

Join this session with Microsoft MVP and MCT Sander Berkouwer, who will explore:

  • Whether you should upgrade your domain controllers to Windows Server
    2019 and beyond
  • Achieving mission impossible: updating DCs within 48 hours
  • How to disable legacy protocols and outdated compatibility options in
    Active Directory

Sponsored by: