email error 452 - different

[Robobroker]

I know that the normal explanation for "Error 452 too many recipients" is
that the ISP is limiting the number of allowed recipients to a certain
amount. However in this case something else is going on.

My ISP is NOT limiting me. In fact I have worked with them to ensure this
(I send a newsletter to a very large group.) On my old computer it worked
fine - all 1300 adresses went out and were delivered. However on the new
computer - all Outlook email account settings set up identically - I get the
immediate "error 452 too many recipients" message.

Everything I can find is set up just the same: SMTP, timeouts, ports, etc.
I'm using the same network connection. Everything. But one computer sends
out just fine and the other one won't do it. So I know it's not an ISP
limitation, but something about the new computer setup. Any ideas?

 

[N. Miller]

I know that the normal explanation for "Error 452 too many recipients" is
that the ISP is limiting the number of allowed recipients to a certain
amount. However in this case something else is going on.

My ISP is NOT limiting me. In fact I have worked with them to ensure this
(I send a newsletter to a very large group.) On my old computer it worked
fine - all 1300 adresses went out and were delivered. However on the new
computer - all Outlook email account settings set up identically - I get the
immediate "error 452 too many recipients" message.

Everything I can find is set up just the same: SMTP, timeouts, ports, etc.
I'm using the same network connection. Everything. But one computer sends
out just fine and the other one won't do it. So I know it's not an ISP
limitation, but something about the new computer setup. Any ideas?

Not a clue. The problem is, SMTP 4xx error codes are returned by the server,
not the client. So, without looking at the configuration myself, I can't
figure out why the behavior of two identical configurations would be
different.

 

[N. Miller]

Not a clue. The problem is, SMTP 4xx error codes are returned by the server,
not the client. So, without looking at the configuration myself, I can't
figure out why the behavior of two identical configurations would be
different.

Just a though: Turn on session logging. Don't know how to do it in Outlook,
but there must be a way. Do it on the system which is failing, and the one
which is not, and compare the logs.