yes youu have rigth
I telnet directly to the server i got my email:
..
top 1 20
+OK message is 2020 bytes
Return-Path: <[EMAIL PROTECTED]>
Delivered-To: [EMAIL PROTECTED]
Received: from dell (200.57.4.170)
by xcien.com with [XMail 1.9 (Linux/Ix86) ESMTP Server]
id <S3187FE> for <[EMAIL PROTECTED]> from <[EMAIL PROTECTED]>;
Tue, 17 Sep 2002 10:01:55 -0500
but my email Client Microsoft Outlook 2000 have the problem...
can you help me to find where putt the blank line:
2.) try to compose responses by the script with _only one_ blank line
after header fields. Less beautiful, but maybe ...
hope that helps ! Looking forward to your response
thank you!
-----Mensaje original-----
De: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]En
nombre de EDV - WHW (Goesta Smekal)
Enviado el: Monday, September 16, 2002 12:18 AM
Para: [EMAIL PROTECTED]
Asunto: [xmail] Re: antivir
On 13 Sep 2002 at 11:39, Juan Hector Medina wrote:
>
> Sure here is the info:
>
> Linux mail.xcien.com 2.4.2-2smp #1 SMP Sun Apr 8 20:21:34 EDT 2001 i686
> unknown
> [XMail 1.9 (Linux/Ix86) POP3 Server]
> This is perl, v5.6.0 built for i386-linux
> Clam Antivirus: The Scanner (ClamScan) 0.24
>
>
> I put the mailscan.pl in /var/MailRoot/bin/
>
> in the filters i put:
>
> "/var/MailRoot/bin/mailscan.pl" "@@FILE"
>
> thereis a TAB there...
>
> yes .... the non-infected messages are delivered correctly...
>
>
> In the virus log i get:
> Thu Sep 12 19:47:23 2002 ->Sircam<- From:[EMAIL PROTECTED]
> Host:192.168.135.156 on:Thu, 12 Sep 2002 19:56:08 -0700
To:[EMAIL PROTECTED]
>
> Thank youu very much!!!
>
> i will send you the email that block the INBOX from the server!
Dear Juan Hector,
the message you forwarded to me seems quite OK ... Your setup is
more recent than mine :-) and the results you mailed me look pretty
good.
Obviously ClamAV is working and mailscan.pl gets the results too.
Even the warning message is composed, so I wonder if my script can be
blamed ... the fault is allways with other people ;->
To be honest, I am very puzzled ! XMail doesn't seem to be guilty
either, because the message is put into your mailbox. So maybe your
client ? (Outlook Express v6 I assume)
What might be odd, are the three blank lines after the MIME header.
RFC 822 does not make the point clear wheather or not more than one
blank line is allowed delimiting header from body (nor does 2045,
AFAIK). Peagsus Mail has no problem with it. But since OE is quite
famous for blunders dealing with incorrect MIME headers, maybe they
'fixed' it with v6, now being too strict.
My advice:
1.) try to read the mail via telnet to port 110 of your mailserver.
(you do speak POP3, don't you ;-) An example could look like this:
(What I typed is prefixed with '>', responses with '<', IPs and
hostnames are x-ed out)
---SESSION COPY START---
> goe@fume:~$ telnet mail.xxx.xxx 110
< Trying xxx.xxx.xxx.xxx...
< Connected to mail.xxx.xxx.
< Escape character is '^]'.
< +OK <[EMAIL PROTECTED]> [XMail 1.9 (Linux/Ix86) POP3
Server] service ready; Mon, 16 Sep 2002 08:52:16 +0200
> user [EMAIL PROTECTED]
< +OK Password required for [EMAIL PROTECTED]
> pass ******
< +OK Maildrop has 5 messages (4339 bytes)
> list
< +OK 5 4339
< 1 880
< 2 877
< 3 876
< 4 865
< 5 841
< .
> top 1 10
(now come the first 10 lines of the message)
<.
>quit
<+OK [XMail 1.9 (Linux/Ix86) POP3 Server] closing session
<Connection closed by foreign host.
---SESSION COPY END---
If that works, your client has the problem !
2.) try to compose responses by the script with _only one_ blank line
after header fields. Less beautiful, but maybe ...
hope that helps ! Looking forward to your response
Goesta
P.S.: as stated by Eric S. Raymond in 'The Cathedral and the Bazaar':
"Given enough eyeballs, all bugs are shallow". So I attached the
blocking message, don't worry, no malicious code inside ;-)
--
Composed with Pegasus Mail v4.01 - the /dev/null for worms
take a look: http://www.pmail.com
-- Attached file included as plaintext by Ecartis --
-- Desc: Text from file 'base64'
Return-Path: <[EMAIL PROTECTED]>
Delivered-To: [EMAIL PROTECTED]
Received: from dell (192.168.135.156)
by xcien.com with [XMail 1.9 (Linux/Ix86) ESMTP Server]
id <S313172> for <[EMAIL PROTECTED]> from <[EMAIL PROTECTED]>;
Fri, 13 Sep 2002 11:23:48 -0500
From: "Juan Hector Medina" <[EMAIL PROTECTED]>
To: "Juan H. Medina" <[EMAIL PROTECTED]>
Subject: RV: cotiza2000
Date: Fri, 13 Sep 2002 11:32:28 -0700
Message-ID: <[EMAIL PROTECTED]>
MIME-Version: 1.0
Content-Type: multipart/mixed;
boundary="----=_NextPart_000_002E_01C25B19.3D6C4150"
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0)
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Importance: Normal
This is a multi-part message in MIME format.
------=_NextPart_000_002E_01C25B19.3D6C4150
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
-----Mensaje original-----
De: Liliana Uribe [mailto:[EMAIL PROTECTED]]
Enviado el: Saturday, January 05, 1980 11:46 PM
Para: [EMAIL PROTECTED]
Asunto: cotiza2000
Hi! How are you?
I send you this file in order to have your advice
See you later. Thanks
------=_NextPart_000_002E_01C25B19.3D6C4150
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: message text
Este mail es un aviso por que un mail que le fue enviado a usted contiene
un archivo adjunto, el cual esta infectado con:
"Sircam"
Este archivo adjunto fue removido por el servidor de correo.
Preguntas y comentarios por favor mandarnos la informacion contenida en
este correo a [EMAIL PROTECTED]
This message contained an appendix, which is infected with
"Sircam"
This appendix was removed by the Mailserver. Questions arrange
you please under indication of the information contained here on
mailto:[EMAIL PROTECTED]
------=_NextPart_000_002E_01C25B19.3D6C4150--
-
To unsubscribe from this list: send the line "unsubscribe xmail" in
the body of a message to [EMAIL PROTECTED]
For general help: send the line "help" in the body of a message to
[EMAIL PROTECTED]
-
To unsubscribe from this list: send the line "unsubscribe xmail" in
the body of a message to [EMAIL PROTECTED]
For general help: send the line "help" in the body of a message to
[EMAIL PROTECTED]
