Using Microsoft Outlook 2010 with BPOS without local *.ost file.

Install Microsoft Outlook 2010, after installing don’t start Microsoft Outlook 2010, first create a mail profile in Start > Control Panel > Mail

Follow the steps on to manually connect Microsoft Outlook 2010 to BPOS.


Except for the screen below: Uncheck [Use Cached Exchange Mode]



How to send an executable as an E-mail attachment with BPOS

Out of the box sending executables as attachments with BPOS is not possible. BPOS will replace the executable with a *.txt file that contains the text:


Microsoft Online has removed winmail.dat->Unnamed Attachment->YoureApplication.exe since it
was found to match the FILE FILTER= unnamed: *.exe file filter.

Even if you zip or rar the file and rename the file extension, BPOS will replace the executable in the zip or RAR file with the txt file.

To prevent BPOS from removing the executable you can ask you administrator to edit the FILE FILTER rule or you can follow the steps below:

  • Zip the executable file
  • Open the zip file with a hexeditor (I use Notepad++ with the HexEditor.dll plugin)
  • Change the first 2 letters “PK” to some other letters, for example “LL”
  • Save the zip file
  • Send it to the customer
  • Customer must open the zip file with a hexeditor
  • Change the first 2 letters “LL” back to “PK” and save the zip file
  • Then the customer can extract the zip file and use the “YoureApplication.exe”