Re: Question about virus/spam filtering for customers with mail servers

From: Bob Martin (bob_at_buckhorn.net)
Date: 07/27/04

  • Next message: Don Mohlmaster: "Bridging firewall without ip question"
    Date: Tue, 27 Jul 2004 08:53:35 -0500
    To: Pat Lashley <patl+freebsd@volant.org>
    
    

    The issue here isn't the MTA. It's running a primary server as a
    secondary, with the DNS "primary" being unreachable.

    Exim can't fix that, nor postfix or any other MTA.

    The first server to receive the mail should be the primary in DNS.

    Bob

    Pat Lashley wrote:
    > --On Monday, July 26, 2004 15:11:44 -0500 Richard Kuhns <rjk@wintek.com>
    > wrote:
    >
    >> I'm hoping someone will be willing to share a better way to handle this.
    >>
    >> We offer virus/spam filtering for customers with their own mail servers.
    >> We're currently implementing this by configuring the customer's firewall
    >> to only accept smtp connections from our servers (all running sendmail
    >> under FreeBSD 4), and the customer's MX records point to their server
    >> first and our server(s) second and third. In most cases this works just
    >> fine -- attempts by a mail server to deliver mail directly to the
    >> customer
    >> fail, the mail server tries the secondary MX site (us), we accept and
    >> filter the message and deliver it to the customer (or not).
    >>
    >> Sometimes, though, there's a very long delay for messages to be delivered
    >> - up to several days. In each case I've been able to track down, it's
    >> been
    >> a Microsoft Exchange 2000 server that has issues with sending messages to
    >> the secondary mail server.
    >>
    >> Does anyone have a good way we could use to list our server as the
    >> primary,
    >> and then forward the messages? I've been going through the bat book, but
    >> the indexing leaves a little to be desired and I haven't found anything
    >> that looks applicable yet.
    >>
    >> Any suggestions would be greatly appreciated. Thanks in advance...
    >
    >
    > If you're willing to abandon Sendmail, this sort of thing is trivial
    > with Exim.
    >
    >
    >
    > -Pat
    > _______________________________________________
    > freebsd-isp@freebsd.org mailing list
    > http://lists.freebsd.org/mailman/listinfo/freebsd-isp
    > To unsubscribe, send any mail to "freebsd-isp-unsubscribe@freebsd.org"
    _______________________________________________
    freebsd-isp@freebsd.org mailing list
    http://lists.freebsd.org/mailman/listinfo/freebsd-isp
    To unsubscribe, send any mail to "freebsd-isp-unsubscribe@freebsd.org"


  • Next message: Don Mohlmaster: "Bridging firewall without ip question"

    Relevant Pages

    • Re: DNS and email problem
      ... Basically our situation boils down to Comcast performing ... a reverse DNS to the wrong IP address for our mail server but I'm not ... The "error" is that our mail server does have a correct PTR and all ...
      (microsoft.public.windows.server.sbs)
    • Re: Noob : Is BIND necessary for mail server ?
      ... Another DNS that will also work fine is ... > djdns from the guy that made qmail. ... This is my first mail server set up, and I can say that I now have it up ...
      (alt.os.linux.redhat)
    • Re: Unable to bind to the destination server in DNS
      ... > Not sure were to post this one, but I'll start in the DNS discussion. ... > My gateway mail server (Win2k3 IIS6 SMTP) will stop delivering ...
      (microsoft.public.windows.server.dns)
    • Re: Delivery takes several days.
      ... Could be either greylisting or DNS ... DNS server dns3.ptd.netis alive and authoritative ... HTTP server www.ptd.netanswers on port 80 ... Mail server smtpin.ptd.netanswers on port 25 ...
      (microsoft.public.exchange.admin)
    • Re: Delivery takes several days.
      ... Could be either greylisting or DNS ...   Got DNS list for 'ptd.net' from i.gtld-servers.net ... DNS server dns3.ptd.netis alive and authoritative ... Mail server smtpin.ptd.netanswers on port 25 ...
      (microsoft.public.exchange.admin)