[koala2]

I have about 7 customers, half on jag and half on panther and all an different G4s with plenty of RAM and "clean" machines.

One user has also randomly the "cannot send problem" as described here. I tried everything from rebuilding mailboxes, new fresh Jaguar-Setup from scratch, removing old mails of the mailboxes. I followed nearly every hint on Apples Mail-Discussionforum.

Since I am 100 percent against Microsoft I do not want the user to switch to Entourage. And for homogenity I would like to stay on Mail.app as well.

Another user on Panther (setup from scratch) crashes with Mail after a Mails has been sent. (So he never know If Mail reaches the To-destination or not...).

This problems go on wie half of my users, randomly changing behaviours. Some are on cable, some are on LANs, some are on 56kb direct.

So far I am out of ideas and hope apple helps soon out with a "not so flaky" email-app.

And a question offtopic I would like to know: Does anyone know how a mailserver (at the provider) does know you have picked up mail already? Because one of my users gets randomly mail twice and triple (even if his mail-account is set to delete immediatly).
Does he remember the client by IP, or something else?

[absmiths]

Originally posted by koala2:
And a question offtopic I would like to know: Does anyone know how a mailserver (at the provider) does know you have picked up mail already? Because one of my users gets randomly mail twice and triple (even if his mail-account is set to delete immediatly).
Does he remember the client by IP, or something else?

I can't answer your other questions, but mail servers know that you have read an email because the mail reader sets the flags on the email to READ. The email program downloads all UNSEEN email, and after it decides that you have read the mail it sets the flag. Alternately, a mail program that keeps the mail locally will delete and expunge the folder.

[cpac]

the cannot send email problem occurs when the designated SMTP server cannot be reached for one reason or another - this can be a server, or a client-side error, but regardless, the solution is to hit the "try again later" button, and wait.