|
List Info
Thread: Odd Behavior
|
|
| Odd Behavior |
 
New Zealand |
2007-03-29 10:27:37 |
Hi,
I'm seeing and getting reports of odd behavior...and its
been
plaguing me for months. Its a good thing I have patient
clients
because this error msg makes no sense to me. The reason it
doesn't
make sense is that the address and really any address that's
got
bouncing mail like what is below, will eventually receive
the msg.
Eventually. When I say 'eventually'...I mean the sender
will keep
trying to send the msg and eventually it will get through.
So my question is this:
What would cause the following ?
+++++++++++++++++++
The following addresses had delivery problems:
<miles xxxxxxxx.com>
Permanent Failure:
550_relaying_blocked,_read_new_mail,_add_204.127.225.95_to_f
orwarding_or
_enable_smtp_authentication_in_
Delivery last attempted at Thu, 29 Mar 2007 03:35:26 -0000
+++++++++++++++++++
M i l e s.
|
|
| Re: Odd Behavior |
New Zealand |
2007-03-29 12:08:20 |
|
| There are two times my clients get this. All stemming from the fact that surgemail requires pop before smtp.
1. They are on dialup, retreive their mail, disconnected or were disconnected by a 15 minute timeout, and then tried to send the message. When they come back on the internet, they are giving a different IP address then what they logged in with and surgemail thinks somebody is pretending to be them since the ip never logged in. Just hitting send and receive again while connected or checking and then sending solves that.
2. They use outlook. Composed an email before retrieving mail in the last few hours and tried to send. Some (maybe all) versions of outlook like to send as/before they login to retrieve mail. Surgemail does not have them recorded as logging in and gives them the same reason as #1 above. Hitting send and receive again fixes that.
I have dialup clients as well as broadband, but if you have dialup clients. Make sure the hang up after sending and receiving option is not checked as this will make issue #1 occur every time. . On Mar 29, 2007, at 8:27 AM, m i l e s wrote:
Hi,
I'm seeing and getting reports of odd behavior...and its been plaguing me for months. Its a good thing I have patient clients because this error msg makes no sense to me. The reason it doesn't make sense is that the address and really any address that's got bouncing mail like what is below, will eventually receive the msg. Eventually. When I say 'eventually'...I mean the sender will keep trying to send the msg and eventually it will get through.
So my question is this:
What would cause the following ?
+++++++++++++++++++
The following addresses had delivery problems:
< miles xxxxxxxx.c om">milesxxxxxxxx.com> Permanent Failure: 550_relaying_blocked,_read_new_mail,_add_204.127.225.95_to_forwarding_or_enable_smtp_authentication_in_ Delivery last attempted at Thu, 29 Mar 2007 03:35:26 -0000
+++++++++++++++++++
M i l e s.
Jody McAlister In-Site Communications (707)765-9993/(866)376-7076 info iscweb.com ">infoiscweb.com
|
| RE: Odd Behavior |
New Zealand |
2007-03-29 12:52:07 |
|
Several things.
1). Surge doesn't INSIST on Pop before SMTP, that's a
config setting you choose.
2). Outlook has a check box on the "More Settings" pages,
the Servers tab, to do PoP before SMTP, so that problem can be
solved.
3). Outlook Express has a similar setting, where you fill
in "My server requires me to log in", and you put your login
info.
FYI
Glenn Meadows
Sheridan Square Entertainment
There are two times my clients get this. All stemming from the fact
that surgemail requires pop before smtp.
1. They are on dialup, retreive their mail, disconnected or were
disconnected by a 15 minute timeout, and then tried to send the message. When
they come back on the internet, they are giving a different IP address then
what they logged in with and surgemail thinks somebody is pretending to be
them since the ip never logged in. Just hitting send and receive again while
connected or checking and then sending solves that.
2. They use outlook. Composed an email before retrieving mail in the last
few hours and tried to send. Some (maybe all) versions of outlook like to send
as/before they login to retrieve mail. Surgemail does not have them recorded
as logging in and gives them the same reason as #1 above. Hitting send and
receive again fixes that.
I have dialup clients as well as broadband, but if you have dialup
clients. Make sure the hang up after sending and receiving option is not
checked as this will make issue #1 occur every time.
.
On Mar 29, 2007, at 8:27 AM, m i l e s wrote:
Hi,
I'm seeing and getting reports of odd
behavior...and its been plaguing me for months. Its a good thing I have patient clients
because this error msg makes no sense to me. The reason it doesn't make sense is that
the address and really any address that's got bouncing mail like what is
below, will eventually receive the msg.
Eventually. When I say
'eventually'...I mean the sender will keep trying to send the msg and
eventually it will get through.
So my question is this:
What would cause the following ?
+++++++++++++++++++
The following addresses had delivery
problems:
Permanent Failure:
550_relaying_blocked,_read_new_mail,_add_204.127.225.95_to_forwarding_or_enable_smtp_authentication_in_
Delivery last attempted at Thu, 29 Mar 2007
03:35:26 -0000
+++++++++++++++++++
M i l e s.
Jody McAlister
In-Site Communications
(707)765-9993/(866)376-7076
info iscweb.com ">infoiscweb.com
|
| Re: Odd Behavior |
New Zealand |
2007-03-29 13:00:33 |
|
| It is the default behavior though so you really only choose to not use it.
Good info on 2. I've gotten so used to telling them to send and receive again, that I never looked for the more settings to make it do pop before smtp. On Mar 29, 2007, at 10:52 AM, Glenn Meadows wrote: Several things. 1). Surge doesn't INSIST on Pop before SMTP, that's a config setting you choose. 2). Outlook has a check box on the "More Settings" pages, the Servers tab, to do PoP before SMTP, so that problem can be solved. 3). Outlook Express has a similar setting, where you fill in "My server requires me to log in", and you put your login info. FYI Glenn Meadows
Sheridan Square Entertainment
There are two times my clients get this. All stemming from the fact that surgemail requires pop before smtp.
1. They are on dialup, retreive their mail, disconnected or were disconnected by a 15 minute timeout, and then tried to send the message. When they come back on the internet, they are giving a different IP address then what they logged in with and surgemail thinks somebody is pretending to be them since the ip never logged in. Just hitting send and receive again while connected or checking and then sending solves that.
2. They use outlook. Composed an email before retrieving mail in the last few hours and tried to send. Some (maybe all) versions of outlook like to send as/before they login to retrieve mail. Surgemail does not have them recorded as logging in and gives them the same reason as #1 above. Hitting send and receive again fixes that.
I have dialup clients as well as broadband, but if you have dialup clients. Make sure the hang up after sending and receiving option is not checked as this will make issue #1 occur every time. . On Mar 29, 2007, at 8:27 AM, m i l e s wrote: Hi,
I'm seeing and getting reports of odd behavior...and its been plaguing me for months. Its a good thing I have patient clients because this error msg makes no sense to me. The reason it doesn't make sense is that the address and really any address that's got bouncing mail like what is below, will eventually receive the msg. Eventually. When I say 'eventually'...I mean the sender will keep trying to send the msg and eventually it will get through.
So my question is this:
What would cause the following ?
+++++++++++++++++++
The following addresses had delivery problems:
< miles xxxxxxxx.c om">milesxxxxxxxx.com>Permanent Failure: 550_relaying_blocked,_read_new_mail,_add_204.127.225.95_to_forwarding_or_enable_smtp_authentication_in_ Delivery last attempted at Thu, 29 Mar 2007 03:35:26 -0000
+++++++++++++++++++
M i l e s.
Jody McAlister In-Site Communications (707)765-9993/(866)376-7076 info iscweb.com ">infoiscweb.com
Jody McAlister In-Site Communications (707)765-9993/(866)376-7076 info iscweb.com ">infoiscweb.com
|
| RE: Odd Behavior |
New Zealand |
2007-03-29 13:13:51 |
|
|
We've just set our servers to require SMTP Authentication,
a simple check box on the servers page.
Glenn Meadows
Sheridan Square Entertainment
It is the default behavior though so you really only choose to not
use it.
Good info on 2. I've gotten so used to telling them to send and receive
again, that I never looked for the more settings to make it do pop before
smtp.
On Mar 29, 2007, at 10:52 AM, Glenn Meadows wrote:
Several things.
1). Surge doesn't INSIST on Pop before SMTP, that's a
config setting you choose.
2). Outlook has a check box on the "More Settings"
pages, the Servers tab, to do PoP before SMTP, so that problem can be
solved.
3). Outlook Express has a similar setting, where you
fill in "My server requires me to log in", and you put your login
info.
FYI
Glenn Meadows
Sheridan Square Entertainment
There are two times my clients get this. All stemming from the
fact that surgemail requires pop before smtp.
1. They are on dialup, retreive their mail, disconnected or were
disconnected by a 15 minute timeout, and then tried to send the message.
When they come back on the internet, they are giving a different IP
address then what they logged in with and surgemail thinks somebody is
pretending to be them since the ip never logged in. Just hitting send and
receive again while connected or checking and then sending solves
that.
2. They use outlook. Composed an email before retrieving mail in the
last few hours and tried to send. Some (maybe all) versions of outlook
like to send as/before they login to retrieve mail. Surgemail does not
have them recorded as logging in and gives them the same reason as #1
above. Hitting send and receive again fixes that.
I have dialup clients as well as broadband, but if you have dialup
clients. Make sure the hang up after sending and receiving option is not
checked as this will make issue #1 occur every time.
.
On Mar 29, 2007, at 8:27 AM, m i l e s wrote:
Hi,
I'm seeing and getting reports of odd
behavior...and its been plaguing me for months. Its a good thing I have patient
clients because this error msg makes no sense to me. The reason it doesn't make sense is
that the address and really any address that's got bouncing mail like
what is below, will eventually receive the msg. Eventually. When I say 'eventually'...I mean the
sender will keep trying to send the msg and eventually it will get
through.
So my question is this:
What would cause the following ?
+++++++++++++++++++
The following addresses had delivery
problems:
Permanent Failure:
550_relaying_blocked,_read_new_mail,_add_204.127.225.95_to_forwarding_or_enable_smtp_authentication_in_
Delivery last attempted at Thu, 29 Mar
2007 03:35:26 -0000
+++++++++++++++++++
M i l e s.
Jody McAlister
In-Site Communications
(707)765-9993/(866)376-7076
info iscweb.com ">infoiscweb.com
Jody McAlister
In-Site Communications
(707)765-9993/(866)376-7076
info iscweb.com ">infoiscweb.com
|
[1-5]
|
|