On Mon, 05 Nov 2001 18:37:46 -0400, PMMail OS/2 Support wrote:
>On Mon, 05 Nov 2001 17:17:26 -0500 (EST), Bruce Francis wrote:
>>This sounds like the Javascript bug that has been around for a while....
>>I'm not using the most current releases, but I thought Trevor said that
>>this bug had been fixed. Trevor?
>It's been so long I don't remember exactly what the problem was
>anymore.
sigh (double sigh) ....
....isn't that a sign that we ought to be getting more updates??
How about this message from over a YEAR ago? I think you wrote it.
....???
(I would LIKE to see this one fixed, REALLY fixed, Peter, as your
(Trevor's) filter involves checking almost every message's _body_ for
specific content, and this takes a LOT of CPU time.... sadly)....
Is Peter around, yet, BTW???
==============================================
On Mon, 30 Oct 2000 11:31:21 -0400, PMMail OS/2 Support wrote:
>On Mon, 30 Oct 2000 06:29:07 -0500 (EST), Gregory L. Marx wrote:
>
>>I'll get a piece of email - usually spam ... When I open it PMMail immediately dies and closes up ...
or so it seems ...
>>But if I do the old "CTL-click on the open task button on the WarpCenter" PMMail shows up as
still running ... and most importantly I can't kill it
>>but the normal conventional means ...
>
>These are the "Killer HTML Spams" that have been around for a few
>months now. We are working on a fix and hope to have it available
>soon.
>
>Until we can release a fix for PMMail to stop this crashing, I have
>written a filter which will identify these "Killer HTML Spams" and
>permanently delete them before you have a chance to even accidentally
>click on them. If you prefer not to trust my filter to know which
>messages are really spam, you can modify the filter to only move them
>to a special folder instead of deleting them.
>
>Here are the filter details:
>
>Enter PMMail/2's filter setup and create a new filter (select
>"Account->Filters...", and click "New") with the following settings.
>You'll want to make this the first filter in your list if you have
>other active filters.
>
>1. Enabled (checked)
>2. Complex (checked) with these settings:
>
>!(Header.Toid="pmmailos2@blueprintsoftwareworks.com" |
>Header.Cc="pmmailos2@blueprintsoftwareworks.com")
>&
>(Header.Content-Type="html")
>&
>(Body="LANGUAGE="JavaScript">IpVecIpV=")
>
>3. Incoming (checked)
>4. Actions:
> a) Set status "Read"
> b) Move message "Trash"
> c) Delete message "Local copy"
> d) Inform user
>
>This filter assumes you do not have "true deletes" checked in your
>account settings' "Preferences" page. If you do have "true deletes"
>checked, you should be able to eliminate step 4b.
>
>This filter assumes you do not have "leave all messages on server"
>checked in your account settings' "Receive" page. If you do have
>"leave all messages on server" checked, you should change step 4c to:
>
>4. Actions:
> c) Delete message "Remote and local copy (incoming only)"
>
>This filter checks 3 things:
>
>1) if the incoming email is *not* addressed to you in the To: or Cc:
>fields;
>
>2) if the string "html" appears in the "Content-type" header line;
>and
>
>3) if the incoming email has a specific string in its body
>('LANGUAGE="JavaScript">IpVecIpV=') which seems to appear in all the
>killer HTML messages.
>
>If these three conditions are met, the message will be marked as read
>and permanently deleted. Also, the filter lets you know that a
>message has been found and removed.
>
>If you are extremely paranoid and worry that this filter might
>accidentally delete a useful message, you can eliminate action 4c
>(Delete message "Local copy"). You will then be able to look over the
>messages in the trash folder to see if they really need to be
>deleted.
>
>CAUTION: THIS DEFEATS THE PURPOSE OF THIS FILTER. The purpose of this
>filter is to remove the offending emails *BEFORE* you have a chance
>to view them, either from the preview pane or by double-clicking.
>
>Some notes:
>
>1. This filter moves and deletes messages it identifies as "killer
>HTML". Once a message has been moved or deleted by a filter in
>PMMail, no other filters are applied to that message.
>
>2. If someone were to send you a "killer HTML" message addressed
>specifically to you in the To: or Cc: fields, this filter would not
>delete it. This means someone could still purposefully crash your
>copy of PMMail if they wanted to. Remove the first two lines of the
>filter:
>
>!(Header.Toid="pmmailos2@blueprintsoftwareworks.com" |
>Header.Cc="pmmailos2@blueprintsoftwareworks.com")
>&
>
>and this filter will delete *all* messages which appear to be "killer
>HTML" messages, regardless of who they're addressed to.
>
>3. I am not 100% sure that the search string I'm using appears in all
>"killer HTML" messages. So far it has been in all the ones I've
>checked, but that's not necessarily a guarantee it will be in all of
>them.
>
>Whenever you find a message that crashes PMMail when you attempt to
>view it (either from the preview pane or by opening the message),
>send it to me as an attachment (turn off your preview pane, then drag
>the message -- without opening it -- from the message list to the
>attachment area of an outgoing message and send it to me) at:
>
>pmmailos2@blueprintsoftwareworks.com
>
>Please let me know either in the subject or body of the message that
>the attachment is a "Killer HTML" email.
>
>
>Again, this is an interim solution until we can fix the bug in PMMail
>which causes this crash.
>
>
>
>--
>Trevor Smith
>PMMail/2 Technical Support
>pmmailos2@blueprintsoftwareworks.com
>
>
>- pmmail-list - The PMMail discussion list ---------------------------
>To POST to the list, send your message to
>pmmail-list@blueprintsoftwareworks.com
>
>To unsubscribe, send a message to mdaemon@bmtmicro.com with the first
>line of the message body being...
>
>UNSUBSCRIBE pmmail-list@blueprintsoftwareworks.com
>---------------------------------------------------------------------
- pmmail-list - The PMMail Dicussion List ---------------------------
To POST to the list, send your message to:
pmmail-list@blueprintsoftwareworks.com
To UNSUBSCRIBE, send a message to mdaemon@bmtmicro.com with the first
line of the message body being...
UNSUBSCRIBE pmmail-list@blueprintsoftwareworks.com
---------------------------------------------------------------------