Netscape/SeaMonkey "SEND" Anomaly Rears Its Head . . . again

[RHPConsult]

Many months (years?) ago I posted here the account of my then Netscape Communicator which kindof, sortof, periodically hiccuped, when asked to SEND an e-message. The only "solution" I was able to construct was to SAVE to DRAFTS, then reopen and bingo, off the message would go.

I never was able fully to eliminate the problem, no matter what kind of maintenance (or goat sacrificing) I attempted. Then it disappeared, as spontaneously as it seemed initially to appear.

Now, however, over the past couple of days It's Baaaack, this time in SeaMonkey. I'm using the same "therapy" to overcome it,  but I'd prefer avoiding it altogether.

All suggestions/ideas welcomed.

[antony]

RHPConsult,

I'd start with something basic, I assume you have correct settings of mail servers in SeaMonkey, it might be a good idea to check those settings again.

I suspect it's due to spam sending prevention in your ISP's mail server. Try to click get mail before sending out, you will have 5 or 10 minutes period allowing you to send out email (after checking for new emails).

Hope this helps.

Antony.

[RHPConsult]

Thanks, Antony.

QUOTE

I assume you have correct settings of mail servers in SeaMonkey, it might be a good idea to check those settings again.

Yup!

In fact what makes this behavior so strange is that is just started . . . boom . . .after months and months of SeaMonky working faultlessly. Moreover, with Communicator, in days of yore, it was episodic – long periods of daily stalling, faollowed by periods of OK operation.

Not sure I grasp what you mean "spam sending prevention in your ISP's mail server".

But, I'll certainly apply your "prescription" – click get mail before sending out, you will have 5 or 10 minutes period allowing you to send out email (after checking for new emails).

What seems to have worked in the past w/Communicator was saving to DRAFTS a stalled message and then immediately re-opening it to SEND. Clicking on GET MAIL seems as though it would be a bit faster.

The "why" still escapes me.  

[antony]

RHPConsult,

What I meant to say was, most ISPs do not want to open an SMTP server (outgoing server) for people to send out mass emails, therefore, they need to know if you are their customer. The easiest way to verify this simply (for you to) check if you have any new emails. Then you will have 5 or 10 minutes "period" (as being verified) to send email out.

I hope this clear enough. Sorry, I should've worded it in a better way.

I have a feeling it was the problem that you resorted to save to draft, then send it from draft.

In SeaMonkey Mail, you can set a small time interval in "Check for new messages every __ minutes" (under Server Settings).

Back to Communicator times, I was using Windows :-)

Antony

[RHPConsult]

QUOTE(antony @ Jul 21 2006, 09:04 AM) <{POST_SNAPBACK}>

RHPConsult . . .most ISPs do not want to open an SMTP server (outgoing server) for people to send out mass emails, therefore, they need to know if you are their customer. The easiest way to verify this simply (for you to) check if you have any new emails. Then you will have 5 or 10 minutes "period" (as being verified) to send email out.

Does not seem unreasonable.

QUOTE

In SeaMonkey Mail, you can set a small time interval in "Check for new messages every __ minutes" (under Server Settings).

5 minutes has always been my usual setting. Were I to select a longer period might that somehow eliminate the "problem"?

Incidentally the problem has not appeared at all today? Do you have an "aura" for producing positive outsomes halfway eound the globe?

[antony]

QUOTE(RHPConsult @ Jul 22 2006, 08:38 AM) <{POST_SNAPBACK}>

5 minutes has always been my usual setting. Were I to select a longer period might that somehow eliminate the "problem"?

Incidentally the problem has not appeared at all today? Do you have an "aura" for producing positive outsomes halfway eound the globe?

I think shorter period should help. I've always had a feeling that it might due to the fact that sometimes you spend longer time to compose emails, and the ‘grace period’ hence be lapsed (Note, I haven't verified this. Only guessing.)

This problem could also be at server's end. I have similar situations with Mail.app as well. But I always click "Get mail", and it usually works.

I might have a crystal ball :-)

Antony.

[RHPConsult]

QUOTE(antony @ Jul 21 2006, 06:19 PM) <{POST_SNAPBACK}>

I think shorter period should help. I've always had a feeling that it might due to the fact that sometimes you spend longer time to compose emails, and the ‘grace period’ hence be lapsed (Note, I haven't verified this. Only guessing.)

 Interesting "guess", Antony. Never have had anything like that stated so directly/clearly. Nothing in Mozilla's Help, that I've found.

Oh yes, I probably do spend too much time composing e-mails. I am not known for spare/skinny communications.