Within the last 12 hours Microsoft has started blocking all messages that link to YouTube. Messages are not received and the sender gets the dreaded “The following message could not be delivered to all recipients” error.
In the past, Microsoft has taken measures to stop propagation of viruses by blocking messages containing phrases such as gallery.php, download.php, .scr and .pif. I see no virus here.
YouTube now joins the list of blocked sites including eBuddy and MediaFire. eBuddy was supposedly blocked because of advertising messages when starting a new conversation, and MediaFire blocked to try stop distribution of the leaked Windows Live Messenger 9.0.
I’m completely baffled as to why a block would be placed against YouTube, and eagerly await an explanation. Trying to hamper competition like this just seems ridiculous, it’s not like this would go unnoticed, lots of users are complaining on forums already.
Workaround? Try the domain youtube.info instead, or remove the http://www.
Following up on my last post about the updated sendMsg script, I have another update available.
This update will now catch error 800 from the server. The server imposes a limit of creating 8 IM sessions in any 60 second period and will throw this error if you try calling createSession a 9th time. As such, the script is not suited for sending messages to more than 8 contacts in the same login session. All other changes are programming improvements.
This will be the final update for a while, if there are any major bugs reported I will fix them, otherwise consider this stable.
Download and check out Troubleshooting phpListGrab if you are having connecting problems (phpListGrab uses the same code base). I will also be posting more troubleshooting information for other problems I have recently discovered with server configuration compatibility.
The script I created over two years ago to send a message using PHP has gained quite a lot of exposure over the last few months, and a common request I have been getting is the ability to send messages to more than one user.
Over the weekend I modified the class with the following changes:
- Function to manually create an IM session with a user.
-
- Function to send a message on the newest IM session.
- Font face and colour support for the sendMessage() function.
- Better error handling when connecting to the messenger server.
- simpleSend() function to send a single message like the original version.
- error property to get socket error.
eBuddy has opened up registration for people wanting to test upcoming versions of eBuddy Web and eBuddy Mobile. The first group of testers for the “Early Bird” beta will be strictly limited, so if you are interested, get in now!
The popular Web Messenger has been rewritten from the group up to improve ease of use and performance (the current version often gives me browser lag).
From what I’ve read, one of the obvious changes will be that you can login to WLM, Yahoo! and AIM all at the same time from within one application (which most other multi-network Web messengers already support), as opposed to the current setup which uses separate browser windows for each IM network.
If you’ve been getting errors when trying to sign in for the last few hours, it may be because of some service downtime. The service status page is reporting temporarily experiencing difficulty.
Sign In
The .NET Messenger Service is temporarily experiencing difficulty. You may be unable to sign in. Please try again later.
Last Update: 4/12/2007 3:00:00 PM Pacific Time (GMT -8:00)
As it says, just try again later. It doesn’t appear to be very widespread, I’m having no problems signing in and have the usual number of contacts online. But, traffic to this Web site has increased a little, so there’s definitely something going on.
Last September the same problem could be solved by changing the server which Messenger connects to, I’ve just tested it and it still works.
Update: Looks like I posted this shortly after the problem had already started to come right, I even missed the acknowledgment from Nicole at the Windows Live Messenger blog.
Within the last 12 hours Microsoft has started blocking all messages that link to YouTube. Messages are not received and the sender gets the dreaded “The following message could not be delivered to all recipients” error.