Recently, my ISP implemented some changes in their Mail system.
Now, I can't send Windows Live Picture Mail. (I used to be able to.)
I keep getting this error:
There was an error while publishing photos.
Subject 'picture test . . .'
Server: 'smtp1.mail.visi.com'
Windows Live Mail Error ID: 0x8BEE000B
Protocol: SMTP
Port: 25
Secure(SSL): No
I did a little checking on the web, and thought the problem must be with my
ISP (Visi.com).
I sent there support personnel an email about this, and was informed that no
change had been made that would prevent these email from being sent.
But I'm not so certain of that.
What must I do to find the problem?
Why can't I continue to send Windows Live Picture Mail?
What is so special about this picture mail anyway?
Why should I be able to send a picture, but not Picture Mail?
I believe all of my other mail is working okay and even being dealt with
properly by Visi.com's mail system.
Has Visi gone doofus on me? Or what?
Thoughts?
Anyone?
Thanks,
- Stan
--
Gary VanderMolen, MS-MVP (Mail)
"Stan Shankman" <stant...@visi.com> wrote in message news:Og5TDl81...@TK2MSFTNGP03.phx.gbl...
"Gary VanderMolen" <Ga...@NoMail.invalid> wrote in message
news:OKN8ol91...@TK2MSFTNGP05.phx.gbl...
--
Gary VanderMolen, MS-MVP (Mail)
"Stan Shankman" <stant...@visi.com> wrote in message news:eGfxqJ%231IH...@TK2MSFTNGP04.phx.gbl...
"Stan Shankman" <stant...@visi.com> wrote in message
news:eGfxqJ#1IHA...@TK2MSFTNGP04.phx.gbl...
Signed in? I think I am signed in. In the upper right corner of Live Mail,
it says "(online)".
I assume that means I am signed in.
Just to reiterate, I used to be able to send Windows Live Picture Mail.
I liked sending Live Picture Mail, and my contacts liked receiving it.
But recently, I have not been able to send any Live Picture Mail.
I keep getting that: 0X8BEE000B error.
It has been going on for weeks now.
I am under the impression that somehow my ISP (Visi.com) is preventing this
from working.
My suspicion is mainly based on the coincidence between the time of "work"
Visi did on their mail server, and the occurrence of my problem.
But, when I contacted my ISP (Visi.com), they inform me; "No change was made
that could be causing my problem."
I am suspicious this may not be true, and so I am here on this board asking
if anyone knows of any similar case when an ISP was at fault?
Or, does anyone have any thoughts about this? Is there anything specific
that I should be asking my ISP.
Is there anything I should be looking at?
I want to restore my ability to send Windows Live Picture Mail.
Thanks,
- Stan
"Ron Sommer" <rso...@nospam.ktis.net> wrote in message
news:eweaLPA...@TK2MSFTNGP05.phx.gbl...
--
Gary VanderMolen, MS-MVP (Mail)
"Stan Shankman" <stant...@visi.com> wrote in message news:%236wOlNK...@TK2MSFTNGP04.phx.gbl...
just to let you know that I'm having the exact same problem (could send
photo-mails before, can't anymore, always get 0x8bee000b. Normal mails work
fine). I've reported it to the helpdesk and they are investigating.
As for your question about WL Picture/Photo mail: the difference with
regular emails (with attached pictures) is that WLM uploads the actual
pictures to a web server and only includes thumbnails (with links to the
pictures) in the email itself.
This is much more efficient than sending the full-size pictures with the
email, especially if you send an email to multiple people.
Anyway, will update if I receive more info from the helpdesk.
Cheers,
Ruud
If this doesn't help, then at least we'll have ruled out language
conflict as a possible cause.
--
Noel
"Stan Shankman" <stant...@visi.com> wrote in message
news:Og5TDl81...@TK2MSFTNGP03.phx.gbl...
I still do not know what was going on, but I can tell all of you what I did
to make Windows Live Mail start sending Picture Mail again.
Using Windows Live Mail's "Tools" menu, I opened "Options". Went to the
"Advanced" tab, and clicked on "Maintenance". I placed a check in "compact
the database on shutdown every X runs". And I Chose "1" for the number of
runs.
I closed the Options pain, and then closed Live Mail. Soon afterwards, the
"Compact the Database" permission box appeared - I allow it to run. This
running (in my case) lasted for several minutes. After it finished I
restarted Windows Live Mail.
I know, I know you guys think the error was gone; right? But guess what? No
cigar.
However, I left the "every 1 runs" in place, and shut Live Mail down again
(and then again and even again). At this point memory fails me. But I can
say for certain that at some point (after a sufficient number of "runs"),
Windows Live Mail came back to being its old self. So now, I have no more
error 0x8BEE000B. Hallelujah!
How would anyone have known?
Just another mystery bubbling from the bits and stew that cook down in my
CPU . . .
:-)
So, if any of you are getting this same error, you may wish to try my
solution.
Oh, and I would like to take this opportunity to bid Bill Gates a fond adieu
from is daily rôle at Microsoft.
I will be watching to see what he does from now, and into the future.
- Stan
"Stan Shankman" <stant...@visi.com> wrote in message
news:Og5TDl81...@TK2MSFTNGP03.phx.gbl...
It turns out there is a 500 photos-per-calendar-month limit on the use of
photo-emails. I suspect the 0x8BEE000B error is trying to tell us we hit that
limit.
In any case, as we're now in a fresh new month, I thought I'd have a go once
more: and yep... photo-emails work fine for me again.
Ruud
I wasn’t even close to having sent 500 pictures.
No, this error was caused by some other mechanism but seems to have been
“fixed” by following the procedure in my earlier post.
Outwardly, it doesn’t seem that an uncompressed file structure should have
any bearing on the ability to send Picture Mail, but it sure seems to have.
Maybe it is yet some kind of bug.
- Stan
"Ruud" <Ru...@discussions.microsoft.com> wrote in message
news:435676CD-5B19-4325...@microsoft.com...
In Live Mail, go to Tools -> Options -> Send. Uncheck the box for "Uploaded
larger images to the web..."
NB
--
...winston
ms-mvp mail
"Cragg" <Cr...@discussions.microsoft.com> wrote in message news:094EBDF8-5AB2-4AAB...@microsoft.com...
This reminds me of a bug with Microsoft Worldwide Telescope that has gone
unfixed for six months, won't allow the software to work with two very
popular mind you older video classes that meet spec. Someone is asleep at the
wheel.
Cragg
--
...winston
ms-mvp mail
"Cragg" <Cr...@discussions.microsoft.com> wrote in message news:20CA00FF-3785-473D...@microsoft.com...