From: "Diego Olivier Fernandez Pons" <FernandezPons@iFrance.com>
To: "Caml" <caml-list@inria.fr>
Subject: [Caml-list] filtering attached document
Date: Tue, 27 Nov 2001 00:29:40 +0100 [thread overview]
Message-ID: <01cc01c176d3$0e6a2960$0d29e8d4@Utilisateur> (raw)
Christophe Raffalli a écrit :
< Should not we filter the list to accept only text as attached
< documents ? It is probably easy to implement with the program that
< is used for that list ?
Voici ce que j'ai reçu de la part de mon fournisseur d'accès :
The email you've received from owner-caml-list@pauillac.inria.fr on
FernandezPons@iFrance.com the 11/22/2001 11:48:22 was infected by
TROJ_ALIZ.A in the file whatever.exe (action : file deleted) /
Le message électronique que vous avez reçu de
owner-caml-list@pauillac.inria.fr sur FernandezPons@iFrance.com le
11/22/2001 11:48:22 contenait le virus TROJ_ALIZ.A dans le fichier
whatever.exe (action: fichier deleted) / El mensaje electronico que
has recibido de owner-caml-list@pauillac.inria.fr a
FernandezPons@iFrance.com el 11/22/2001 11:48:22 contenia el virus
TROJ_ALIZ.A en el fichero whatever.exe (acción : fichero deleted).
Et dans les messages concernés, le fichier whatever.exe avait été
éliminé, avec un message de rappel ajouté en prologue.
J'ignore si une politique semblable peut être mise en place par la
liste, mais elle serait plus flexible que de n'accepter que des
fichiers texte.
I do not know if the caml-list could do the same, but it would be less
restrictive than accepting only text files as attached documents.
Diego Olivier
-------------------
Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/
To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr
reply other threads:[~2001-11-26 23:37 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='01cc01c176d3$0e6a2960$0d29e8d4@Utilisateur' \
--to=fernandezpons@ifrance.com \
--cc=caml-list@inria.fr \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).