To verify the validity of an SPF record installed for a domain, go here:
put the domain in the form for “Does my domain already have an SPF record? What is it? Is it valid?”, and submit. This will detect many issues, including issues which the syntax checker further down does not catch.
To do a deep study of a bounceback, the best tool this writer has ever seen is here:
in the Message Analyzer tab. Just paste every header you have into there and submit, and then read. Lots and lots of excellent information comes up.
Best information is now here for Windows and other software firewalls:
There is a link in the above for “whitelisting information” which really has the skinny for hardware firewalls:
This method copies an entire mailbox, including all folder structure.
First of all, if it has not been done before, we need to set up permissions for a primary EOL admin user, to be able to use Search-Mailbox. At this writing, it does not come by default to EOL administrators, and is not even available as a visible role in the EOL permissions console, until the below was done. Here is what was necessary, because a user cannot elevate itself:
- Give a second user the administrative role, using the EOL console
- Connect PowerShell to EOL by the second user
- Prepare the EOL organization for the next step:
- Run the following using the PowerShell connection:
New-RoleGroup -Name "Exchange Mailbox Import Export" -Roles "Mailbox Import Export" -Members firstname.lastname@example.org -DisplayName "Exchange Mailbox Import Export"
- Next we need to give the same primary admin user, the “Discovery Management” role. For this we do go into the Exchange Online administrative area, under Permissions, and add the primary admin to the “Discovery Management” role.
Now that permissions have been established, we can do the job:
- Close the above PowerShell instance entirely, because it is not using the proper user
- Start up a new one connected as the primary admin
- Run the below:
Search-Mailbox -Identity email@example.com -TargetMailbox firstname.lastname@example.org -TargetFolder "Copied from mailbox_to_be_copied"
If EOL is working well when you start this, it will run until complete, it may take quite a while though. It will make a copy of mailbox_to_be_copied underneath a folder it will create within destination_mailbox, called “Copied from mailbox_to_be_copied”.
And don’t forget to delete or revert the secondary admin afterwards!
The amazing David Lewis recently discovered something very close to unbelievable. A user profile on a PC — not a user, not a PC — had full administrative rights to a folder on a server on the domain, where the user was explicitly denied such rights. Deletion and replacement of the user profile, eliminated the problem.
Today I found it ridiculously difficult to download IE11 on a Windows 7 box which had not seen updates in a while. If you suffer so, browse here:
Offline installers in many languages.
Rather a neat tool:
Can eliminate a lot of issues in Explorer.
There are many situations in which a recent version of Excel will report that there is not enough available memory or disk space, where there very clearly is. To knock this one out, go to File menu and Options, click Trust Center on the left, click Trust Center Settings… on the right, and then Protected View on the left. Uncheck everything in there, and OK all the way out. Close Excel and try it again. Problem eliminated.
This is a new one, both Windows and Linux. Based on Chromium, the core of Chrome. Amazingly fast and efficient. Includes recent Adobe Flash, in both 32-bit and 64-bit. This is very probably the fastest and most efficient 32-bit browser with Flash in the world right now.
There is a lot of talk about this on the wild Web. This situation occurs because some instances of Microsoft SQL default to “FULL” logging mode, and this can be very helpful because if there is a crash, the database can be restored to the very transactional instant of the crash. In “FULL” logging mode, the LDF file keeps on piling up until an SQL-aware system backup is performed, at which time the LDF is pared down automatically.
But there are many SQL databases out there where we don’t care about transaction-level restore, where the backup is system image-wide and we are very happy with that level of restoration. In this case, “FULL” logging mode is very wasteful, because since the backup is not SQL-aware, the LDF file keeps on piling and piling, taking many gigabytes of disk space.
For these we want “SIMPLE” logging mode. To set this up, log into SQL Studio using an appropriately high-privileged user, and run this query substituting database_name appropriately:
ALTER DATABASE database_name SET RECOVERY SIMPLE ;
Two things are accomplished by the above. First, the LDF will quit piling. Second, a CHECKPOINT was done, which tells SQL Studio immediately that most of the space in the huge LDF is wasted. This means that you can tell SQL Studio to shrink the LDF, eliminating the wasted space, like this:
- In Databases, right-click on the database whose LDF needs shrinking
- Click Tasks —> Shrink —> Files.
- In File type, choose Log.
- Make sure “Release unused space” is selected. The other numbers will make it obvious how much space you are freeing up. If they’re not good, you have something else wrong or undone!
- Click OK. The shrinkage will begin. Depending on how much is to be done, it may take a while, but the progression will show up in free disk space recorded in CMD.