We use a hub transport rule to automatically append a corporate signature to all outbound emails.
Certain values are pulled from staff AD profiles and imported into the appropriate section of dynamic signatures when emails are sent. This works perfectly for us at the moment but I am running into an issue when trying to add an extra value which, unlike the phone numbers already in the dynamic signature, does not apply to everyone (mobile numbers).
Up until now, we have included two phone numbers in signatures: the office number (preceded by a "p." prefix) and fax number (preceded with a "f." prefix). These numbers existed for absolutely everyone in AD - so there was no issue with blank AD fields leaving a prefix that was not followed by a value.
Now, if I add "mobile" as an additional field in our corporate signature, any users who do not have a mobile phone are left with the prefix "m." (example below)
John Doe p. 123-456-7890 f. 123-456-7890 m.
Is there any way that I can make our hub transport rule smart enough that it does not include a particular prefix if there is no corresponding AD value for a given user?