Take the 2-minute tour ×
Server Fault is a question and answer site for professional system and network administrators. It's 100% free, no registration required.

Our Setup

External email arrives at a Postfix server, is scanned, and then forwarded via settings in transport (using the RELAY:[{ip-address}] for a given address) to an Exchange 2007 server. Some users are on Exchange, but a few are still on the Postfix server (they will be moved in the near future).

IMAPS is provided for external connections via Dovecot; in-house, IMAP is provided for the Gateway and native MAPI is used for Exchange/Outlook. Blackberries are connected via BIS, which uses Dovecot as a reverse-proxy IMAPS service to connect to Exchange (when the mailbox exists on Exchange, otherwise it connects to the mailbox on the gateway).

The Issue

We have a user that, when they forward an email on their Outlook client, they get a duplicate of the original message on their Blackberry. When I say duplicate, I mean that they have a copy of the forwarded version of the message (i.e. their version of the message that they obtained hitting the forward button), and a copy of the original message that shows up at the same time.

The expected behavior is to just see the forwarded message, not the forwarded message and a 2nd copy of the original message.

We've only seen this with Outlook users that also have a Blackberry. Other IMAP clients, such as OS X Mail or Thunderbird, do not exhibit this behavior when connecting to the Exchange server; forwarded messages work as expected.

The Questions

  • what is causing this to happen?
  • why does it only affect Outlook/Blackberry setups, and not TBird/Blackberry or OSX-Mail/Blackberry?
  • how do we get it to stop, before people go insane and never forward messages again?
share|improve this question
    
Apparently, this question/topic is where all other questions go to die a slow, lonely death...6 months later and not a single bite... –  Avery Payne Apr 28 '10 at 1:44
1  
Go Go Tumbleweed!! –  Holocryptic May 11 '10 at 21:52

1 Answer 1

up vote 0 down vote accepted

Apparently this was an issue with Blackberry's BIS servers. The symptoms have disappeared after a recent service upgrade.

share|improve this answer

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.