Here I am

site not notifying of posts

Attention: TDR Forum Junkies
To the point: Click this link and check out the Front Page News story(ies) where we are tracking the introduction of the 2025 Ram HD trucks.

Thanks, TDR Staff

forum databases repaired, still slow?

Site outage (1/25 12:30am-2:20pm)

FYI the site is not sending emails notifying of posts? Also does not seem to be showing new posts on threads? The posts are on the threads but it does not show the number of replys. Hope you understand what I am trying to communicate :(
 
Check to see if your ISP has enabled a spam blocker on your email account. I've had several people that all of a sudden weren't getting their notification emails and when they checked their ISP had turned on a spam blocker. They checked it and sure enough there were the email notifications. My ISP has it and I can check the spam blocker account and it will show me all the emails that it's blocked from sending to me.



On the replies if you are using speed up software it will sometimes cache some pages and therefore won't update the reply numbers. It's working fine here and I tested it at a client today on a dial up and it worked fine there too.
 
Originally posted by Steve St. Laurent

Check to see if your ISP has enabled a spam blocker on your email account.




Checked my ISP AT&T Worldnet, no blocker and no blocked messages? Also was getting them fine and then 2 days ago just stopped. :confused: Anything you can do to help would be great.
 
AT&T is rejecting our emails. Here is the data from the logs:



Jan 24 01:54:11 turbodieselregister sendmail[23639]: h0O1sAQ23637: to=(****your email address deleted****)@worldnet. att.net, ctladdr=nobody (65534/65534), delay=00:00:01, xdelay=00:00:00, ma

iler=esmtp, pri=30939, relay=gateway1. worldnet. att.net. [204. 127. 134. 23], dsn=5. 0. 0, stat=Service unavailable



Jan 24 01:54:11 turbodieselregister sendmail[23639]: h0O1sAQ23637: h0O1sBP23639:

DSN: Service unavailable



You may try contacting AT&T with that information and see what they can do about it.



Here's an example of one right after yours that went through fine:



Jan 24 01:57:54 turbodieselregister sendmail[23691]: h0O1von23689: to=(***email address deleted***)@attbi.com, ctladdr=nobody (65534/65534), delay=00:00:04, xdelay=00:00:04, mailer=

esmtp, pri=30924, relay=gateway. attbi.com. [216. 148. 227. 70], dsn=2. 0. 0, stat=Sent (Message received: 20030124070027. UIW26345. rwcrgwc56. attbi.com@turbodieselregister.com)
 
Deezul1 - here's a copy of the log entry where your email was sent to aol:



Jan 24 10:30:03 turbodieselregister sendmail[30742]: h0OATsR30740: to=(***your email address deleted***)@aol.com, ctladdr=nobody (65534/65534), delay=00:00:09, xdelay=00:00:04, mailer=esmtp, pri=30942, relay=mailin-04. mx. aol.com. [64. 12. 136. 153], dsn=2. 0. 0, stat=Sent (OK)



Looks like AOL is blocking it internally - check for spam blocker.
 
Thanks Steve

Now all I have to do is figure out how to "unblock it". Where do you start looking for that stuff.
 
Back
Top