New Problem..... cannot access POP email account?

Status
This thread has been Locked and is not open to further replies. The original thread starter may use the Report button to request it be reopened but anyone else with a similar issue should start a New Thread. Watch our Welcome Guide to learn how to use this site.

BigDaveinNJ

Thread Starter
Joined
Jun 9, 2000
Messages
898
OK... one problem solved... another one surfaces. My problems of extremely poor DOWNLOAD times was rectified when I tried... just for the hell of it.... a freeware connectivity tool called WinOPTIMIZER3000.... after installing this program my DOWNLOAD speeds went from about 54k to over 2000kbps :) Evidently.... it tweaked one of my settings that must have been set for dial-up....anyway... my surfing is now great!

Anyway.... I can no longer access my dial-up accounts email with OUTLOOK EXPRESS when I try to send or receive mail.... I get this error message.
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

The message could not be sent because one of the recipients was rejected by the server. The rejected e-mail address was .XXXXXXXXXXXXX Subject 'Just a quick note :)', Account: 'mail.XXXXXXXXXX.com Server: 'smtp.XXXXXXXXXX.com', Protocol: SMTP, Server Response: '550 5.7.1 .. Relaying denied', Port: 25, Secure(SSL): No, Server Error: 550, Error Number: 0x800CCC79


Now... I was told that as long as my account was still active and was POP3 I still should be able to use my OUTLOOK EXPRESS as before to send and receive email.

When I go to TOOLS/ACCOUNTS .... my original dial-up servers are still listed as the active accounts but I am not able to send or receive email without getting these error messages.

What should I do? If my dial-up mail server is POP3, why is it rejecting my email? Are there setting changes I should look into?

Thanks in advance

DAVID
 
Joined
Dec 2, 1998
Messages
2,736
Does that happen with all emails? Just curious because the message stated "because one of the recipients was rejected by the server" which would lead me to believe it simply had a problem with one of the addresses you were sending it to, not necessarily that it's from you.

Also found some additional information (below). Not sure what changes that little tweak made that would cause that.

CAUSE
This problem can occur with the following configurations:

You are logged in to a Local Area Network that has an Internet gateway and attempt to send e-mail through an Internet Service Provider's SMTP gateway.


You are dialed into an Internet Service Provider and attempt to send e-mail through another Internet Service Provider's SMTP gateway.


You are using a cable modem or ADSL to get to another Internet Service Provider and attempt to send e-mail through that ISP's SMTP gateway.





RESOLUTION
This problem affects all messaging clients, regardless of manufacturer.

Customers should contact their ISP for assistance since this problem is not caused by the e-mail client. From a messaging client standpoint, there are no solutions for customers who have ISP's that block all SMTP Relay traffic.

Most of the new SMTP e-mail gateway software can allow relaying for specific IP addresses. This is how cable modem and ASDL users will be able to continue to use their same ISP. The Cable Modem/ASDL provider must provide the customer a static IP address, in-turn the customer's e-mail ISP will allow relaying for that specific IP address. Banks of IP addresses can also be allowed, which may provide a workaround for some corporate customers who access ISP's through their corporate Local Area Networks.

If the error is random, it is possible that your SMTP server is checking whether the domain or the recipient name actually exists before sending. If the recipient's mail server is temporarily down or unavailable for another reason, such as high network volume, your SMTP server cannot verify the address and may reject the relay. In this case, no action is required. The message will be sent when the receiving server is again available.



MORE INFORMATION
This problem may become more common as ISP's begin to take action against SPAM e-mail. SPAM is flooding the Internet with many copies of the same message, in an attempt to send the message to people who would not otherwise choose to receive it. Most SPAM uses an automated system to send commercial advertising, or mass marketing e-mail messages. SPAM costs the sender very little to send; most of the costs are paid for by the recipient or the e-mail providers.

Some ISP's are fighting SPAM by requiring each user to be dialed directly into their system in order to send e-mail through their SMTP gateway. This is an easy way to control SPAM but may affect some users who tunnel into their e-mail account from another ISP.

MSN, the Microsoft Network, is just one example of an ISP that has already imposed SPAM blocking. Additionally, MSN has imposed restrictions whereby, if the e-mail address in your Internet account properties does not match that of your MSN account, you may also receive SMTP blocking errors. This affects users who receive mail with two different Internet addresses, but want the same reply address on both e-mail accounts. Other ISP's implement similar strategies.

Examples:
Employees have personal ISP accounts at <isp.com> where <isp.com> is your Service Provider's domain name. They use the company's corporate LAN to access their <isp.com> e-mail. They have no problems sending or receiving. One day they start receiving SMTP blocking errors when they try to reply to e-mail that they have received from <isp.com>. They contact <isp.com> technical support and are told that <isp.com> just installed new SMTP gateway software which prevents SMTP relaying. Now the employees can receive e-mail through the LAN, but cannot send e-mail because they're not connected directly to <isp.com>.


A user has two ISP accounts, one with <isp.com> and one with <myisp.net> where <isp.com> and <myisp.net> are the Service Providers' domain names. The user dials into <myisp.net> and is able to both send and receive mail from both accounts without problems. One day the user connects to <myisp.net>, trys to send mail through <isp.com> and receives blocking errors. The user connects directly to <isp.com> and can still send and receive mail with both accounts. In this example <isp.com> implemented SMTP relay blocking and <myisp.net> did not.
 

BigDaveinNJ

Thread Starter
Joined
Jun 9, 2000
Messages
898
Yes Angel....it happens with ALL emails. I have tried sending emails to several friends...even to MYSELF, to no avail :(

Any ideas very much appreciated.

DAVID
 
Joined
Dec 2, 1998
Messages
2,736
David,

Looks like I edited my post while you were replying - sorry! See above.
:)
 
Status
This thread has been Locked and is not open to further replies. The original thread starter may use the Report button to request it be reopened but anyone else with a similar issue should start a New Thread. Watch our Welcome Guide to learn how to use this site.

Users Who Are Viewing This Thread (Users: 0, Guests: 1)

As Seen On
As Seen On...

Welcome to Tech Support Guy!

Are you looking for the solution to your computer problem? Join our site today to ask your question. This site is completely free -- paid for by advertisers and donations.

If you're not already familiar with forums, watch our Welcome Guide to get started.

Join over 807,865 other people just like you!

Latest posts

Top