I'm not clear on what your issue is.

Are you saying that OE goes into a loop and hangs when using the message
rule?

As for the TOP command, the POP3 server sends a period on a line by
itself to indicate that it has sent the whole response. This is the
same as the RETR command. It's up to the POP3 server to determine where
the header ends.

--

Mike - http://pages.prodigy.net/michael_santovec/techhelp.htm


"Capomaestro" wrote in message
...
Right. And someone does not read posts before touting freeware with
broken links
(http://service.schlund.de/service/download/magic29.zip). But that's
not the point.

The OE client IS searching the SUBJECT header for the string
'POTENTIAL-SPAM'. Here is what the client issues (POP3
commands) -

STAT
messages?
[yes - LIST]
[no - QUIT]
msgLoopLIST :
last message?
[yes - =msgLoopRETR]
TOP n 0 (n = message number)
(search stream for 0xOD0A0D0A to ensure all headers sent)
SUBJECT contains 'POTENTIAL-SPAM'?
[yes - issue DELE n command]
=msgLoopLIST
msgLoopRETR :
{blah, blah, blah}

The search for the final header loops because of the malformed EOM
(0x0D0A0A). This is a *normal* programming mechanism for
determining EOM in text-based messages.

Perhaps someone can suggest how to convince the spammers to upgrade
rather than asking M$ to fix the rules engine?


"Jim Pickering" wrote in message
...
You cannot do that with the limited rule set available for Outlook
Express.
I'd suggest a 3rd party program to do what you have in mind such as
Magic
mail monitor:

MagicMailMonitor
http://service.schlund.de/service/do...vice/magic.zip

You can set it up to always run at startup and use it to quickly
monitor and
delete messages. Outlook Express can only check for "text" in the
To, From,
Subject before downloading the message. To delete a message from the
server
based on some other line in the headers using a message rule will not
work.
Sorry.

As for users who are still running v. 6.00.2900.2180, is there some
reason
that they are not installing updates from Microsoft. Such a version
is
really out of date.
--
Jim Pickering, MVP, Windows Mail Apps
https://mvp.support.microsoft.com/pr...8-1171988A62D6
Please deliver feedback to the newsgroup, so that others can be
helped.







"Capomaestro" wrote in message
...
Here is the problem -

000002a0h: 31 38 30 0D 0A 58 2D 4D 69 6D 65 4F 4C 45 3A 20 ;
180..X-MimeOLE:
000002b0h: 50 72 6F 64 75 63 65 64 20 42 79 20 4D 69 63 72 ;
Produced By
Micr
000002c0h: 6F 73 6F 66 74 20 4D 69 6D 65 4F 4C 45 20 56 36 ; osoft
MimeOLE
V6
000002d0h: 2E 30 30 2E 32 39 30 30 2E 32 31 38 30 0D 0A 0A ;
.00.2900.2180...

...and

000002a0h: 2E 32 39 30 30 2E 32 31 38 30 0D 0A 58 2D 4D 69 ;
.2900.2180..X-Mi
000002b0h: 6D 65 4F 4C 45 3A 20 50 72 6F 64 75 63 65 64 20 ; meOLE:
Produced
000002c0h: 42 79 20 4D 69 63 72 6F 73 6F 66 74 20 4D 69 6D ; By
Microsoft
Mim
000002d0h: 65 4F 4C 45 20 56 36 2E 30 30 2E 32 39 30 30 2E ; eOLE
V6.00.2900.
000002e0h: 32 31 38 30 0D 0A 0A 54 68 69 73 20 69 73 20 61 ;
2180...This
is a

The mail rule is -

Where the Subject line contains 'POTENTIAL-SPAM'
and
Where the message is from the Some Network account
Delete it from server

But the rule engine loops searching for the required 0x0D0A0D0A

The problem appears with M$'s X-MimeOLE V6.00.2900.2180 headers.
Messages
produced with the X-MimeOLE V6.00.2900.2962 contain the
required CR (0x0D).

OE 6.00.2800.1807 client successfully downloads the defective
messages and
correctly applies a 'local' mail rule -

Apply this rule after the message arrives
Where the Subject line contains 'POTENTIAL-SPAM'
and
Where the message is from the Some Network account
Delete it

I want to continue avoiding the complete message download by having
OE
scan the headers and delete them directly from the POP3
server.