stantiam
05.04.2010, 12:22
Hallo,
ich habe ein mail abgeschickt an zwei mir bekannte (seriöse) Adressen.
(ich weiß nicht ob das wichtig ist: Das mail hatte 4 attaches (von mir eingescannte Formulare im jpg-Format) ).
Das mail kam als unzustellbar zurück, mit einer Vielzahl von email-Adressen, die vermutlich maschnell generiert wurden.
Meine Frage: Wo muss man die Ursache suchen? Ich habe mein System mit akt. Virenscanner gescannt, da wurde kein Virus gefunden.
Hier das zurückgekommene mail, die mailadressen und Serveradressen habe ich verändert:
X-Account-Key: account22
X-UIDL: [UID filtered]
X-Mozilla-Status: 0001
X-Mozilla-Status2: 00000000
X-Mozilla-Keys:
Return-Path: <>
Delivered-To: poor [at] spamvictim.tld
Received: (qmail 30662 invoked by UID: [UID filtered]
Received: from mailout1.myprovider.example (83.243.58.133)
by mail8.myprovider.example with SMTP; 2 Apr 2010 xx:xx:xx -0000
Received: (qmail 14481 invoked for bounce); 2 Apr 2010 xx:xx:xx -0000
Date: 2 Apr 2010 xx:xx:xx -0000
From: MAILER-DAEMON [at] mailout1.myprovider.example
To: poor [at] spamvictim.tld
Subject: failure notice
Hi. This is the qmail-send program at mailout1.myprovider.example.
I'm afraID: [ID filtered]
This is a permanent error; I've given up. Sorry it didn't work out.
<........ [at] aol.com>:
qmail-spawn unable to open message. (#4.3.0)
I'm not going to try again; this message has been in the queue too long.
<....... [at] cs.com>:
qmail-spawn unable to open message. (#4.3.0)
I'm not going to try again; this message has been in the queue too long.
<....... [at] verizon.net>:
qmail-spawn unable to open message. (#4.3.0)
I'm not going to try again; this message has been in the queue too long.
<........ [at] sbcglobal.net>:
qmail-spawn unable to open message. (#4.3.0)
I'm not going to try again; this message has been in the queue too long.
<........ [at] aol.com>:
qmail-spawn unable to open message. (#4.3.0)
I'm not going to try again; this message has been in the queue too long.
<....... [at] bellsouth.net>:
qmail-spawn unable to open message. (#4.3.0)
I'm not going to try again; this message has been in the queue too long.
......... lange Folge derartiger Meldung
<..... [at] ins-lua.com>:
qmail-spawn unable to open message. (#4.3.0)
I'm not going to try again; this message has been in the queue too long.
<..... [at] quincysurgical.com>:
qmail-spawn unable to open message. (#4.3.0)
I'm not going to try again; this message has been in the queue too long.
--- Below this line is a copy of the message.
Return-Path: <ich [at] example.com>
Received: (qmail 30841 invoked by UID: [UID filtered]
Received: from unknown (HELO ?192.168.2.32?) (ich [at] example.com@91.23.239.179)
by mailout1.myprovider.example with ESMTPA; 2 Apr 2010 xx:xx:xx -0000
X-Originator: 9f6d492b53574ec548a225ce17e6ecde
Message-ID: [ID filtered]
Date: Fri, 02 Apr 2010 xx:xx:xx +0200
From: "ich [at] example.com" <ich [at] example.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; de; rv:1.9.1.9) Gecko/20100317 Thunderbird/3.0.4
MIME-Version: 1.0
To: poor [at] spamvictim.tld
Subject: Re: ___
References: <4B9E128A.3020901 [at] gmx.de> <4B9E3A18.1040408 [at] example.com> <4BB46860.40505 [at] gmx.de>
In-Reply-To: <4BB46860.40505 [at] gmx.de>
Content-Type: multipart/mixed;
boundary="------------030900040006000502050804"
This is a multi-part message in MIME format.
--------------030900040006000502050804
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
Sehr geehrte Damen und Herren,
.... mein Text .......
--------------030900040006000502050804
Content-Type: image/jpeg;
name="Bild1.jpg"
Content-Transfer-Encoding: base64
Content-Disposition: attachment;
filename="Bild1.jpg"
.........
--------------030900040006000502050804--
ich habe ein mail abgeschickt an zwei mir bekannte (seriöse) Adressen.
(ich weiß nicht ob das wichtig ist: Das mail hatte 4 attaches (von mir eingescannte Formulare im jpg-Format) ).
Das mail kam als unzustellbar zurück, mit einer Vielzahl von email-Adressen, die vermutlich maschnell generiert wurden.
Meine Frage: Wo muss man die Ursache suchen? Ich habe mein System mit akt. Virenscanner gescannt, da wurde kein Virus gefunden.
Hier das zurückgekommene mail, die mailadressen und Serveradressen habe ich verändert:
X-Account-Key: account22
X-UIDL: [UID filtered]
X-Mozilla-Status: 0001
X-Mozilla-Status2: 00000000
X-Mozilla-Keys:
Return-Path: <>
Delivered-To: poor [at] spamvictim.tld
Received: (qmail 30662 invoked by UID: [UID filtered]
Received: from mailout1.myprovider.example (83.243.58.133)
by mail8.myprovider.example with SMTP; 2 Apr 2010 xx:xx:xx -0000
Received: (qmail 14481 invoked for bounce); 2 Apr 2010 xx:xx:xx -0000
Date: 2 Apr 2010 xx:xx:xx -0000
From: MAILER-DAEMON [at] mailout1.myprovider.example
To: poor [at] spamvictim.tld
Subject: failure notice
Hi. This is the qmail-send program at mailout1.myprovider.example.
I'm afraID: [ID filtered]
This is a permanent error; I've given up. Sorry it didn't work out.
<........ [at] aol.com>:
qmail-spawn unable to open message. (#4.3.0)
I'm not going to try again; this message has been in the queue too long.
<....... [at] cs.com>:
qmail-spawn unable to open message. (#4.3.0)
I'm not going to try again; this message has been in the queue too long.
<....... [at] verizon.net>:
qmail-spawn unable to open message. (#4.3.0)
I'm not going to try again; this message has been in the queue too long.
<........ [at] sbcglobal.net>:
qmail-spawn unable to open message. (#4.3.0)
I'm not going to try again; this message has been in the queue too long.
<........ [at] aol.com>:
qmail-spawn unable to open message. (#4.3.0)
I'm not going to try again; this message has been in the queue too long.
<....... [at] bellsouth.net>:
qmail-spawn unable to open message. (#4.3.0)
I'm not going to try again; this message has been in the queue too long.
......... lange Folge derartiger Meldung
<..... [at] ins-lua.com>:
qmail-spawn unable to open message. (#4.3.0)
I'm not going to try again; this message has been in the queue too long.
<..... [at] quincysurgical.com>:
qmail-spawn unable to open message. (#4.3.0)
I'm not going to try again; this message has been in the queue too long.
--- Below this line is a copy of the message.
Return-Path: <ich [at] example.com>
Received: (qmail 30841 invoked by UID: [UID filtered]
Received: from unknown (HELO ?192.168.2.32?) (ich [at] example.com@91.23.239.179)
by mailout1.myprovider.example with ESMTPA; 2 Apr 2010 xx:xx:xx -0000
X-Originator: 9f6d492b53574ec548a225ce17e6ecde
Message-ID: [ID filtered]
Date: Fri, 02 Apr 2010 xx:xx:xx +0200
From: "ich [at] example.com" <ich [at] example.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; de; rv:1.9.1.9) Gecko/20100317 Thunderbird/3.0.4
MIME-Version: 1.0
To: poor [at] spamvictim.tld
Subject: Re: ___
References: <4B9E128A.3020901 [at] gmx.de> <4B9E3A18.1040408 [at] example.com> <4BB46860.40505 [at] gmx.de>
In-Reply-To: <4BB46860.40505 [at] gmx.de>
Content-Type: multipart/mixed;
boundary="------------030900040006000502050804"
This is a multi-part message in MIME format.
--------------030900040006000502050804
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
Sehr geehrte Damen und Herren,
.... mein Text .......
--------------030900040006000502050804
Content-Type: image/jpeg;
name="Bild1.jpg"
Content-Transfer-Encoding: base64
Content-Disposition: attachment;
filename="Bild1.jpg"
.........
--------------030900040006000502050804--