Re: Found the problem

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

if you are on SBS 2003, Exchange has IMF for filtering out spam.

--
Kevin Weilbacher [SBS-MVP]
"The days pass by so quickly now, the nights are seldom long"


"Applebaum" <mappleNOSPAM@xxxxxxxx> wrote in message
news:OBbuyr7xFHA.1168@xxxxxxxxxxxxxxxxxxxxxxx
> Thanks for your help, everyone.
>
> On Friday, as I prepared to again accept the advice of register.com, as
> well
> as the helpers on this thread, I found that the A record that I (I think
> it
> was me) had set up connecting mail.sa-intl.org to our mail server's IP
> address, was wrong. The IP address was off by one number. Tricky little
> bugger.
>
> Next tasks: Find a solution to our enourmous spam problem, and set up a
> backup mail server.
>
> Thanks again!!!
>
>
> "Applebaum" <mappleNOSPAM@xxxxxxxxxxxxxx> wrote in message
> news:uExFBa6wFHA.2348@xxxxxxxxxxxxxxxxxxxxxxx
>> Hi,
>>
>> We recently switched our DNS services to Register.com. At first, I copied
>> the way our settings had been before. For Mx records, I put in:
>>
>> Host Name Priority Mail Server
>>
>> sa-intl.org High 64.115.124.115
>> it.sa-intl.org High mail.centroitalia.coop.org
>>
>> After I set this up, it worked just fine, or so I thought.
>>
>> Then I checked with Register.com's tech support to verify that I had set
> up
>> the subdomain's (it.) Mx record properly. They said that I had, but they
>> insisted that for our main record, it should say mail.sa-intl.org, and
>> NOT
>> our mail server's IP address, and we should have an A record pointing
>> mail.sa-intl.org to our mail server's IP address.
>>
>> I followed their advice, and we stopped receiving external email. So I
>> switched the Mx record back to our IP address, and we received external
>> email again.
>>
>> But I'm getting reports that people from some domains are unable to email
>> us. They're getting NDRs like:
>>
>> <SAI.sa-intl.org #5.5.0 smtp;550-Verification failed for...
>>
>> And, when I go to DNSreport.com, we get:
>>
>> FAIL: MX is host name, not IP
>> ERROR: You have one or more MX record(s) that contain an IP address.
>> This
>> is not valid. A fully RFC-compliant mailserver will not be able to send
> you
>> mail (although some mail servers will, due to the TCP/IP functions that
> they
>> use). The problem MX records are: 64.115.124.115.
>>
>> also I get:
>>
>> WARN: Multiple MX records
>> WARNING: You only have 1 MX record. If your primary mail server is down
>> or
>> unreachable, there is a chance that mail may have troubles reaching you.
>>
>> But when I followed followed Register.com's advice, we stopped receiving
>> emails. I don't want to mess around with it again without knowing
>> exactly
>> what to do.
>>
>> Many thanks in advance!!!
>>
>> Matthew
>>
>>
>
>


.

Relevant Pages

  • Re: postfix mail server
    ... Building a mail server for 200/300 users (able to grow ... till a thousand) and as a newbie I need an advice ... Marking spam so the user can examine it, ... instead a front device with squirrelmail with iptables ...
    (Debian-User)
  • Found the problem
    ... On Friday, as I prepared to again accept the advice of register.com, as well ... > Host Name Priority Mail Server ... and we stopped receiving external email. ...
    (microsoft.public.backoffice.smallbiz2000)
  • Another Mx Problem
    ... Host Name Priority Mail Server ... I followed their advice, and we stopped receiving external email. ...
    (microsoft.public.backoffice.smallbiz2000)
  • Re: Another Mx Problem
    ... That's what register.com told me, but when I did that, we stopped receiving ... > An MX record should be a host name, ... >> I followed their advice, and we stopped receiving external email. ... If your primary mail server is down ...
    (microsoft.public.backoffice.smallbiz2000)
  • Re: content filtering
    ... opinion on experience that's limited to dealing with domestic US ... Considering that the large majority of spam originates from the US, ... Now all you need is some method of identifying the sender. ... 550 code would come to the attention of the mail server admin who could ...
    (microsoft.public.exchange.admin)