[Elecraft] my ISP sucks

Fri Nov 28 06:35:01 2003

More than likely it has nothing to do with your actual reply address.

Some ISP's, Hosting companies, etc. use a reverse lookup process to validate
mail servers. They do this in an effort to reduce Spam. Sometimes your
actual mail server (not necessarily your domain name) can be black listed or
not have the reverse lookup stuff configured properly.

I know we had one of our servers setup without the "reverse" information
configuration and anytime another local company got mail from this one
server it would bounce. All other mailservers were fine. Since you can send
from Webmail, this is probably the case. This is a big problem and not one
you can solve easily unless you can configure your mail program to use
another SMTP server.

Good luck and 73,
Rich
"Iowa Web Hosting" :)

----- Original Message ----- 
From: <[email protected]>
To: <[email protected]>
Cc: <[email protected]>
Sent: Thursday, November 27, 2003 7:26 PM
Subject: [Elecraft] my ISP sucks

> All of a sudden, I am unable to send messages to the elecraft list because
my ISP cannot be validated by the mail reflector.
>
> Hence, I am attempting to send and recieve mail via Netscape webmail.
>
> This is a genuine pain.
> Have any other list members experienced this problem?
>
> Carl
> WA7CS
> Pasco, WA
>
> __________________________________________________________________
> McAfee VirusScan Online from the Netscape Network.
> Comprehensive protection for your entire computer. Get your free trial
today!
> http://channels.netscape.com/ns/computing/mcafee/index.jsp?promo=393397
>
> Get AOL Instant Messenger 5.1 free of charge.  Download Now!
> http://aim.aol.com/aimnew/Aim/register.adp?promo=380455
> _______________________________________________
> Elecraft mailing list: [email protected]
> You must be subscribed to post to the list.
> To subscribe or unsubscribe see:
http://mailman.qth.net/mailman/listinfo/elecraft
> Elecraft Web Page: http://www.elecraft.com
> Also see: http://www.elecraft.com/elecraft_list_guidelines.htm
>