[Linux-sunucu] Server 'daki Bir Mailin Yahoo Groups Sorunu?

---------

New Message Reply About this list Date view Thread view Subject view Author view Attachment view

From: Murat (muex) (muex@muex.info)
Date: Wed 19 Oct 2005 - 14:34:37 EEST


Selam arkadaslar, server 'imda bir bir mail adresi var. Yahoo ve
yahoogroup lardan mail alamiyor. Bunun hakkında ne cozum uretirsiniz.
Asağida bana gonderdiği bir kac maili yaziyorum.. Tesekkurler (sanirim
bounce lanmiş. Ama nasil cozebilirim)

---------------------------

-----Original Message-----
From: Content-filter at no [mailto:postmaster@no.spam.ee]
Sent: Tuesday, October 18, 2005 10:24 AM
To: aydin.ozkaya@karina.gen.tr <mailto:aydin.ozkaya@karina.gen.tr>
Subject: BANNED (P=p003,L=1,M=multipart/mixed |
P=p002,L=1/2,M=application/octet-stream,T=zip,N=message.zip |
P=p004,L=1/2/1,T=exe,T=exe-ms,N=message.htm .pif) IN MAIL FROM YOU

BANNED CONTENTS ALERT

Our content checker found
banned name: P=p003,L=1,M=multipart/mixed |
P=p002,L=1/2,M=application/octet-stream,T=zip,N=message.zip |
P=p004,L=1/2/1,T=exe,T=exe-ms,N=message.htm
.pif
in email presumably from you (<aydin.ozkaya@karina.gen.tr>),
to the following recipient:
-> tonu@spam.ee <mailto:tonu@spam.ee>

Our internal reference code for your message is 25357-03.

Delivery of the email was stopped!

The message has been blocked because it contains a component
(as a MIME part or nested within) with declared name
or MIME type or contents type violating our access policy.

To transfer contents that may be considered risky or unwanted
by site policies, or simply too large for mailing, please consider
publishing your content on the web, and only sending an URL of the
document to the recipient.

Depending on the recipient and sender site policies, with a little
effort it might still be possible to send any contents (including
viruses) using one of the following methods:

- encrypted using pgp, gpg or other encryption methods;

- wrapped in a password-protected or scrambled container or archive
(e.g.: zip -e, arj -g, arc g, rar -p, or other methods)

Note that if the contents is not intended to be secret, the
encryption key or password may be included in the same message
for recipient's convenience.

We are sorry for inconvenience if the contents was not malicious.

The purpose of these restrictions is to cut the most common propagation
methods used by viruses and other malware. These often exploit automatic
mechanisms and security holes in certain mail readers (Microsoft mail
readers and browsers are a common and easy target). By requiring an
explicit and decisive action from the recipient to decode mail,
the dangers of automatic malware propagation is largely reduced.

For your reference, here are headers from your email:
------------------------- BEGIN HEADERS -----------------------------
Return-Path: <aydin.ozkaya@karina.gen.tr>
Received: from karina.gen.tr (unknown [85.98.109.130])
by no.spam.ee (Postfix) with ESMTP id 2B3466438E
for <tonu@spam.ee>; Tue, 18 Oct 2005 10:23:36 +0300 (EEST)
From: aydin.ozkaya@karina.gen.tr <mailto:aydin.ozkaya@karina.gen.tr>
To: tonu@spam.ee <mailto:tonu@spam.ee>
Subject: Test
Date: Tue, 18 Oct 2005 10:54:44 +0300
MIME-Version: 1.0
Content-Type: multipart/mixed;
boundary="----=_NextPart_000_0002_8B7F6886.4910AC2F"
X-Priority: 3
X-MSMail-Priority: Normal
Message-Id: <20051018072336.2B3466438E@no.spam.ee>
-------------------------- END HEADERS ------------------------
_______________________________________________
Linux-sunucu mailing list
Linux-sunucu@liste.linux.org.tr
http://liste.linux.org.tr/mailman/listinfo/linux-sunucu


New Message Reply About this list Date view Thread view Subject view Author view Attachment view

---------

Bu arsiv hypermail 2.1.2 tarafindan uretilmistir.