This often is the results of recent visit to an off-brand web site that plants some malware while one is visiting. Think back of bowsing just before the bounce, etc problems were noticed. Run a a good malware detect and delete program for luck. Stay young , OldAck. On Thursday 04 May 2006 08:35, Jim Flanagan wrote:
Hi all,
I'm receiving bounce warnings from this list, as well as other Suse lists, and some from the Spamassassin list as well. Can someone tell me why this is happening? I'm getting maybe one or two a week. I saw a similar post a couple of weeks ago, but didn't see a solution, other than it seemed to be a configuration issue on the OPs side.
I'm running Suse 10, postfix, clamav, spamassassin, all basically default suse setup from DVD rpm's. I also have a backupmx set up at dyndns.org in case my server is temporarily down for reboot etc., which I believe is set up properly. My server has been up continually for over a month.
See below copy of one recent bounce message.
TIA for any pointers.
Jim Flanagan
---------------
Hi! This is the ezmlm program. I'm managing the suse-linux-e@suse.com mailing list.
I'm working for my owner, who can be reached at suse-linux-e-owner@suse.com.
Messages to you from the suse-linux-e mailing list seem to have been bouncing. I've attached a copy of the first bounce message I received.
If this message bounces too, I will send you a probe. If the probe bounces, I will remove your address from the suse-linux-e mailing list, without further notice.
I've kept a list of which messages from the suse-linux-e mailing list have bounced from your address.
Copies of these messages may be in the archive. To get message 12345 from the archive, send an empty message to:
Here are the message numbers:
267899 268109
--- Enclosed is a copy of the bounce message I received.
Return-Path: <> Received: (qmail 26361 invoked from network); 18 Apr 2006 23:27:54 -0000 Received: from unknown (HELO Relay2.suse.de) (195.135.221.8) by 0 with SMTP; 18 Apr 2006 23:27:54 -0000 Received: from Relay2.suse.de (localhost [127.0.0.1]) by Relay2.suse.de (Postfix) with ESMTP id 648687249C for
; Wed, 19 Apr 2006 01:27:54 +0200 (CEST) Received: from Relay2.suse.de ([127.0.0.1]) by Relay2.suse.de (Relay2 [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id 14779-01 for ; Wed, 19 Apr 2006 01:27:51 +0200 (CEST) Received: from mx2.suse.de (cantor2.suse.de [195.135.220.15]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by Relay2.suse.de (Postfix) with ESMTP id AD84E41BBB for ; Wed, 19 Apr 2006 01:27:51 +0200 (CEST) Received: from lists.suse.com (lists.suse.de [195.135.221.131]) by mx2.suse.de (Postfix) with SMTP id 941A21EBE1 for ; Wed, 19 Apr 2006 01:27:51 +0200 (CEST) Received: (qmail 26347 invoked for bounce); 18 Apr 2006 23:27:51 -0000 Date: 18 Apr 2006 23:27:51 -0000 From: MAILER-DAEMON@lists.suse.com To: suse-linux-e-return-267899-@suse.com Subject: failure notice Message-Id: <20060418232751.941A21EBE1@mx2.suse.de> X-Virus-Scanned: by amavisd-new at Relay2.suse.de X-Spam-Status: No, hits=0.1 tagged_above=-20.0 required=5.0 tests=BAYES_50, FORGED_RCVD_HELO, MY_LINUX, NO_REAL_NAME X-Spam-Level: Hi. This is the qmail-send program at lists.suse.com. I'm afraid I wasn't able to deliver your message to the following addresses. This is a permanent error; I've given up. Sorry it didn't work out.
: 24.238.237.18 failed after I sent the message. Remote host said: 550 Error: improper use of 8-bit data in message body -----------------