@bsetter iPad is in the works and desktop is on our roadmap!—
Mailbox (@mailbox) April 25, 2013

After some controversy for the popular Mailbox iOS app earlier this week, some good news for Mailbox users comes today in the form of confirmation of new features and an iPad app coming soon.

As noted in the tweets above and below, the Mailbox devs have publicly confirmed in a number of recent tweets that and iPad version of the app is currently “in the works” and expected to launch soon. We also learn that desktop and Android versions of the app are on the company’s roadmap, while iCloud support, landscape typing, alias support, and “Send as” features are also on the list for future updates:

@mkmks Yes! Alias support & "send as" are on our list. No ETA for release as of yet.—
Mailbox (@mailbox) April 25, 2013

@herbigt Yes- we're hoping to do so in a future update!—
Mailbox (@mailbox) April 25, 2013

@bsetter iPad is in the works and desktop is on our roadmap!—
Mailbox (@mailbox) April 25, 2013

(via TechCrunch)

Import-Csv E:\mbx.csv | foreach {Search-Mailbox -identity ($_.users) -SearchQuery “Sent:> $(’2013-03-31′) and Sent:< $(’2013-04-03′) and from:’Accounts@mydomain.com’” -TargetMailbox “administrator” -TargetFolder “search” -LogOnly -LogLevel full} | ft Identity, Resultitemscount

Here accounts@mydomain.com is the shared mailbox.

Note: Users should not move/delete their mails from sent items.

GOOD For Enterprise have now outlined a permanent fix for this issue.

Using the following fix will re-instate the Send As permissions for the required user accounts that the GOOD app uses to remotely send emails from their handheld apps, therefore eliminating the need to go through the workaround which I had outlined in my previous post.

The Permanent Fix

In order to achieve a permanent fix for this issue we need to re-instate the Send As ability that the required user accounts had before a certain Windows update removed this right, this is done using the DSACLS utility.

The syntax for the correct command is as follows:

dsacls "cn=adminsdholder,cn=system,dc=domainname,dc=com" /G "\GoodAdmin:CA;Send As"

Please be sure to update the dc values to match your specific domain name.

For example, if your domain name is company.local the command would then become:

dsacls "cn=adminsdholder,cn=system,dc=<strong>company</strong>,dc=<strong>local</strong>" /G "\GoodAdmin:CA;Send As"

Hope this help you guys out.

This behavior is not really good, if more people have to access this mailbox and want to have access to every mail sent with this user. Unfortunately there are no options to manage this with the Exchange Server. To change this behavior you have to do the following steps directly on the client computer:

1. Open the Registry editor by typing “Windows key + R” and then enter “regedit”. If you asked about admin premissions, klick on yes or type your username and password in it.
2. Change into this directory: “HKEY_CURRENT_USER\Software\Microsoft\Office\14.0\Outlook\Preferences”
3. In this directory do a right click and add a new DWORD.
4. Name the new DWORD “DelegateSentItemsStyle”.
5. Double click on the new DWORD and set the Value to “1″. Make sure, that you have choosen hexadecimal values.
6. If not already done: close Outlook.
7. Open Outlook again

Now, if you send a mail with your other mailbox, your mails should be saved in the right sent items folder.

Adding Send-As permissions to a user is usually a straight forward task in Exchange. But finding all the Send-As permissions a user has on all the mailboxes in the organization is a different story.

In this article we will discuss how to find all the Send-As permissions a user has on all the mailboxes in the environment. And then removing all these permissions. Of course PowerShell will come in handy to achieve these goals. (And by PowerShell I mean the Exchange Management Shell, EMS)

The first step will be to find the permissions the user has on all the mailboxes.

$SendAsPermissions = Get-Mailbox | Get-ADPermission | Where-Object {($_.ExtendedRights -like “Send-As”) -and ($_.User –Like “Contoso\Kim.Akers”)}

In this command we used the Get-Mailbox without any parameters to get all the mailboxes then piped them to the Get-ADPermission cmdlet that returns all the permissions on a mailbox then we piped all the information to the Where-Object cmdlet in order to filter the output by the Send-As permissions where the user is Kim Akers who is the user that we querying the information about. Finally we created a variable $SendAsPermissions to store the data.

Running this command WILL take a long time to complete in a larger environment, so you may want to prepare yourself to wait for a while before it’s done.

You may want to run a command that shows you what permissions where found,

$SendAsPermissions | FL Identity, User, ExtendedRights

And the output should be something like that,

Identity : Contoso.local/Users/Don Hall
User : CONTOSO\Kim.Akers
ExtendedRights : {Send-As}
.
Identity : Contoso.local/Users/Delilah Edward
User : CONTOSO\Kim.Akers
ExtendedRights : {Send-As}

As you see, the results shows that Kim Akers has Send-As permissions on two users, Don Hall and Delilah Edward.

Now the next step is to remove the permissions and stop Kim Akers from being able to send as Don or Delilah.

$SendAsPermissions | Remove-ADPermission -Confirm:$False

In this command we piped the data in our variable into the Remove-ADPermission cmdlet that removed the permissions applied, the Confirm switch makes sure we don’t have to confirm the removal of each and every entry.

There will be no output if everything runs smoothly! So you may want to run the first command again (and expect no output too!) to check the successfulness of removal or check them manually from the EMC.

You may notice that there was no technical need for the second step, but knowing what you are deleting is usually a good idea.

This concludes our article, credit goes to Rajith Jose Enchiparambil for his article as it gave me the idea for this one.

There are 3 primary tasks that must be performed post-transition (with some pre-transition preparation recommended).

1. Send-As perissions for Distribution Lists must be restored.
Due to the difference in how permissions are stored for Distribution Lists between Exchange 2007 and Exchange 2010, these permissions are dropped during the transition process. It is recommended to submit a Service Request to the Support team to get an export of these permissions prior to transition (this can be done post-transition as well, if necessary). Once you have transitioned, and have access back to your tenant with Administrative permissions, you can then set the permissions as necessary to the Distribution Lists in Office 365.

2. Send on Behalf of permissions will need to be backed up and restored.
If you are planning to run Directory Synchronization for Office 365, you will need to back up your ‘Send on Behalf of’ permissions prior to running DirSync for the first time, and then restore them after running DirSync. The reason for this is that one of the new AD attributes synced by the Office 365 Directory Sync tool (DirSync v2) is publicDelegates, which is directly responsible for keeping track of this permission set. This does not affect FullAccess or SendAs permission; those should transition successfully and not have any problems. Prior to running DirSync v2, the permissions will function successfully as all AD attributes in BPOS will transition successfully to Office 365. When DirSync v2 is run for the first time (and any Full Sync performed afterwards) it will replace the O365 AD attributes with the attributes on-premises. If you have expanded your AD schema for Excange you will have the publicDelegates attribute (if you have not extended your schema, you do not have to worry about this).

3. Proxy Addresses must be copied to AD.
In BPOS, Directory Sync (DirSync v1) does not update mailbox-enabled user objects’ proxyAddresses attribute once it has been assigned a license (and thus a mailbox). As such, most customers have taken the habit of adding proxy addresses to their BPOS users without adding them on-premises as well. Immediately post-transition, the proxy addresses will be available with no detriment to the users, however, once DirSync v2 has been run, it will overwrite the proxyAddresses attribute and remove any proxy addresses that are not in your on-premises AD (if you have not extended your AD schema for Exchange on-premises, you will not have to worry about this).

Google just updated the Gmail iOS app with a number of new features. Perhaps the most notable is that Notification Center support provides users with banners, alerts, and lock screen notification options that are manageable from settings. Google also noted on the Official Gmail Blog that notifications in the updated app are “up to 5x faster than in the previous version.”

Another new feature is a “From:” option when composing a new message. It allows you to switch between sender addresses under Settings->Accounts->Send mail as from Gmail on the desktop. Finally, Google explained the improved “persistent logins” would allow you to stay logged in as long as you want:

“we’ve improved the login process to allow you to stay logged into the app for as long as you’d like. You can still choose to sign out of your account, but you won’t be automatically logged out after a certain period of time has elapsed.”

What’s New in Version 1.2.7812

- Notification Center support. Banners, alerts and lock screen notification options.
- “Send-as”. Alternate sender support, if configured within Gmail.
- Persistent login. Sessions no longer expire.

Related articles

• Google doesn’t plan to leave iOS Maps users without a fight (9to5google.com)
• After getting booted from Maps.app, Google is plotting their own amazing iOS Maps experience (9to5mac.com)
• Facebook working on ‘major update’ to its SDK for iOS, acquires Face.com (9to5mac.com)

This tutorial from Specialist John will show you how to set this up – including a handy tip that goes above and beyond the usual config to ensure that on Microsoft Outlook you don’t get those annoying “on behalf of” messages when you send from your second email address. i.e. if you want to be able to send from your old ISP email address, Outlook will display it as “From john@yourcloudspecialist.com on behalf of cleary@iinet.net.au”. This tip solves that problem!

This setup is perfect for when you’ve got a couple of different email addresses that you need to be able to send from but want to manage it in one inbox / sent box. You can use this tip to have more than one domain on your Google Apps account too – i.e. if you have a personal domain and business domain you can set up to be able to send from either without having to set up multiple accounts on your computer each time.

Set up Google Apps / Gmail to be able to send from another email address you own

Hope this tutorial has been helpful. If you have any questions, feel free to ask away in the comments!

Google has just started rolling out an update to the Gmail app for iPhone, iPad, and iPod touch with a few new welcomed features. First off, users now have the ability to set a custom signature for messages as well as a vacation responder. Both of those new features will be available via the gear icon at the top of the app’s new menu. The update also includes support for nested labels and the usual “bug fixes and UI improvements”.

A new Scribbles feature allows you to open a canvas, draw a picture or sketch with multiple colors, brush sizes and line elements, and attach it to a message within Gmail. Scribbles is available now in both the Gmail iOS app and Gmail mobile web app. Another notable and highly requested change is a new notification sound on iOS 5, making it easier to tell when you’ve received an email

Google also mentioned in their blog post that they are continuing to work on some of the most requested features from users including multiple login support, banner notifications, and a “send as” feature to mail send mail from multiple accounts within the app.

Cross-posted on 9to5Mac.com

Google has just started rolling out an update to the Gmail app for iPhone, iPad, and iPod touch with a few new welcomed features. First off, users now have the ability to set a custom signature for messages as well as a vacation responder. Both of those new features will be available via the gear icon at the top of the app’s new menu. The update also includes support for nested labels and the usual “bug fixes and UI improvements”.

A new Scribbles feature allows you to open a canvas, draw a picture or sketch with multiple colors, brush sizes and line elements, and attach it to a message within Gmail. Scribbles is available now in both the Gmail iOS app and Gmail mobile web app. Another notable and highly requested change is a new notification sound on iOS 5, making it easier to tell when you’ve received an email

Google also mentioned in their blog post that they are continuing to work on some of the most requested features from users including multiple login support, banner notifications, and a “send as” feature to send mail from multiple accounts within the app.

Cross-posted on 9to5Google.com

First, I verified the user did not have the rights about to be assigned.

Get-Mailboxdatabase -Identity DBIdentity | Get-ADPermission -User SERVICEACCOUNT

I did not receive any results from the above cmdlet.

Next, I added the permissions to the database for the service account.

Get-Mailboxdatabase -Identity DBIdentity | Add-ADPermission -User SERVICEACCOUNT -AccessRights ExtendedRight -ExtendedRights receive-as, send-as

Once I issued that command, I verified they applied successfully by running the get-adpermission command again.

This worked for me but I cannot guarantee it will work for others.

Exchange has many options but some of them are more popular or usable for the day-to-day management. I want to go over some of them and will start with Send-As.

Send-As is a feature that allow userA to send emails for UserB where the recipient doesn’t know that UserB did not send the mail. A good use case would be a secretary that send emails or appointment invitations for her boss.

In the management console open the Recipient Configuration-> Mailbox-> mailbox_name-> right-click and choose Manage Send As Permission.

If you want to allow not only the Send As permission but full access to the mailbox (aka reading mail), use the Manage Full Access Permission.

Distribution and Security groups have an important role in Exchange (and Outlook). The difference between the types of groups is simple:

• Distribution groups is a group of objects from the Exchange database
• Security group uses both Exchange user database and Active Directory objects (and their AD permissions)

To create a group, in the management console open the Recipient Configuration-> Distribution Group->New Distribution Group option and choose the type of group to be created.

Tip: by default when you create a mail-enabled group they are disabled for out of the Exchange domain users (meaning Internet users cannot email the group). This is the shell way to enable outside users for these groups:

Set-distributiongroup GROUPNAME-RequireSenderAuthenticationEnabled $False

Mail-enabled contact is another useful feature. A mail-enabled user has an e-mail address at the organization but does not have an Exchange mailbox. All e-mail messages that are sent to the mail-enabled user are forwarded to the specified external e-mail address.

Check Part II of this post for more recipients management options.

Format ofthe CSV something like this

UserMailbox,User
Krishna,Domain/Krishna

———————————————————————————————————————-

$csv = Import-csv -path “C:\Userdetails.csv”
foreach($line in $csv)
{
Add-MailboxPermission $Line.UserMailbox -AccessRights FullAccess -user $Line.User
Add-ADPermission $Line.UserMailbox -Extendedrights “Send As” -User $Line.User

}

———————————————————————————————————————-