You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomcat.apache.org by hg...@slib.fr on 2005/04/13 20:26:22 UTC
Error
During a routine email scan at UTC, a file attached to this
message was deleted per UTC Security Policy. UTC does not allow
emailing several file types due to their potential to transmit viruses.
An attachment named sjufp.scr was removed from this message.
The body text of the message that included the deleted attachment can be found
in the .txt file below. It is safe to open this file. If you believe this
message is not business related simply delete it. If the message is business
related and you require the file that was deleted, please contact the sender/nand arrange an alternate means of receiving it. The recommended method is to/nhave the sender zip the file before sending it.
Re: OT: Re: Error
Posted by Henri Gomez <he...@gmail.com>.
Well I didn't use this email for at least 3 years but it seems many
viri robots still use it.
On 4/13/05, William A. Rowe, Jr. <wr...@rowe-clan.net> wrote:
> Wow, social engineering on a whole new level.
>
> An enigma wrapped in a puzzle, wrapped in a riddle.
>
> At 01:26 PM 4/13/2005, hgomez@slib.fr wrote:
> >Content-Type: text/plain; name="warning1.txt"
> >Content-Disposition: inline; filename="warning1.txt"
> >Content-Transfer-Encoding: 7bit
> >MIME-Version: 1.0
> >X-Mailer: MIME-tools 5.411 (Entity 5.404)
> >
> >During a routine email scan at UTC, a file attached to this
> >message was deleted per UTC Security Policy. UTC does not allow
> >emailing several file types due to their potential to transmit viruses.
> >
> >An attachment named sjufp.scr was removed from this message.
> >The body text of the message that included the deleted attachment can be found
> >in the .txt file below. It is safe to open this file. If you believe this
> >message is not business related simply delete it. If the message is business
> >related and you require the file that was deleted, please contact the sender/nand arrange an alternate means of receiving it. The recommended method is to/nhave the sender zip the file before sending it.
> >
> >
> >The message cannot be represented in 7-bit ASCII encoding and has been sent as a binary attachment.
> >
> >
> >
> >---------------------------------------------------------------------
> >To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
> >For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org
OT: Re: Error
Posted by "William A. Rowe, Jr." <wr...@rowe-clan.net>.
Wow, social engineering on a whole new level.
An enigma wrapped in a puzzle, wrapped in a riddle.
At 01:26 PM 4/13/2005, hgomez@slib.fr wrote:
>Content-Type: text/plain; name="warning1.txt"
>Content-Disposition: inline; filename="warning1.txt"
>Content-Transfer-Encoding: 7bit
>MIME-Version: 1.0
>X-Mailer: MIME-tools 5.411 (Entity 5.404)
>
>During a routine email scan at UTC, a file attached to this
>message was deleted per UTC Security Policy. UTC does not allow
>emailing several file types due to their potential to transmit viruses.
>
>An attachment named sjufp.scr was removed from this message.
>The body text of the message that included the deleted attachment can be found
>in the .txt file below. It is safe to open this file. If you believe this
>message is not business related simply delete it. If the message is business
>related and you require the file that was deleted, please contact the sender/nand arrange an alternate means of receiving it. The recommended method is to/nhave the sender zip the file before sending it.
>
>
>The message cannot be represented in 7-bit ASCII encoding and has been sent as a binary attachment.
>
>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
>For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org