Full Version: Bounces from spam@uce.gov
I've had a bunch of bounced messages this afternoon. They were CC: reports to spam@uce.gov. Anyone else have the problem?
Welcome back Tim! 
I also have this in my CC list, and have had no problems. Is it spelled correctly in your CC list?
I also have this in my CC list, and have had no problems. Is it spelled correctly in your CC list?
I just got a ton of these messages also:
They've been in my CC list for a few weeks, so...not sure what's going on!
- JRB
QUOTE
**********************************************
** THIS IS A WARNING MESSAGE ONLY **
** YOU DO NOT NEED TO RESEND YOUR MESSAGE **
**********************************************
The original message was received at Mon, 21 Feb 2005 17:25:42 -0500
from adsl-68-124-120-44.dsl.lsan03.pacbell.net [68.124.120.44]
----- The following addresses had transient non-fatal errors -----
<spam@uce.gov>
----- Transcript of session follows -----
451 uce.gov: Name server timeout
Warning: message still undelivered after 4 hours
Will keep trying until message is 5 days old
Reporting-MTA: dns; tempevideo.com
Arrival-Date: Mon, 21 Feb 2005 17:25:42 -0500
Final-Recipient: RFC822; spam@uce.gov
Action: delayed
Status: 4.4.3
Last-Attempt-Date: Tue, 22 Feb 2005 01:04:36 -0500
Will-Retry-Until: Sat, 26 Feb 2005 17:25:42 -0500
** THIS IS A WARNING MESSAGE ONLY **
** YOU DO NOT NEED TO RESEND YOUR MESSAGE **
**********************************************
The original message was received at Mon, 21 Feb 2005 17:25:42 -0500
from adsl-68-124-120-44.dsl.lsan03.pacbell.net [68.124.120.44]
----- The following addresses had transient non-fatal errors -----
<spam@uce.gov>
----- Transcript of session follows -----
451 uce.gov: Name server timeout
Warning: message still undelivered after 4 hours
Will keep trying until message is 5 days old
Reporting-MTA: dns; tempevideo.com
Arrival-Date: Mon, 21 Feb 2005 17:25:42 -0500
Final-Recipient: RFC822; spam@uce.gov
Action: delayed
Status: 4.4.3
Last-Attempt-Date: Tue, 22 Feb 2005 01:04:36 -0500
Will-Retry-Until: Sat, 26 Feb 2005 17:25:42 -0500
They've been in my CC list for a few weeks, so...not sure what's going on!
- JRB
QUOTE
uce.gov: Name server timeout
Warning: message still undelivered after 4 hours
Warning: message still undelivered after 4 hours
Could just be their servers were down for maintenance or whatever and your mail hit that window. That mail was just an advisory that it hadn't been delivered after 4 hours. If you don't get a Delivery failure report then it will have gone through.
I just got a bunch of these also... 
QUOTE
spam@uce.gov
It's in my cc list also, but have had no bounces (so far
). But then, My spam levels have fallen so low, that I only have somthing to report every few days. 
Yes,
I just got about 75 of these:
I'd rather have them than spam - can delete all in a batch.
I just got about 75 of these:
QUOTE
Arrival-Date: Mon, 21 Feb 2005 20:14:53 -0700
Final-Recipient: RFC822; caspam@doj.ca.gov
Action: delayed
Status: 4.4.1
Remote-MTA: DNS; imail.doj.ca.gov
Last-Attempt-Date: Tue, 22 Feb 2005 01:11:18 -0700
Will-Retry-Until: Sat, 26 Feb 2005 20:14:53 -0700
Final-Recipient: RFC822; spam@uce.gov
Action: delayed
Status: 4.4.3
Last-Attempt-Date: Tue, 22 Feb 2005 01:11:18 -0700
Will-Retry-Until: Sat, 26 Feb 2005 20:14:53 -0700
Final-Recipient: RFC822; uce@ftc.gov
Action: delayed
Status: 4.4.3
Last-Attempt-Date: Tue, 22 Feb 2005 01:11:18 -0700
Will-Retry-Until: Sat, 26 Feb 2005 20:14:53 -0700
Final-Recipient: RFC822; caspam@doj.ca.gov
Action: delayed
Status: 4.4.1
Remote-MTA: DNS; imail.doj.ca.gov
Last-Attempt-Date: Tue, 22 Feb 2005 01:11:18 -0700
Will-Retry-Until: Sat, 26 Feb 2005 20:14:53 -0700
Final-Recipient: RFC822; spam@uce.gov
Action: delayed
Status: 4.4.3
Last-Attempt-Date: Tue, 22 Feb 2005 01:11:18 -0700
Will-Retry-Until: Sat, 26 Feb 2005 20:14:53 -0700
Final-Recipient: RFC822; uce@ftc.gov
Action: delayed
Status: 4.4.3
Last-Attempt-Date: Tue, 22 Feb 2005 01:11:18 -0700
Will-Retry-Until: Sat, 26 Feb 2005 20:14:53 -0700
I'd rather have them than spam - can delete all in a batch.
This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please click here.