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.