Announcement

Collapse
No announcement yet.

Exch2010: Identify messages from BES

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • Exch2010: Identify messages from BES

    Slightly odd request!

    Is there an obvious way (header content possibly) of identifying emails which have come from the corporate BES (i.e. sent from local blackberry) to apply transport rules specific to them. I know a key word could be put into the subject but this relies on users.

    Exch 2010 SP1 (or it will be -- this is a client in the process of deployment)
    Tom Jones
    MCT, MCSE (2000:Security & 2003), MCSA:Security & Messaging, MCDBA, MCDST, MCITP(EA, EMA, SA, EDA, ES, CS), MCTS, MCP, Sec+
    PhD, MSc, FIAP, MIITT
    IT Trainer / Consultant
    Ossian Ltd
    Scotland

    ** Remember to give credit where credit is due and leave reputation points where appropriate **

  • #2
    Re: Exch2010: Identify messages from BES

    Use the signature feature of BES would be one way.
    My Blackberry has

    --
    Sent from my Blackberry, please excuse typos and abbreviations

    Which comes after any other signature.
    The users can't change that as it is server side applied. You could put anything you like in to the signature - and then use a replace rule to remove it.

    Simon.
    --
    Simon Butler
    Exchange MVP

    Blog: http://blog.sembee.co.uk/
    More Exchange Content: http://exchange.sembee.info/
    Exchange Resources List: http://exbpa.com/
    In the UK? Hire me: http://www.sembee.co.uk/

    Sembee is a registered trademark, used here with permission.

    Comment


    • #3
      Re: Exch2010: Identify messages from BES

      Good one!
      Thanks, Sembee
      Tom Jones
      MCT, MCSE (2000:Security & 2003), MCSA:Security & Messaging, MCDBA, MCDST, MCITP(EA, EMA, SA, EDA, ES, CS), MCTS, MCP, Sec+
      PhD, MSc, FIAP, MIITT
      IT Trainer / Consultant
      Ossian Ltd
      Scotland

      ** Remember to give credit where credit is due and leave reputation points where appropriate **

      Comment

      Working...
      X