problem sending e-mail
tom koehler
getting the message, "Cannot send message using the server
smtp.frontiernet.net:tvkoe...@frontiernet.net" and then at the bottom of
this window is a button to "try again using selected server" and guess which
server is selected? the only one I have, the very one also listed in the
trouble message. So, I click the button and poof! the message goes out! It is
like I have my own personal government bureaucrat tucked away inside my
computer - which is a brandy-new imac with Snow Leopard 6.2 innit. As it
turns out, my dear wife has been having the same problem with her outgoing
mail. Her computer is a new laptop with Snow Leopard.
As usual in these cases, I am certainly willing to try to do some detective
work to try to solve this puzzle, but am clueless about where to start or
what to look for.
tom koehler
--
I will find a way or make one.
Bill
tom koehler <tvnospa...@nospamfrontiernet.netinvalid> wrote:
A couple of ideas that may or may not be relevant to your problem:
1. Maybe the server refused the message the first time because of being
busy or some other temporary problem that cleared up by the time you
sent it again.
2. Sometimes when I hit the Reply button on an message I received, the
address does not get formatted in a standard way and that blocks the
sending. However, in that case, I clear up the address formatting
manually before I send again.
tom koehler
(in message
<bbcollins-BE980...@70-3-168-216.pools.spcsdns.net>):
> In article <0001HW.C7618FBA...@news.frontiernet.net>,
> tom koehler <tvnospa...@nospamfrontiernet.netinvalid> wrote:
>
>> Well, I am back, hat in hand, asking for more help. Lately I have been
>> getting the message, "Cannot send message using the server
>> smtp.frontiernet.net:tvkoe...@frontiernet.net" and then at the bottom of
>> this window is a button to "try again using selected server"
> A couple of ideas that may or may not be relevant to your problem:
>
> 1. Maybe the server refused the message the first time because of being
> busy or some other temporary problem that cleared up by the time you
> sent it again.
>
> 2. Sometimes when I hit the Reply button on an message I received, the
> address does not get formatted in a standard way and that blocks the
> sending. However, in that case, I clear up the address formatting
> manually before I send again.
Bill, thank you for your reply and your time.
What has been happening is very recent, and seems to be an automatic failure
to send and an automatic successful send when I click the "try again..."
button, regardless of time of day or length of message.
In replying, my problem is not related to the nature or format of the address
of the recipient of my message. My problem is very strictly as stated,
"Cannot send message..." whether a reply or an original.
You
tom koehler <tvnospa...@nospamfrontiernet.netinvalid> wrote:
Use the "Connection Doctor" to determine what the Server is sending back
as an Error Message, and work from there....
Leonard Blaisdell
tom koehler <tvnospa...@nospamfrontiernet.netinvalid> wrote:
"Cannot send message using the server
> smtp.frontiernet.net:tvkoe...@frontiernet.net"
At the expense of being ridiculed, I've never used an smtp server
address like that in fifteen years of using random smtp servers. For
instance, now my smtp server is smtp.att.yahoo.com with password
authentication.
Have you tried just using smtp.frontiernet.net as your smtp server? I
know I'm missing something.
leo
Chris Ridd
> In article <0001HW.C7618FBA...@news.frontiernet.net>,
> tom koehler <tvnospa...@nospamfrontiernet.netinvalid> wrote:
>
> "Cannot send message using the server
>> smtp.frontiernet.net:tvkoe...@frontiernet.net"
>
> At the expense of being ridiculed, I've never used an smtp server
> address like that in fifteen years of using random smtp servers. For
I suspect the way the address is formatted is just Mail's way of saying
smtp.frontiernet.net using "tvko...@frontiernet.net" to authenticate.
> instance, now my smtp server is smtp.att.yahoo.com with password
> authentication.
> Have you tried just using smtp.frontiernet.net as your smtp server? I
> know I'm missing something.
Mail's Connection Doctor window is quite a handy, yet under-used tool.
--
Chris
Leonard Blaisdell
Chris Ridd <chri...@mac.com> wrote:
> Mail's Connection Doctor window is quite a handy, yet under-used tool.
I knew I was missing something. I've never had to use Connection Doctor
so far. Mumble. I googled smtp with a colon parameter in various
incorrect ways and drew a blank. Thanks.
leo
Cliff
<tvnospa...@nospamfrontiernet.netinvalid> said:
Tom,
Have you tried pinging the smtp mail server? Per the data capture
below, smtp.frontierNET.net does not respond yet smtp.frontier.net
responds. Please try using the smtp.frontier.net mail server.
Cliff
imac2:~ user$ ping smtp.frontier.net
PING mail.brainstorminternet.net (66.118.220.24): 56 data bytes
64 bytes from 66.118.220.24: icmp_seq=0 ttl=50 time=105.657 ms
64 bytes from 66.118.220.24: icmp_seq=1 ttl=50 time=107.065 ms
64 bytes from 66.118.220.24: icmp_seq=5 ttl=50 time=105.541 ms
64 bytes from 66.118.220.24: icmp_seq=7 ttl=50 time=106.927 ms
^C
--- mail.brainstorminternet.net ping statistics ---
8 packets transmitted, 8 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 105.524/106.204/107.713/0.827 ms
imac2:~ user$ ping smtp.frontiernet.net
PING relay.frontiernet.net (66.133.129.10): 56 data bytes
Request timeout for icmp_seq 0
Request timeout for icmp_seq 1
Request timeout for icmp_seq 2
Request timeout for icmp_seq 3
^C
--- relay.frontiernet.net ping statistics ---
5 packets transmitted, 0 packets received, 100.0% packet loss
imac2:~ user$
tom koehler
(in message <leoblaisdell-0830...@News.Individual.NET>):
Thank you. This is the format that my ISP told me I had to use. In trying the
original format from my service provider (as you suggest), the connection is
refused altogether. My ignorance in this area of knowledge is nearly
perfect. This is a rural area, and Frontier is the only player in town. They
say "frog" and I jump.
tom koehler
(in message <2010010117...@news.giganews.com>):
Frontier is a national company and has somewhat different address formats in
the different areas of the country. Here in northeastern Minnesota (Two
Harbors) the format is frontiernet.net, with two nets. Has been, ever since
Frontier bought out Contel, here. In some other service areas, frontier.net
is the proper form.
tom koehler
(in message <you-E58D2C.1...@unknown.hwng.net>):
Thank you. I will try that, the next time I have the problem. Today, Jan 1, I
sent an e-mail and had no problem. Since my wife had the same problem, I am
thinking the problem was with the isp not being able to handle the load over
the holiday. I'm hoping that is the problem, anyway.
tom koehler
(in message <2010010117...@news.giganews.com>):
> On 2009-12-31 00:16:10 -0500, tom koehler
I tried the ping, per your suggestion, with the same results of course. My
ignorance is not diminished any, but my curiosity is piqued. I am going to
modify my outgoing account per your suggestion, to see what happens. dangit,
my address is still frontiernet.net, though. Will see what happens next.
tom koehler
(in message <2010010117...@news.giganews.com>):
>
>
> Tom,
>
> Have you tried pinging the smtp mail server? Per the data capture
> below, smtp.frontierNET.net does not respond yet smtp.frontier.net
> responds. Please try using the smtp.frontier.net mail server.
>
> Cliff
>
>
well, to Cliff and all the rest who have given freely of their time on my
problem, here are my results:
First I freely admit to being a putz, sometimes, and it appears that this may
be one of those times - though the details are still sketchy.
In setting up the new computer, I somehow put the wrong info in for my
outgoing mail server. I went to the well... to the Frontier website, to see
what was what. Though my mail address is frontiernet.net for incoming mail,
my outgoing server wants frontier.COM, and also wants password
authentication. I have made the necessary corrections and sent out a few
messages to test. Maybe the problem is solved. You have all helped in some
way. I am now puzzled why the wrong server info worked at all, even if it was
poorly. Maybe I should not care.
Thank you all. Best wishes for the new year.
Cliff
<tvnospa...@nospamfrontiernet.netinvalid> said:
Glad it worked. Don't worry as we are all putz's at some point in
time. I schedule mine in my calendar so people can be wary of the
quality or lack thereof, of the answer they're getting.
Cliff