|
|
 | | From: | John H Meyers | | Subject: | Bug - new outgoing messages are neither sendable nor saved | | Date: | Tue, 11 Jan 2005 17:11:21 -0600 |
|
|
 | I have repeatedly encountered this problem
with both 7.54 and 7.54u1:
Although most outgoing (SMTP) mail messages
get sent correctly, it sometimes happens that
in the midst of my composing a short outgoing email,
some office activity interrupts my attention,
and may require me to do some other internet browsing;
when I return to the "compose" window in progress
and finally click "send," the "send" button
recognizes the mouse click and "depresses,"
but nothing else happens -- the message just sits there,
and is never sent (I was addressing these to another
of my own email accounts, and can attest to the fact
that these "dead send button" messages in fact never go out).
The message also does not move to the "Sent" folder,
but remains in the "Drafts" folder.
Finally (and here is a clue to what may be going wrong),
when I try to re-open the message from the "Drafts" folder,
the message body shows as "Message not downloaded,"
and all my just-typed text has completely vanished.
I understand that "Message not downloaded" can apply to externally
composed messages (or newsgroup posts) which I *receive* but do not
retain; however, in this case, I composed this message myself,
on this computer, so it must be an error for Opera to have
lost the text which I just typed, before I ever clicked "Send."
By the way, in the "Drafts" folder, my "unsendable" message
has today's date and recent time in the "sent" column, even though
in fact the message was never sent, and its text has evidently
been lost by Opera (except on the screen, if I have kept the
original "compose" window still open).
Finally, the one and only M2 mail account which I have defined
is a "News" type account, specifying both my SMTP server (*not* IMAP!)
and my NNTP server (the latter irrelevant to sending outgoing SMTP mail).
Although 95% of my outgoing messages do get sent,
the fact that about 5% of them end up with a "dead Send button"
(and the "saved Draft" also missing the entire just-composed
message body), plus other SMTP bugs previously reported,
leave me with a very good browser, but a very unreliable
email client, as of version 7.54u1.
Thank you for your interest.
|
|
| | From: | Lester Stiefel | | Subject: | Re: Bug - new outgoing messages are neither sendable nor saved | | Date: | Wed, 12 Jan 2005 03:23:58 -0500 |
|
|
| On Tue, 11 Jan 2005 17:11:21 -0600, John H Meyers wrote:
> I have repeatedly encountered this problem
> with both 7.54 and 7.54u1:
>
> Although most outgoing (SMTP) mail messages
> get sent correctly, it sometimes happens that
> in the midst of my composing a short outgoing email,
> some office activity interrupts my attention,
> and may require me to do some other internet browsing;
> when I return to the "compose" window in progress
> and finally click "send," the "send" button
> recognizes the mouse click and "depresses,"
> but nothing else happens -- the message just sits there,
> and is never sent (I was addressing these to another
> of my own email accounts, and can attest to the fact
> that these "dead send button" messages in fact never go out).
>
> The message also does not move to the "Sent" folder,
> but remains in the "Drafts" folder.
>
> Finally (and here is a clue to what may be going wrong),
> when I try to re-open the message from the "Drafts" folder,
> the message body shows as "Message not downloaded,"
> and all my just-typed text has completely vanished.
>
> I understand that "Message not downloaded" can apply to externally
> composed messages (or newsgroup posts) which I *receive* but do not
> retain; however, in this case, I composed this message myself,
> on this computer, so it must be an error for Opera to have
> lost the text which I just typed, before I ever clicked "Send."
>
> By the way, in the "Drafts" folder, my "unsendable" message
> has today's date and recent time in the "sent" column, even though
> in fact the message was never sent, and its text has evidently
> been lost by Opera (except on the screen, if I have kept the
> original "compose" window still open).
>
> Finally, the one and only M2 mail account which I have defined
> is a "News" type account, specifying both my SMTP server (*not* IMAP!)
> and my NNTP server (the latter irrelevant to sending outgoing SMTP mail).
>
> Although 95% of my outgoing messages do get sent,
> the fact that about 5% of them end up with a "dead Send button"
> (and the "saved Draft" also missing the entire just-composed
> message body), plus other SMTP bugs previously reported,
> leave me with a very good browser, but a very unreliable
> email client, as of version 7.54u1.
>
> Thank you for your interest.
While the bug is being looked into, try the following,
File>save as draft, then go back and retrieve it later, and
see if you can send it or paste into an outgoing message.
--
Lester Stiefel
In Romans 1 there are qualities of Unregenerate man listed
which describe him in the last days.
Is your quality found on this list??
|
|
| | From: | John H Meyers | | Subject: | Re: Bug - new outgoing messages are neither sendable nor saved | | Date: | Tue, 18 Jan 2005 19:08:38 -0600 |
|
|
| Lester Stiefel wrote:
> While the bug is being looked into, try the following,
> File>save as draft, then go back and retrieve it later, and
> see if you can send it or paste into an outgoing message.
It is almost certain that I have done "saves" (CTRL-S)
during every message composition, because I am in the habit
of doing saves after every few sentences, all the time,
and in fact I always do a "save" one last time,
just before I click "send" -- this is a habit I have
long practiced with every word processor (before closing),
and every email program (before sending).
However, since occurrences of this problem are not predictable
(and I don't know exactly how to reproduce it on demand),
I am not able to stage a test of closing completely
and re-opening just before a "send" fails :)
BTW there is no "File > Save as draft" in the compose menu,
although there is a "Save" button.
The only time I have been able to use copy/paste
to recover from such incidents is when I have still left
the original message window open for display, in which case
it appears that the displayed screen text remains copyable
in volatile memory (or cache), while the text supposedly
"saved" (to disk) has disappeared into a wormhole.
Once again, I find that some outgoing messages which I
compose locally during an Opera session (and even save
while composing) can not be sent ("send" button depresses
but is ignored), and when this happens, any subsequent
attempt to re-display the message (which *is* listed
in "Drafts") says "message not downloaded" -- but
of course NEW outgoing messages are never "downloaded"
from anywhere, and there is no excuse for the disappearance,
especially after many "saves" were performed during composition.
Another way to state the problem is that "save" is unreliable,
since despite "saving" many times, the draft text may have
disappeared from everywhere but display memory (or cache),
and can then be neither sent nor re-displayed at all.
Thank you for your interest.
|
|
| | From: | John H Meyers | | Subject: | Re: Bug - new outgoing messages are neither sendable nor saved | | Date: | Thu, 20 Jan 2005 20:54:31 -0600 |
|
|
| Is no one else noticing this problem?
I'm guessing that it may relate to the options
in my M2 "news" account -- in my "incoming" tab,
I have left all unchecked -- in particular, neither
"download message body when checking" nor
"keep local copy of message body" are checked.
Now, those options are meant to apply to INCOMING only
(which in my case means newsgroup postings only,
because I have defined only one "news" type account,
specifying just an NNTP server and an SMTP outgoing mail server).
Certainly it would be a BUG if the notion
not to "keep local copy of message body" were applied
as well to an OUTGOING message which I am composing myself,
but in fact that's exactly what seems to have been happening
on those occasions when the "send" button refuses to send it,
after which I find that if I attempt to display
my saved OUTGOING message from the "drafts" folder,
the displayed text says only "message body not downloaded,"
and my entire original OUTGOING message has disappeared!
I am quite convinced that this is a bug in 7.54 (and 7.54u1);
it happens only about 5% of the time, however, usually after
some additional browsing and other activity has been
interspersed with my composing activity (although
at no time had I ever closed my "compose" window),
and I am unable to pin down exactly what action(s)
lead to the disappearance of my OUTGOING message body text.
For me, then, M2 is very well designed but still unreliable,
and I still have to relegate it to unimportant business,
since I can't afford the never-sent emails (a prior acknowledged
bug with "news" accounts and only "Bcc:" addressees) and the
occasional completely lost outgoing message texts (this new bug).
Thank you for your interest.
|
|
| | From: | Steven V. Gunhouse | | Subject: | Re: Bug - new outgoing messages are neither sendable nor saved | | Date: | Fri, 21 Jan 2005 14:01:48 GMT |
|
|
| On Thu, 20 Jan 2005 20:54:31 -0600, John H Meyers wrote:
> Is no one else noticing this problem?
>
> I'm guessing that it may relate to the options
> in my M2 "news" account -- in my "incoming" tab,
> I have left all unchecked -- in particular, neither
> "download message body when checking" nor
> "keep local copy of message body" are checked.
>
> Now, those options are meant to apply to INCOMING only
> (which in my case means newsgroup postings only,
> because I have defined only one "news" type account,
> specifying just an NNTP server and an SMTP outgoing mail server).
>
> Certainly it would be a BUG if the notion
> not to "keep local copy of message body" were applied
> as well to an OUTGOING message which I am composing myself,
> but in fact that's exactly what seems to have been happening
> on those occasions when the "send" button refuses to send it,
> after which I find that if I attempt to display
> my saved OUTGOING message from the "drafts" folder,
> the displayed text says only "message body not downloaded,"
> and my entire original OUTGOING message has disappeared!
>
> I am quite convinced that this is a bug in 7.54 (and 7.54u1);
> it happens only about 5% of the time, however, usually after
> some additional browsing and other activity has been
> interspersed with my composing activity (although
> at no time had I ever closed my "compose" window),
> and I am unable to pin down exactly what action(s)
> lead to the disappearance of my OUTGOING message body text.
>
> For me, then, M2 is very well designed but still unreliable,
> and I still have to relegate it to unimportant business,
> since I can't afford the never-sent emails (a prior acknowledged
> bug with "news" accounts and only "Bcc:" addressees) and the
> occasional completely lost outgoing message texts (this new bug).
>
> Thank you for your interest.
My settings there sound the same as yours - I don't download message
bodies nor do I keep local copies. And everything works fine.
Under Outgoing, do you have Opera set to save sent messages? How about to
send immediately? Those are the settings you ought to look at, not
anything on your Incoming tab. Also, some ISPs want you to fetch new
messages when you send, there's a setting for that.
--
Using Opera's revolutionary e-mail client: http://www.opera.com/m2/
|
|
| | From: | John H Meyers | | Subject: | Re: Bug - new outgoing messages are neither sendable nor saved | | Date: | Sun, 23 Jan 2005 03:52:03 -0600 |
|
|
| Steven V. Gunhouse wrote:
> Under Outgoing, do you have Opera set to save sent messages?
> How about to send immediately?
> Those are the settings you ought to look at,
> not anything on your Incoming tab.
Much software "ought" to work properly, but just doesn't :)
My "Outgoing" tab (on a *News* account)
has these options only:
o Automatically wrap outgoing messages
[irrelevant, but not checked]
o Queue messages (do not send immediately)
[not checked, so yes, send immediately,
but also irrelevant, since the "send" button
never even finds anything to send, because
the composed message has been *totally*lost* from the disk]
o Send queued e-mail after checking email
[not checked, but irrelevant, because in fact
you can not *check*email* from a NEWS account]
o Add contacts when sending message
[not checked, also irrelevant]
I still suspect that the M2 client gets confused
between Outgoing and Incoming messages and options,
because "message body not downloaded" is something
which normally appears only when *Incoming* messages
(postings) have either never been downloaded, or else
have been downloaded and then (intentionally) forgotten again.
The loss of some of my personally composed, outgoing messages
looks very suspiciously like that, where Opera's M2 client
may have thought that my own *outgoing* message body
(never even sent in the first place)
could be disposed of in the same way -- perhaps M2
thought that my outgoing message was actually an
incoming (news) message, and since I do not ask M2
to save downloaded postings at all, perhaps that's why
it trashes an occasional *outgoing* message as well.
> Also, some ISPs want you to fetch new messages when you send,
> there's a setting for that.
I don't see it, but if you mean to authenticate to an SMTP
server by first checking for mail on a POP server,
not only do we not require that, but once again,
there is *no* POP server associated with a NEWS account!
Thus far I have seen three bugs in 7.54 re NEWS accounts:
o The "Always BCC" option is most of the time ignored
when sending mail (perhaps not when posting news,
or vice-versa), so that I have to manually insert
my own address into "Bcc:" on every composed email message.
o When posting news, addresses even manually inserted into "Bcc:"
are also ignored, unless at least one "To:" address is also provided
(you argued with me on that one also, but finally someone from Opera
Software reproduced it and agreed that it happens with News accounts).
o Sometimes, after having done other browsing while composing,
even after having used "save" many times during composition,
I finally press "Send" and it won't send at all; in every such
case, the message subject (with a time stamp) appears in "Drafts"
but trying to re-open the message from "Drafts" shows only
"Message body not downloaded," and the entire composed message
has completely and permanently vanished.
Bottom line:
This version has an unreliable M2 client, at least with News accounts,
and it is "not ready for prime time" as far as I am concerned.
Thank you for your comments and interest.
|
|
|
