Mailwasher Slow

[astarlaworks]

Back to the old version for me !
Checking mail it seems to go into limbo and the stop button ignores me. Loading up is abysmally slow, too many things going on.
Quite a few posts indicate .NET to be the problem, as a programmer myself I was think of switching from Visual Foxpro to .NET. I might be re-thinking this idea.

[stan_qaz]

.Net has its good points and if you work at it you should be able to hide the initial startup delay by coming up with a pre-loader app like they did to speed up Office.

I'm not a .net fan myself so I'd never suggest a friend go there... If I was consulting and needed a steady income stream I'd suggest it to a client that I didn't like very much.

[rusticdog]

Back to the old version for me !
Checking mail it seems to go into limbo and the stop button ignores me. Loading up is abysmally slow, too many things going on.
Quite a few posts indicate .NET to be the problem, as a programmer myself I was think of switching from Visual Foxpro to .NET. I might be re-thinking this idea.

The main issue with .NET is the loading of the libraries that aren't loaded on startup given we're using 3.5, if you see how long MailWasher takes to start after first booting, then exit and restart MailWasher you'll see the difference.

That said we haven't full optimised the startup and removed everything that isn't necessary for MailWasher to open, so we might be trying to load libraries that simply aren't required. So I wouldn't blame .NET as being the only reason MW is slow to start. A large blacklist and friends list too will also cause delays, something we've improved on for the coming version.

The Checking Mail going into limbo though sounds like either a setup issue (possibly a duplicate account) or the email server doesn't like PIPELINING, which the old MailWasher never used. I'd need to see logs to verify the cause, so if you still have the new version installed let me know.

[V65magnafan]

It's not just slow to load. It hangs on checking mail accounts. It hangs on washing--it stalls. Fifteen minutes sitting there telling me it's washing two spam messages and several deletes?

And, why do I have to click on the delete garbage can button two, three, four times before it acknowledges the command?

I have a clean XP Pro system with lots of free space on C.

So far, I'm disappointed. I'm thinking of relying on my provider's Yahoo mail cleaner and be done with it.

Are you folks coming up with a fix? (1.0.10) .

[stan_qaz]

You may be clicking the delete button before it gets around to the first state switch and then having to wait out one switch for each click. There is a bug that makes this slow but you can avoid hitting it by clicking the delete and then clicking the next message, when the highlight moves you"ll know the delete should have been set on the previous message.

Turning off the bolding of unread messages and restarting MW or just closing/restarting MW might clear out the delay, it doesn't usually bite until several hundred messages have been loaded.

[V65magnafan]

Thanks for the quick reply. Yes, closing and restarting MW "cleans it out". Should that be a normal operating procedure? I don't think so.
Nevertheless, it will be interesting to see the improvements in each version.

[stan_qaz]

They are prioritizing bugs, most work right now on the ones that keep folks from working in MW at all, next in line are ones that can be worked around and adding missing features. The actual order they appear is set by the developers based on programmer time and how much time it is going to take to fix the problem. What gets done when has always been left as a surprise until it gets to the beta stage then rusticdog may let folks know a fix is coming in the next release.

[V65magnafan]

Neat answer. Thanks. Really.

I appreciate it.

[stan_qaz]

Not a problem, I've been using and testing beta versions for a while so I have some of the answers, for the ones I don't we all have to wait on rusticdog for official ones or other posters that know them.