The Raaymakers Family

Consider the following. You have an Exchange 2003 environment. Users are getting the following message from the Exchange PostMaster account on meeting updates or meeting cancelations they sent to recipients outside your exchange organization.

Subject: Delivery Status Notification (Delay)

This is an automatically generated Delivery Status Notification.

THIS IS A WARNING MESSAGE ONLY.

YOU DO NOT NEED TO RESEND YOUR MESSAGE.

Delivery to the following recipients has been delayed.

       This e-mail address is being protected from spambots. You need JavaScript enabled to view it

       This e-mail address is being protected from spambots. You need JavaScript enabled to view it

All recipient addresses check good. You check the Outgoing SMTP Queue on the Exchange Server the users mailbox is hosted on and notice the users message is there with a red dot on the envelope icon indicating delivery has thus far failed and a retry is scheduled.

Normal messages and initial meeting requests go thru to the same outside recipients with no problem. The same outside recipients can accept the meeting request and the sender recieves the accept message.

Then after the meeting update or cancelation sent by the internal user expires in the queue the user will recieve the following NDR message from the system Administrator on the same meeting update or meeting cancelation they sent to recipients outside your exchange organization.

Subject: Undeliverable: Delivery Status Notification (Failure)

Your message did not reach some or all of the intended recipients.

      Subject:    [Subject of Message]

The following recipient(s) cannot be reached:

      This e-mail address is being protected from spambots. You need JavaScript enabled to view it  on 4/8/2010 8:48 AM

            Could not deliver the message in the time limit specified.  Please retry or contact your administrator.

      This e-mail address is being protected from spambots. You need JavaScript enabled to view it  on 4/8/2010 8:48 AM

            Could not deliver the message in the time limit specified.  Please retry or contact your administrator.

Check if the external recipients messaging system is Exchange 2007 or Exchange 2010. If so refer to this Microsoft Knowledgebase Article.

http://support.microsoft.com/kb/938650 

"A meeting update message or a meeting cancellation message from an Exchange 2003 user is not delivered to an Exchange 2007 user"

This will explain how I changed the Joomla Icon in the browsers address bar and page tab. 1st this works on Joomla 1.5 as it appears most templates use the admin favicon.ico.  

There are 2 websites where you can create an icon on line.

http://tools.dynamicdrive.com/favicon/

http://www.degraeve.com/favicon

After creating your icon, rename the current favicon.ico to faviconico.old in the //administrator/templates/Khepri directory then upload your new favicon.ico in it's place. That worked for me.

A copy of this is in my Forums for discussion....

I installed WUBI 9.10 on a Dell Inspiron 5100 32bit. Was running great till I updated it. After updating it booted to a SH:GRUB> prompt. I did some online research and found a series of commands to get booted into Ubuntu 9.10 then from a terminal window run >sudo update-grub2 which fixed the issue. The key for me was figuring out whether I was on sda, sda1 or sda2 and which version I was on. Checkout the below commands

sh:grub> linux /boot/vmlinuz-2.6.31-19-generic root=/dev/sda2 loop=/ubuntu/disks/root.disk ro
sh:grub> initrd /boot/initrd.img-2.6.31-19-generic
sh:grub> boot

After typing "sh:grub> linux /boot/vm" press the TAB key. You get a list of choices. Use the newest vmlinuz-x.xx-xx-generic. Do not use the TAB key for any of the other parts of the command, for example the root=. It will not give you a good list. I've BOLDED the only variables in these commands. The version and the sda?. Also note that in the "initrd" command the version must be the same.

Once you are booted into Ubuntu, open a terminal window and type "sudo update-grub2", press enter, type your root password, press enter again. If you do not see any errors you should be ok. Try to reboot and it should boot ok.

Thats what fixed it for me. Hope this helps for you too.

Here is the forum I found my fix on...

https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/477104 

James

Please read this MSNBC article on RansomeWare. This is malware that takes control of your computer and holds it ransome until you pay the author money for a license key. Even though you pay the criminal still has control of your computer and will hold it for ransome again. Whats worse is you would be giving your credit card number to a criminal. You get these RansomeWare programs from visting websites. To learn more about these very serious threats read the article by clicking the link above. Read all the comments too, as there is additional information from readers who have experienced the ransomeware themselves.

I learned this this last weekend. You have a Blacberry Enterprise Server in your Exchange 2003 environment. You have an Exchange Server with multiple Storage Groups and need to take a few mailstores offline for an extended amount of time. I would make sure the BES-ADMIN mailbox gets moved to a mailstore that is not going offline. If it is on one of the mailstores that is going offline, your BES will will not forward messages as it is unable to access the BES-ADMIN mailbox.  Your Application Event log will begin filling up with 10277 Errors from the Blackberry Messaging Agent saying "Blackberry Messaging Agent (ServerName) Agent 1 failed to start, Error code 5305"