Are you using any anti-virus set to scan e-mail or a anti-spam program
or POP3 proxy that sits between OE and the POP3 server that might be
causing problems?

Are you seeing the MSIMN.EXE in the task manager go to near 100% CPU
utilization when this happens.

If you change the message rule action to something other than Delete
from Server (or Do not download), such as move to another folder, does
the same problem occur?

--

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


"Capomaestro" wrote in message
...
Correct. The POP3 server sends the headers and then the OE rules
engine loops when it encounters the defective empty header when it
is directed to 'Delete it from server'.

"Michael Santovec" wrote in message
...
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.

Was this a question or a statement? -
Are you seeing the MSIMN.EXE in the task manager go to near 100% CPU utilization when this happens.

No. OE6 is a 'well-behaved' Windoze application, relinquishing the CPU to the Windoze message loop periodically.

You too (RTFP)?
If you change the message rule action to something other than Delete from Server (or Do not download), such as move to another
folder, does the same problem occur?
__________________________________________________ _____________
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

__________________________________________________ _____________

Face it, OE6's rules engine is broken. There is no NG fix for this other than an MVP sending in a defect report.

"Michael Santovec" wrote in message ...
Are you using any anti-virus set to scan e-mail or a anti-spam program
or POP3 proxy that sits between OE and the POP3 server that might be
causing problems?

Are you seeing the MSIMN.EXE in the task manager go to near 100% CPU
utilization when this happens.

If you change the message rule action to something other than Delete
from Server (or Do not download), such as move to another folder, does
the same problem occur?

--

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


"Capomaestro" wrote in message
...
Correct. The POP3 server sends the headers and then the OE rules
engine loops when it encounters the defective empty header when it
is directed to 'Delete it from server'.

"Michael Santovec" wrote in message
...
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.

Buenas noches: *Capomaestro* escribió:

Face it, OE6's rules engine is broken. There is no NG fix for this
other than an MVP sending in a defect report.

Excuse me, if I got something wrong in this thread - it was not always
easy to get your meaning - but did you not state in your initial post
that OE with inetcomm.dll version 6.0.2900.2962 is doing alright? That
is the current version of OE for Windows XP SP2, so why bug something
already fixed?

Also, you mentioned inetcomm.dll version 6.0.2800.1807 neither having
a problem, which is the current version of OE for Windows 2000 with IE 6
installed.

Maybe I am missing something here?

Saludos
Roland
--
Probleme mit OE? Hier gibt es die Lösungen: http://oe-faq.de!

"Ein Kompromiß ist nur dann gerecht, brauchbar und dauerhaft,
wenn beide Parteien damit gleich unzufrieden sind. (H. Kissinger)

Ja, Sie haben kein ahnung. LDFP (auf deutsch).

"Roland Bierlein" wrote in message ...
Buenas noches: *Capomaestro* escribió:

Face it, OE6's rules engine is broken. There is no NG fix for this
other than an MVP sending in a defect report.

Excuse me, if I got something wrong in this thread - it was not always
easy to get your meaning - but did you not state in your initial post
that OE with inetcomm.dll version 6.0.2900.2962 is doing alright? That
is the current version of OE for Windows XP SP2, so why bug something
already fixed?

Also, you mentioned inetcomm.dll version 6.0.2800.1807 neither having
a problem, which is the current version of OE for Windows 2000 with IE 6
installed.

Maybe I am missing something here?

Saludos
Roland
--
Probleme mit OE? Hier gibt es die Lösungen: http://oe-faq.de!

"Ein Kompromiß ist nur dann gerecht, brauchbar und dauerhaft,
wenn beide Parteien damit gleich unzufrieden sind. (H. Kissinger)

The guy is obviously not friendly to discussion and disses everyone who
tries to reply.

steve

"Roland Bierlein" wrote in message
...
Buenas noches: *Capomaestro* escribió:

Face it, OE6's rules engine is broken. There is no NG fix for this
other than an MVP sending in a defect report.

Excuse me, if I got something wrong in this thread - it was not always
easy to get your meaning - but did you not state in your initial post
that OE with inetcomm.dll version 6.0.2900.2962 is doing alright? That
is the current version of OE for Windows XP SP2, so why bug something
already fixed?

Also, you mentioned inetcomm.dll version 6.0.2800.1807 neither having
a problem, which is the current version of OE for Windows 2000 with IE 6
installed.

Maybe I am missing something here?

Saludos
Roland
--
Probleme mit OE? Hier gibt es die Lösungen: http://oe-faq.de!

"Ein Kompromiß ist nur dann gerecht, brauchbar und dauerhaft,
wenn beide Parteien damit gleich unzufrieden sind. (H.
Kissinger)

Buenas tardes: *Capomaestro* escribió:

Ja, Sie haben kein ahnung. LDFP (auf deutsch).

Well, at least I am able to realise that your education in languages
did not extend to good behaviour.

Saludos
Roland

[Fup2 (falls nötig) poster]
--
Probleme mit OE? Hier gibt es die Lösungen: http://oe-faq.de!

NOW LEAVE UPON THE INSTAND, said Death, and added,
BEFORE THE SEARING WINDS OF INFINITY SCORCH THY WORTHLESS CARCASS. (T. Pratchett)

What's to 'discuss'? I am only that way with people that are too lazy to do their own research, which amounts to 96.54% of all
posts here. Suffice to say I do not suffer fools gladly. Sadly, I have yet to uncover a response in this NG by an MVP that amounts
to more than RTFM of the OE Help file.

I know and can prove the defect in the 6.0.2800.1807 rules engine. I simply will not pay M$ for the priviledge of reporting it.

"Steve Cochran" wrote in message ...
The guy is obviously not friendly to discussion and disses everyone who
tries to reply.

steve

"Roland Bierlein" wrote in message
...
Buenas noches: *Capomaestro* escribió:

Face it, OE6's rules engine is broken. There is no NG fix for this
other than an MVP sending in a defect report.

Excuse me, if I got something wrong in this thread - it was not always
easy to get your meaning - but did you not state in your initial post
that OE with inetcomm.dll version 6.0.2900.2962 is doing alright? That
is the current version of OE for Windows XP SP2, so why bug something
already fixed?

Also, you mentioned inetcomm.dll version 6.0.2800.1807 neither having
a problem, which is the current version of OE for Windows 2000 with IE 6
installed.

Maybe I am missing something here?

Saludos
Roland
--
Probleme mit OE? Hier gibt es die Lösungen: http://oe-faq.de!

"Ein Kompromiß ist nur dann gerecht, brauchbar und dauerhaft,
wenn beide Parteien damit gleich unzufrieden sind. (H.
Kissinger)

Coming into a forum and calling the people there fools doesn't often provide
much help.


steve

"Capomaestro" wrote in message
...
What's to 'discuss'? I am only that way with people that are too lazy to
do their own research, which amounts to 96.54% of all
posts here. Suffice to say I do not suffer fools gladly. Sadly, I have
yet to uncover a response in this NG by an MVP that amounts
to more than RTFM of the OE Help file.

I know and can prove the defect in the 6.0.2800.1807 rules engine. I
simply will not pay M$ for the priviledge of reporting it.

"Steve Cochran" wrote in message
...
The guy is obviously not friendly to discussion and disses everyone who
tries to reply.

steve

"Roland Bierlein" wrote in message
...
Buenas noches: *Capomaestro* escribió:

Face it, OE6's rules engine is broken. There is no NG fix for this
other than an MVP sending in a defect report.

Excuse me, if I got something wrong in this thread - it was not always
easy to get your meaning - but did you not state in your initial post
that OE with inetcomm.dll version 6.0.2900.2962 is doing alright? That
is the current version of OE for Windows XP SP2, so why bug something
already fixed?

Also, you mentioned inetcomm.dll version 6.0.2800.1807 neither having
a problem, which is the current version of OE for Windows 2000 with IE
6
installed.

Maybe I am missing something here?

Saludos
Roland
--
Probleme mit OE? Hier gibt es die Lösungen: http://oe-faq.de!

"Ein Kompromiß ist nur dann gerecht, brauchbar und dauerhaft,
wenn beide Parteien damit gleich unzufrieden sind. (H.
Kissinger)

???? ????? "Steve Cochran" ?? ?????
...
Coming into a forum and calling the people there fools doesn't often
provide much help.


steve

"Capomaestro" wrote in message
...
What's to 'discuss'? I am only that way with people that are too lazy to
do their own research, which amounts to 96.54% of all
posts here. Suffice to say I do not suffer fools gladly. Sadly, I have
yet to uncover a response in this NG by an MVP that amounts
to more than RTFM of the OE Help file.

I know and can prove the defect in the 6.0.2800.1807 rules engine. I
simply will not pay M$ for the priviledge of reporting it.

"Steve Cochran" wrote in message
...
The guy is obviously not friendly to discussion and disses everyone who
tries to reply.

steve

"Roland Bierlein" wrote in message
...
Buenas noches: *Capomaestro* escribió:

Face it, OE6's rules engine is broken. There is no NG fix for this
other than an MVP sending in a defect report.

Excuse me, if I got something wrong in this thread - it was not always
easy to get your meaning - but did you not state in your initial post
that OE with inetcomm.dll version 6.0.2900.2962 is doing alright? That
is the current version of OE for Windows XP SP2, so why bug something
already fixed?

Also, you mentioned inetcomm.dll version 6.0.2800.1807 neither having
a problem, which is the current version of OE for Windows 2000 with IE
6
installed.

Maybe I am missing something here?

Saludos
Roland
--
Probleme mit OE? Hier gibt es die Lösungen: http://oe-faq.de!

"Ein Kompromiß ist nur dann gerecht, brauchbar und dauerhaft,
wenn beide Parteien damit gleich unzufrieden sind. (H.
Kissinger)