>As for that mac.com address, there is currently an ongoing problem at >Apple's .Mac servers. See this news report: Thanks for the info. I had a feeling there was a problem, but I do trust .mac to finally deliver at some point.
>The more you post the more it seems as if it is only a few messages that >are exhibiting the problem. Well, the reason it *seems that way* is because I've said so. It doesn't affect all messages, yes, but it affects many messages on many different accounts, including my schools, which is run on Mac and usually does not display any kind of problems like this. I suppose I'll have to look at the actual transaction data, the next time the problem arise. Maybe I'll be wiser then. >Did you follow Tim's instructions to use >another program (not Mail; I've forgotten the particular program people >use here to go into the POP account and manipulate it directly, killing >corrupt email once and for all) to remove the message from the server? Explain the difference between using Pop Monitor to delete the messages and using PowerMails feature to delete messages at download. I already tried the latter and it worked for now. But it also means I can't leave messages on server and feel secure the problem won't come back. If you also could explain why another client could download from one of the accounts, leave the messages and know that it was downloaded, where Powermail couldn't, that should prove interesting. >Mikael Byström sez: > >>How can you say so, Karen, when I've told that the problems at question >>here continued in PM 4.1.2 and 4.1.3, *even* with a fresh new POP >>account? > >She can probably say so because she isn't exhibiting the problems you're >having. I, too, am not having the problems you describe. Which is no reason for you to hint the problem ain't real at my end, is it? I will never ever put off a user with someting akin to "if I'm not having this particular problem, then you can't have it either". Which effectively is what you're saying. Why do you try this particular way? >Honestly, if you do and no update has fixed it >to your satisfaction, move on to another client that does. This comment take the price. Most people on software discussion lists take a common interest in identifying problems with the software being discussed so that workarounds can be established and spread in the user comunity and the maker can be informed how to reproduce the problem and get rid of it in the next incremental update. your "please, move along" comment hints that you're not like those people. It also means you're not part of the solutio, at least not regarding this problem. That is your prerogative of course, but I kindly ask from you to be a little less condescending next time you feel a need to put somebody off.
