Re: Outbound email, but no inbound

I think you've got a misconfiguration, as in an IP restriction on incoming
mail. Try your Default SMTP Virtual Server properties - on the General Tab,
is (All Unassigned) set as the IP address?

How are the Relay Restrictions configured (Access Tab, Relay Button).

--
Les Connor [SBS Community Member - SBS MVP]
-----------------------------------------------------------
SBS Rocks !


"Clarence" <Clarence@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:77F1F942-7275-4126-AB9C-3A297403513D@xxxxxxxxxxxxxxxx
> Les,
>
> Thanks for the reply... Sorry that I neglected to say that I ran this
> before and saw the errors... I did check with the ISP provider and of
> course
> they say all is okay... However, I did ask for a senior tech to give me a
> call back (still waiting)...
>
> Also, the info that follows is from an email headerfrom an email sent from
> an external source and was denied... Does this reveal anything that might
> point directly to what the issue is?
>
>>>>>>
>
> The original message was received at Mon, 8 Aug 2005 10:05:51 -0400 (EDT)
> from imo-m23.mail.aol.com [172.20.107.69]
>
>
> *** ATTENTION ***
>
> Your e-mail is being returned to you because there was a problem with its
> delivery. The address which was undeliverable is listed in the section
> labeled: "----- The following addresses had permanent fatal errors -----".
>
> The reason your mail is being returned to you is listed in the section
> labeled: "----- Transcript of Session Follows -----".
>
> The line beginning with "<<<" describes the specific reason your e-mail
> could
> not be delivered. The next line contains a second error message which is
> a
> general translation for other e-mail servers.
>
> Please direct further questions regarding this message to the e-mail
> administrator or Postmaster at that destination.
>
> --AOL Postmaster
>
>
>
> ----- The following addresses had permanent fatal errors -----
> <dnorton@xxxxxxxxxxxx>
>
> ----- Transcript of session follows -----
> ... while talking to mail.microkey.com.:
>>>> MAIL From:<NOTTIE@xxxxxxx> SIZE=590
> <<< 454 5.7.3 Client does not have permission to submit mail to this
> server.
> <dnorton@xxxxxxxxxxxx>... Deferred: 454 5.7.3 Client does not have
> permission to
> submit mail to this server.
> Message could not be delivered for 3 hours
> Message will be deleted from queue
>
> Final-Recipient: RFC822; dnorton@xxxxxxxxxxxx
> Action: failed
> Status: 4.4.7
> Remote-MTA: DNS; mail.microkey.com
> Diagnostic-Code: SMTP; 454 5.7.3 Client does not have permission to submit
> mail
> to this server.
> Last-Attempt-Date: Mon, 8 Aug 2005 13:07:37 -0400 (EDT)
>
> Received: from imo-m23.mx.aol.com (imo-m23.mail.aol.com [172.20.107.69])
> by
> imr-d03.mx.aol.com (v98.19) with ESMTP id RELAYIN1-242f766bf280; Mon, 08
> Aug
> 2005 10:05:51 -0400
> Received: from NOTTIE@xxxxxxx
> by imo-m23.mx.aol.com (mail_out_v38_r4.1.) id 3.83.2d237525 (16109)
> for <dnorton@xxxxxxxxxxxx>; Mon, 8 Aug 2005 08:18:13 -0400 (EDT)
> Received: from MBLK-M27 (mblk-m27.mblk.aol.com [64.12.136.71]) by
> air-id12.mx.aol.com (v107.10) with ESMTP id MAILINID121-3eed42f74d851f9;
> Mon, 08
> Aug 2005 08:18:13 -0400
> Date: Mon, 08 Aug 2005 08:18:13 -0400
> From: nottie@xxxxxxx
> Message-Id: <8C76A2A6220FB89-FF4-6FDC@xxxxxxxxxxxxxxxxxxxxxxx>
> X-MB-Message-Source: WebUI
> X-MB-Message-Type: User
> Received: from 199.72.34.130 by MBLK-M27.sysops.aol.com (64.12.136.71)
> with
> HTTP
> (WebMailUI); Mon, 08 Aug 2005 08:18:13 -0400
> X-Mailer: AOL WebMail 1.1.0.13507
> Subject: test into work
> Content-Type: multipart/alternative;
>
> boundary="--------MailBlocks_8C76A2A6220FB89_FF4_66E3_MBLK-M27.sysops.aol.com"
> MIME-Version: 1.0
> To: dnorton@xxxxxxxxxxxx
> X-AOL-IP: 172.20.107.69
> X-Spam-Flag: NO
>
>>>>>>
>
> Once again, thanks for the assistance!
>
> "Les Connor [SBS Community Member - SBS M" wrote:
>
>> Hi Clarence,
>>
>> Here's a link to a report for microkey.com, and mail.microkey.com is
>> indeed
>> unreachable from the internet. There are a number of warnings in the
>> report,
>> have a look and see if you need to discuss these with your ISP or domain
>> host.
>>
>> Hang on. Now it's reachable.
>>
>> http://www.dnsreport.com/tools/dnsreport.ch?domain=microkey.com
>>
>> --
>> Les Connor [SBS Community Member - SBS MVP]
>> -----------------------------------------------------------
>> SBS Rocks !
>>
>>
>> "Clarence" <Clarence@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
>> news:D038E29D-CBE7-4DF2-B2EE-CB435F72D639@xxxxxxxxxxxxxxxx
>> > Hi Les,
>> >
>> > Our domain is microkey.com
>> > MX record points to mail.microkey.com
>> >
>> > If any other info needed, just inquire....
>> >
>> > Thnaks for the reply!
>> >
>> > "Les Connor [SBS Community Member - SBS M" wrote:
>> >
>> >> Hi Clarence,
>> >>
>> >> What's your domain name, we'll check it out.
>> >>
>> >> --
>> >> Les Connor [SBS Community Member - SBS MVP]
>> >> -----------------------------------------------------------
>> >> SBS Rocks !
>> >>
>> >>
>> >> "Clarence" <Clarence@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
>> >> news:0F9F2776-84F5-4293-A043-0B0CCDFDFE94@xxxxxxxxxxxxxxxx
>> >> > Can anyone assist me i determining the actions needed to correct
>> >> > this
>> >> > issue:
>> >> >
>> >> > Using a single nic, behing a Watchguard firewall
>> >> >
>> >> > - Outbound email has been configured and is working.
>> >> > - No inbound email
>> >> > - Verified port 25 (tcp) open o firewall both ways
>> >> > - verified using 'telnet maila.microsoft.com 25' and recv'd
>> >> > appropiate
>> >> > response, then used 'ehlo microkey.com' and recv'd a bunch of 250
>> >> > replies
>> >> > - MX record on ISP's dns server, however the authoratative dns
>> >> > servers
>> >> > used
>> >> > are those at our telco (not same dns servers).. NOTE: Recv'd email
>> >> > fine
>> >> > under system we migrated from..
>> >> > - Not really sure what I'm missing as everything seems to be setup
>> >> > correctly...
>> >> > - IS it necessary to have a MX record on the local dns server (SBS
>> >> > box)??
>> >> >
>> >> > Thank you for any assistance o this matter!!
>> >> >
>> >> >
>> >>
>> >>
>> >>
>>
>>
>>


.