Grant,

It is not likely that the CNAME is the cause of the problem as most mail
servers now handle that. IMail now does, but not sure if that was fixed in
the 4.0 series or later. I think it was by 4.07, but memory fails me right
now.

Try putting your 'local' addresses in the Relay table and see what that does
for you.

>From what I know of DirectPC, yes, it is 'one way' but does it not use is a
modem connection for the other direction? So you end up with a normal duplex
connection, with one way much faster (but may have other delays).

I'd also try the IMail client on the server to send an outside email. If
that works, then IMail itself and your 'net connection are likely to be OK.
If not then look at logs to see what happened and use telnet as Kevin
suggested. If OK, then the problem would seem to be the connection between
your client and the server. Use telnet again, from the client machine, to
see if you can connect to the SMTP service of IMail.

Daniel Donnelly
Ipswitch Technical Support
________________________________________________________
See our Knowledge Base at http://support.ipswitch.com/kb

----- Original Message -----
From: "Grant Griffith" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, July 19, 2000 10:37 AM
Subject: Re: [IMail Forum] Weird Problem Sending Mail!


> Hello Daniel,
>
>    Thanks for the reply.  We are currently co-located at Cinternet, they
take care of all of our names server stuff.  I was unaware that they had the
priority 10 and 15 MX is going to them, but the priority 5 is going to our
server.
>
>    The error I gave was from MS Outlook 2000.  Didn't think it would be of
much help, but wanted to pass it along in case.
>
>    As for the 'Control Access' I have not done anything with it forever!
I think I actually had this problem all along if I was not using the
satelite connection via DirecPC.  But now that I have quit DirecPC it is a
REAL problem.
>
>    I just find it confusing that it works when using DirecPC when DirecPC
is only one way and that is in receiving information.
>
>    I just tried setting it SMTP to Relay ALL Mail and stopped and
restarted the service.  The problem still exists.  Could the CNAME and A
Record problems possibly cuase this?
>
> Thanks,
> Grant Griffith
>
> ---------- Original Message ----------------------------------
> From: "Daniel Donnelly" <[EMAIL PROTECTED]>
> Reply-To: [EMAIL PROTECTED]
> Date: Wed, 19 Jul 2000 09:48:24 -0400
>
> >Grant,
> >
> >Normally, when using 'Relay for Addresses', one would enter all your
'local'
> >addresses in the table, to allow those computers on your network, to
relay
> >via IMail.
> >
> >I just checked DNS and the secondary MX host I find is not IMail, nor
does
> >it VRFY your email address. So I'm not sure how you are 'getting' new
email
> >to the IMail accounts, if that route is used.
> >
> >ei8htlegs.net.
> >    nameserver = NS2.CINTERNET.NET.
> >    nameserver = NS1.CINTERNET.NET.
> >    5, mail.ei8htlegs.com.
> >    10, MX.CINTERNET.NET.
> >    15, MX2.CINTERNET.NET.
> >
> >MX.CINTERNET.NET.
> >    206.112.217.12
> >
> >However the highest priority server is IMail and does recognise your
> >account, so that is good and the most likely route to be used. It would
not
> >relay an email to me.
> >
> >The error you show is not very helpful and I suspect it is from your
email
> >client. Are you sure you did not touch the 'Control Access' for the SMTP?
> >That, set incorrectly, can limit who can connect to the SMTP service and
you
> >might have set it to block all local access rather than accept local
access.
> >
> >I would normally use the full name, mail.ei8htlegs.net, as the POP/SMTP
> >server name. But I see in DNS that this is a CNAME used in the MX records
> >and that is NOT recommended! MX records should always point to a hostname
> >(FGDN) and that hostname (FQDN) should always have an A record. So
> >ei8htlegs.net should work OK at the clients SMTP/POP3 names.
> >
> >Daniel Donnelly
> >Ipswitch Technical Support
> >________________________________________________________
> >See our Knowledge Base at http://support.ipswitch.com/kb
> >
> >----- Original Message -----
> >From: "Grant Griffith" <[EMAIL PROTECTED]>
> >To: "IMail" <[EMAIL PROTECTED]>
> >Sent: Tuesday, July 18, 2000 10:12 PM
> >Subject: [IMail Forum] Weird Problem Sending Mail!
> >
> >
> >> Hello All,
> >>
> >>    I have been using DirecPC for about a year and I have been able to
> >receive and send mail fine using OutLook 2000.
> >>
> >>    Well, I am wanting to cancel DirecPC and just go with straight modem
> >connection.  However I am not able to send mail all of a sudden.  I can
> >receive it fine, but it keeps giving me the following Error Code:
0x800ccc0e
> >(Unable to connect to the Server (ei8htlegs.net))!
> >>
> >>    My server setting are set-up to Relay only mail for local addresses
> >(edit local address table)!  My address table is currently empty!
> >>
> >>    Any help would be great!
> >>
> >> --
> >> Sincerely,
> >> Grant Griffith, Vice President
> >> EI8HT LEGS Web Management Co., Inc.
> >> http://www.ei8htlegs.net
> >> Bus. Phone: (877) 483-3393
> >> Cell Phone: (513) 602-2257
> >>
> >> http://www.route-one.com - South-Eastern Indiana Website
> >> http://www.getafreewebsite.com
> >> --
> >> Please visit http://www.ipswitch.com/support/mailing-lists.html
> >> to be removed from this list.
> >>
> >> An Archive of this list is available at:
> >> http://www.mail-archive.com/imail_forum%40list.ipswitch.com/
> >>
> >
> >Please visit http://www.ipswitch.com/support/mailing-lists.html
> >to be removed from this list.
> >
> >An Archive of this list is available at:
> >http://www.mail-archive.com/imail_forum%40list.ipswitch.com/
> >
> Please visit http://www.ipswitch.com/support/mailing-lists.html
> to be removed from this list.
>
> An Archive of this list is available at:
> http://www.mail-archive.com/imail_forum%40list.ipswitch.com/
>

Please visit http://www.ipswitch.com/support/mailing-lists.html 
to be removed from this list.

An Archive of this list is available at:
http://www.mail-archive.com/imail_forum%40list.ipswitch.com/

Reply via email to