E-mail

[radixr]

Is there something wrong with the thread e-mail notification? I'm not getting any emails telling me a thread I subscribed to has a new post.

 

[illflem]

Could be your PM mailbox is full

 

[Doc Tinker]

Radixr, check your profile and make sure the email address is correct. I had the same problem a while back and my address was goofed up from a previous problem on the site.



Doc

 

[radixr]

Doc and illflem,



My email address is correct and my PM box is empty. I don't get it. #@$%! #@$%!



I also verified that the box for email notification was checked before I posted this reply.

 

[barryg41]

radixr, it looks like you have been doing the TDR thing for a while. Looking at the amount of posts that you have posted. Did you change ISP's (Internet Service Provider)?



I know that @HOME has just gave up giving service to Cox. (My Provider) I had to change my email address on TDR.



I had other problems also but it was with Cox.



It's kind of ironic that you had problems today, @home email service has totally dropped Cox or any other users today.



Hope this helps!!

 

[radixr]

Grrrrrrrrrrr!

Dang it! That email notification (about the only aspect of the new forum software that I liked) is still not working. How about it Steve? Any idea of why it's not working for me?:{ :{ :{

 

[admin2]

Your host

Blame your host... . looks like they are blocking mail from TDR:



maillog:Mar 5 17:37:31 linux1788 sendmail[21459]: g25MbQt21457: to=radixr@velocity.net, ctladdr=nobody (99/99), delay=00:00:05, xde

lay=00:00:05, mailer=esmtp, pri=30931, relay=mx. velocity.net. [208. 3. 88. 3], dsn=5. 0. 0, stat=Service unavailable



And a prior log entry:



maillog. 5:Feb 28 05:04:49 linux1788 sendmail[12059]: g1QMMMe13281: to=radixr@velocity.net, ctladdr=nobody (99/99), delay=1+11:42:27,

xdelay=00:00:05, mailer=esmtp, pri=2640898, relay=mx. velocity.net. [208. 3. 88. 3], dsn=4. 2. 0, stat=Deferred: 450 Client host rejected

: cannot find your hostname, [128. 242. 197. 111]

 

[radixr]

It's working now. It must have been my ISP's fault. Thanks everyone.