| Re: interrupted while sending mail; with error message |
|
 |
|
 |
|
 |
|
 |
Group: comp.groupware.lotusnotes.admin · Group Profile
Author: yellowchilliyellowchilli Date: Sep 1, 2008 18:33
thanks for your reply.
nufortunately we're still on R6 so no autosave..
I eventually found the sent copy intact in her sent folder. the
recipient received it twice.
I do suspect offline/local replica causing this-
itd explain why user was interrupted after pressing Send, because of
authentication with server for the 1st time that session hence passord
expiry nag;
would also explain how it did not appear in sent folder immediately as
thats the way it is with local replicas.
simple.
too bad i checked with user and local replica was apparently NOT in
use...not available at all.
even IBM support couldnt answer me this one....................sigh
On Aug 22, 5:09Â pm, Lester thanks.com> wrote:
> Not sure I can help much. Â Just some general thoughts. Â I'm not sure I
> have seen that message before but in a way it reminds me of the
> message you get that tells you the location document was being edited
> elsewhere when you try to save it. Â If the user is trying to salvage
> the contents of the message are you using the autosave feature in
> R7/R8? Â If the user doesn't have save sent mail turned on in
> preferences then it's not going to be the sent view. Â Did the
> recipient receive it? Â Are they a laptop user working in offline mode?
>
> On Tue, 19 Aug 2008 21:03:43 -0700 (PDT), yellowchilli
>
> gmail.com> wrote:
>>hi hope somebody here can help
>
>>user was interrupted (by a password change nag) while sending an
>>email.
>>after the password was changed, user continued to send mail but was
>>greeted with the following:
>
>>Are you sure? This message was already sent to one or more recipients.
>>If you send it again, some recipients may receive more than one copy
>>of the message. Select Yes to continue, Noe to cancel sending.
>
>>After clicking 'No', it appears the message was apparently not sent
>>and not saved in Sent Box.
>
>>This doesnt look like a common error and I can't seem to reproduce
>>it..
>
>>Any ideas appreciated.
|