Yahoo Groups archive

Cgs synth

Index last updated: 2026-04-28 23:16 UTC

Message

e-mail problem? (reaching Ken direct, kind of OT)

2008-01-11 by Larry T.

Hi Ken

I just tried to send you a question and an order. Please check the
message below and if there is a problem either let me know, or check
with your ISP. You can reach me at ltroth at socal.rr.com. Looking
forward to talking with you.

Larry

Your mail bounced with the following message:
----------------------------------------------

This Message was undeliverable due to the following reason:

Each of the following recipients was rejected by a remote mail server.
The reasons given by the server are included to help you determine why
each recipient was rejected.

Recipient: <sasami@...>
Reason: 5.7.1 Service unavailable; Client host [71.74.56.122]
blocked using zen.spamhaus.org;
http://www.spamhaus.org/query/bl?ip=71.74.56.122

Please reply to <Postmaster@...>
if you feel this message to be in error.
Reporting-MTA: dns; hrndva-omta04.mail.rr.com
Arrival-Date: Fri, 11 Jan 2008 20:05:26 +0000
Received-From-MTA: dns; lrt-linwin.socal.rr.com (72.134.35.122)

Final-Recipient: RFC822; <sasami@...>
Action: failed
Status: 5.2.0
Remote-MTA: dns; vscan4.hotkey.net.au (202.138.0.38)
Diagnostic-Code: smtp; 554 5.7.1 Service unavailable; Client host
[71.74.56.122] blocked using zen.spamhaus.org;
http://www.spamhaus.org/query/bl?ip=71.74.56.122
Received: from lrt-linwin.socal.rr.com ([72.134.35.122])
by hrndva-omta04.mail.rr.com with ESMTP
id
<20080111200526.QMPE17975.hrndva-omta04.mail.rr.com@...>
for <sasami@...>; Fri, 11 Jan 2008 20:05:26 +0000
Message-Id: <5.1.0.14.2.20080111115820.0284ed50@...>
X-Sender: ltroth@...
X-Mailer: QUALCOMM Windows Eudora Version 5.1
Date: Fri, 11 Jan 2008 12:04:59 -0800
To: sasami@...
From: Larry Troth <ltroth@...>
Subject: Question and Board Order
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed

Attachments

Move to quarantaine

This moves the raw source file on disk only. The archive index is not changed automatically, so you still need to run a manual refresh afterward.