eu vad ca esti in dsbl, spamcom, etc :)
(spamassassin-ul nostru a catalogat mail-ul tau de pe rlug ca fiind spam )
X-Spam-Status: Yes, hits=5.8 required=5.0 tests=MAILTO_TO_SPAM_ADDR,
RCVD_IN_BL_SPAMCOP_NET,RCVD_IN_DSBL,RCVD_IN_NJABL,RCVD_IN_NJABL_RELAY
autolearn=no version=2.63
X-Spam-Report:
* 1.1 MAILTO_TO_SPAM_ADDR URI: Includes a link to a likely spammer
email
* 1.1 RCVD_IN_DSBL RBL: Received via a relay in list.dsbl.org
* [<http://dsbl.org/listing?ip=62.231.108.46>]
* 2.2 RCVD_IN_BL_SPAMCOP_NET RBL: Received via a relay in
bl.spamcop.net
* [Blocked - see <http://www.spamcop.net/bl.shtml?62.231.108.46>]
* 1.3 RCVD_IN_NJABL_RELAY RBL: NJABL: sender is confirmed open relay
* [62.231.108.46 listed in dnsbl.njabl.org]
* 0.1 RCVD_IN_NJABL RBL: Received via a relay in dnsbl.njabl.org
* [62.231.108.46 listed in dnsbl.njabl.org]
On Friday 26 March 2004 14:08, Radu Dragomir wrote:
> On Friday 26 March 2004 08:36, Mihai RUSU wrote:
> > On Fri, 26 Mar 2004, Radu Dragomir wrote:
> > > datele problemei:
> > >
> > > Un qmail normal fara v-pop se comporta foarte ciudat
> > > 1. trimite mailuri aiurea (SPAM) - si nu .. nu e open relay
> >
> > Detaliaza despre ce mailuri aiurea e vorba (cu exemple clare de headere
> > si de ce zici tu ca sunt aiurea).
>
> deci tinind cont ca inca nu am gasit o rezolvare ...
>
> aici ar fi mesaju' :
>
> Return-Path: <[EMAIL PROTECTED]>
> Delivered-To: [EMAIL PROTECTED]
> Received: (qmail 5852 invoked by alias); 26 Mar 2004 09:32:58 -0000
> Delivered-To: [EMAIL PROTECTED]
> Received: (qmail 5850 invoked for bounce); 26 Mar 2004 09:32:58 -0000
> Date: 26 Mar 2004 09:32:58 -0000
> From: [EMAIL PROTECTED]
> To: [EMAIL PROTECTED]
> Subject: failure notice
> Status: R
> X-Status: N
> X-KMail-EncryptionState:
> X-KMail-SignatureState:
>
>
> Hi. This is the qmail-send program at marka.ro.
> I tried to deliver a bounce message to this address, but the bounce
> bounced!
>
> <[EMAIL PROTECTED]>:
> 68.1.17.3 does not like recipient.
> Remote host said: 550 Invalid recipient: <[EMAIL PROTECTED]>
> Giving up on 68.1.17.3.
>
> --- Below this line is the original bounce.
>
> Return-Path: <>
> Received: (qmail 5848 invoked for bounce); 26 Mar 2004 09:32:56 -0000
> Date: 26 Mar 2004 09:32:56 -0000
> From: [EMAIL PROTECTED]
> To: [EMAIL PROTECTED]
> Subject: failure notice
>
> Hi. This is the qmail-send program at marka.ro.
> 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.
>
> <[EMAIL PROTECTED]>:
> 205.188.159.57 failed after I sent the message.
> Remote host said: 554-: (HVU:B1) The URL contained in your email to AOL
> members has generated a high volume of complaints. Per our Unsolicited
> BuF!8mailID=2774064000e142
> 554 TRANSACTION FAILED
>
> --- Below this line is a copy of the message.
>
> Return-Path: <[EMAIL PROTECTED]>
> Received: (qmail 5687 invoked from network); 26 Mar 2004 09:31:55 -0000
> Received: from [EMAIL PROTECTED] by ns1 by uid 1001 with
> qmail-scanner-1.20
> (clamuko: 0.60. hbedv: 6.22.0.1/6.22.0.54. vexira: 6.20.0.0. spamassassin:
> 2.55. Clear:RC:0(61.149.219.59):SA:1(3.8/2.0):.
> Processed in 2.168779 secs); 26 Mar 2004 09:31:55 -0000
> X-Spam-Status: Yes, hits=3.8 required=2.0
> Received: from unknown (HELO activating) ([EMAIL PROTECTED])
> by with SMTP; 26 Mar 2004 09:31:52 -0000
> From: "Irene LeVine"<[EMAIL PROTECTED]>
> To: [EMAIL PROTECTED]
> Subject: B|uying C`IAL1S & L`EVITRA 0nline has never been easier and can
> now be shipped wOrldw1de!
> Mime-Version: 1.0
> Content-Type: text/html; charset=us-ascii
> Content-Transfer-Encoding: 7bit
> X-Qmail-Scanner-Message-ID: <[EMAIL PROTECTED]>
>
> > > 2. desi am inchis tot (SMTP/POP3 ... tot) coada continua sa se umpe
> > > intr-o veselie (aprox 100 mailuri pe minut) astfel incit la repornire
> > > ... imi pleaca mail-uri
> >
> > Coada se poate umple din 2 motive doar:
> > 1. SMTP
> > 2. local cu /var/qmail/bin/sendmail sau qmail-inject (sau de fapt
> > qmail-queue care e apelat de astea doua)
> >
> > Deci daca pe SMTP nu vin mesaje inseamna ca sunt injectate local. In
> > aceasta situatie poti vedea in headerele unui asemenea mesaj injectat
> > local ce UID avea procesul care a injectat mesajul si deci sa te ajute sa
> > track down cauza.
> >
> > > 3. serverul fizic pe care sta acest q-mail nu pare a fi rootkit-at sau
> > > macar spart (pe veriificate)
> >
> > Vezi mai sus.
>
> ---
> Detalii despre listele noastre de mail: http://www.lug.ro/
---
Detalii despre listele noastre de mail: http://www.lug.ro/
