If I try to remove the 'message/partial' from the action2 tab, FW-1 will
tell me, that it is recommended to strip MIME of type 'message/partial' when
using CVP server. Do you want to add 'message/partial'. Is there any
malfunction in CVP-scanning, if I don�t add the MIME of type
'message/partial' ?

-----Urspr�ngliche Nachricht-----
Von: rich [mailto:[EMAIL PROTECTED]]
Gesendet am: Sonntag, 19. August 2001 17:41
An: Ament, Andreas; [EMAIL PROTECTED]
Betreff: Re: [FW1] Mime attachment stripped

We have just had exactly the same problem. If you go into the properties for
the SMTP resource->action2 tab and remove the 'message/partial' from this
section (fw-1 will check to see if you're sure) then it should work. Also
make sure you have the latest VirusScan  patches.

Rich
----- Original Message -----
From: <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Friday, August 17, 2001 1:46 PM
Subject: [FW1] Mime attachment stripped



Hi to all,

I use FW1-SP2 and TrendMicro�s Interscan for CVP-inspection of mail. In the
SMTP-Ressource I have to define that FW stripps message/partial MIME types,
because CVP cannot handle this type. Now I have mails, whoose attachments
are stripped.

the log viewer shows the following entries:
invalid encoding
forbidden mime attachment stripped

I tried "set: smtp_encoded_content_fields (true)" in objects.C

Is the only solution to install a SMTP relay, which provides the Virus
scanning ?

Thanks for any help

Andreas Ament


============================================================================
====
     To unsubscribe from this mailing list, please see the instructions at
               http://www.checkpoint.com/services/mailing.html
============================================================================
====




================================================================================
     To unsubscribe from this mailing list, please see the instructions at
               http://www.checkpoint.com/services/mailing.html
================================================================================

Reply via email to