Multiple Signatures on Exchange/Outlook 365 with multiple connected pop3 accounts wanting sepearate signatures

Question

I was referred here from another thread, see
http://community.office365.com/en-us/f/158/p/245124/778388.aspx#778388but not sure if this is the right forum, so please move/correct my posting if needed!
It's a exchange/Outlook365 query, relating to signatures
I have several connected pop3 accounts to the exchange mailbox, but there appears to be no way to have separate signatures for each connected account, in fact there appears to be only 1 signature for the entire account? So when I send emails I can select
from several different from addresses, but the signature remains the same ...
On desktop outlook 2003-2010 at least, there is the ability to have default reply, default new message signatures for each account in use, is there a way to configure the exchange/outlook365 OWA to do this ?
I'm about to test if an outlook 2010 desktop client allows/recognises the server side linked accounts and allows email to be sent from them, so any tips or points on that would be welcome!
thanks

Answer 1

In Outlook2010 you can set multiple signatures, yes.
If you connect to those accounts LOCALLY using POP3 you can also then set defaults for each account ... HOWEVER
if you set the CONNECTED ACCOUNTS via OUTLOOK365 via the cloud server, the local Outlook will not let you set default signatures for each account. Yes you can have signatures and manually select them, but that's not the same thing, and leads to mistakes.
The whole point of connecting the accounts via the Cloud is that the local PC is then no longer part of the critical path when away from the office, so if the local PC crashed or lost internet, then it would not affect mail delivery to the single exchange
mailbox, for access via the web or mobile devices. Quite important. A common failure we have on local outlook pop3 connections is a single password failure to login, leaves the pop up menu on screen and then stops all other pop3 mail collection from working.
We have tried for 2+ years to solve this "password failure popup", but as the passwords are saved and don't change and the problem persists, we wanted to move to the cloud ... and avoid problems when users are away.
Last but not least, if using the cloud to send a reply to a mail via a connected account, the email is not sent as the connected account (despite it being validated for send as) but sent using a "<exchange Primary email> send on behalf of <pop3
connected email>" which defeats to whole point of connecting the accounts and verifying them!
I've got to say when even Google can get this right! why can't Microsoft? It really does suck!
For a business class product having 1 signature per user within OWA is seriously deficient.
Maybe time to move our email needs to Google, as on searching the depths of old archives it does appear these issues have been raised for several years, yet nothing has improved ... shame on Microsoft.