Daniel wrote:
Paul B. Gallagher wrote:
Daniel wrote:
Paul, as ChrisI mentioned, a couple of days ago he posted to moz.test to
check out if he had a problem. I'm fairly certain (or I'd assume) that
ChrisI would have been subscribed to moz.test previously, and for this
test post, which worked, I guess he un-subscribed, posted the test
message, then re-subscribed to check.
I'm wondering if there might have been some sort of machine memory at
work in this case .... i.e. ChrisI's 'puter or the Moz server
"remembered" that ChrisI had been subscribed to the server, so when this
test post rocked up, it was let through, where as you, Paul, may never
have been subscribed to moz.test/m.d.a.seamonkey (which I think was the
original "problem" group), so when your message showed up, Paul, it/they
were rejected.
Paul, if you think what I've hypothesised above makes any sort of sense,
can you subscribe to moz.test, post a message, check it arrives,
un-subscribe from group, send another test, re-subscribe and see if
things are different to your current situation?
(Do I really want to post this "drivel"?? If nothing else, it might
prove a negative. O.K.)
OK, here are the results for your drivel.
1) Subscribed to mozilla.test from this account, downloaded all posts
and marked all as read. Posted a test message. It went through
instantly. Got new messages, mine had arrived intact.
2) Unsubscribed from mozilla.test, opened the test message in my Sent
folder ("edit as new"), made sure to select the same account with the
munged email address as I had used the first time, tried to post. Got
two superimposed error messages:
a) In back:
Sending message - Test
Status: Assembling message...
Progress: [progress bar with green bit cycling endlessly]
[Cancel]
b) In front:
Send Message Error
(!) Sending of message failed.
Please verify that your Mail & Newsgroups settings
are correct and try again.
It didn't matter that I had previously subscribed. What mattered was
that I was not currently subscribed.
Saw one post by you in moz.gen, but no second one!
O.K., so my "drivel" was drivel!! No "machine memory".
So how/why did ChrisI succeed??
And, today, apparently, Hartmut has been testing this situation in
moz.test as well!
--
Daniel
User agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:21.0) Gecko/20100101
Firefox/21.0 SeaMonkey/2.18 Build identifier: 20130418192405
or
User agent: Mozilla/5.0 (X11; Linux i686 on x86_64; rv:21.0)
Gecko/20100101 Firefox/21.0 SeaMonkey/2.18 Build identifier: 20130403022815
_______________________________________________
support-seamonkey mailing list
[email protected]
https://lists.mozilla.org/listinfo/support-seamonkey
