Email notifications?

[JSellers]

Steve,



I use AT&T (previously Bellsouth) as my internet service provider. I remember seeing notices (TDR?) on a couple (or few) sites where problems exist with Bellsouth (along with other providers) and forum notifications via email. I may have experienced this recently with TDR, as I did not receive a requested response via email for login/password. (one of my computers was inadvertently logged out, and I had forgotten which password was needed to login... )



I think this problem has been ongoing, since I no longer receive any email notifications for responses to threads I join on TDR. I would like to fix this if possible.



Do you know of any approach I can use with my service provider to clear up issues with TDR notifications (and perhaps with other sites/forums)? I don't know technical background for these issues, but will go to bat with my provider to help this problem with my access (and maybe others in the same boat?).



Thanks,

John Sellers

 

[Steve St.Laurent]

Here is the info you'd need to contact your tech support department with. Here are log entries from a notification sent to you yesterday (with the email names in the address asterisked out):

Dec 8 05:20:39 turbodieselregister sm-mta[44005]: nB8AKdve044005: to=<*********@bellsouth.net>, delay=00:00:00, mailer=esmtp, pri=32117, stat=queued

Dec 8 05:20:39 turbodieselregister sendmail[44004]: nB8AKd9U044004: to=*********@bellsouth.net, ctladdr=webmaster (1010/80), delay=00:00:00, xdelay=00:00:00, mailer=relay, pri=31937, relay=[127. 0. 0. 1] [127. 0. 0. 1], dsn=2. 0. 0, stat=Sent (nB8AKdve044005 Message accepted for delivery)

Dec 8 07:45:05 turbodieselregister sm-mta[45059]: nB8AKdve044005: to=<*********@bellsouth.net>, ctladdr=<webmaster@turbodieselregister.com> (1010/80), delay=02:24:26, xdelay=00:00:00, mailer=esmtp, pri=122117, relay=gateway-f1. isp. att.net. , dsn=5. 0. 0, stat=Service unavailable

and here is the message header from one of my notifications so that can see how the message comes through:

X-Envelope-From: webmaster@turbodieselregister.com
Return-Path: <webmaster@turbodieselregister.com>
Received: from turbodieselregister.com (turbodieselregister.com [66. 154. 81. 110])
by mail990c35. nsolutionszone.com (8. 13. 6/8. 13. 1) with ESMTP id nB9HQQEf012767
for <*******@centurytel.net>; Wed, 9 Dec 2009 12:26:28 -0500
Received: from turbodieselregister.com (localhost [127. 0. 0. 1])
by turbodieselregister.com (8. 13. 6/8. 13. 6) with ESMTP id nB9HPM0o037555
for <*******@centurytel.net>; Wed, 9 Dec 2009 12:25:22 -0500 (EST)
(envelope-from webmaster@turbodieselregister.com)
Received: (from webmaster@localhost)
by turbodieselregister.com (8. 13. 6/8. 13. 6/Submit) id nB9HPM7Y037554;
Wed, 9 Dec 2009 12:25:22 -0500 (EST)
(envelope-from webmaster)
Date: Wed, 9 Dec 2009 12:25:22 -0500 (EST)
To: *******@centurytel.net
Subject: New Private Message at TDR Roundtable
From: "TDR Roundtable" <rpatton@ix.netcom.com>
Auto-Submitted: auto-generated
Message-ID: <20091209172522. 5c884eb805cf@www.turbodieselregister.com>
MIME-Version: 1. 0
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 8bit
X-Priority: 3
X-Mailer: vBulletin Mail via PHP
X-MMR: 0

 

[JSellers]

Thanks, Steve - I'll see what response I get with this information.



Best,

John

 

[rbattelle]

Funny you should mention this because all of a sudden I'm not getting any email notifications from TDR. One day it worked, then suddenly it stopped.

Ryan