Update 14-Oct-2010: We just added a further check to our system so if you sent the email from your Google Apps domain email address we will now correctly identify the message and user of BCC'ed messages.
On the 5th of October we upgraded our dropbox software that handles incoming emails to a new system. The change will allow us to better handle peak loads and the increase in emails sent as more customers sign up.
The new software is slightly different to the old system, but the only change visible to customers is when some email servers send email to Insightly via a blind carbon copy or BCC.
Insightly looks through the header information in the email to match the message to a users special dropbox email address when the message comes in, but some email servers do not add the addressee to the headers for BCC messages. In this case, the Insightly dropbox cannot identify which user the email is for and discards the email.
Google's Gmail servers add the header on BCC messages, and by far the majority of our users use Gmail. If you use Gmail for email no change is needed and your dropbox will continue to work great.
Yahoo email servers on the other hand do not append the addressee to the email headers on BCC messages, so if you use Yahoo email you will need to send emails to your dropbox by CC or by a Forward.
If you use another type of email server software it's best to test it yourself. Send out an email with your dropbox address in the BCC field and check Insightly twenty seconds later to see if that email appears in the email tab in Insightly. If it does: great - but if it does not, you may have to send future emails to Insightly with your dropbox email address in the CC field, or just forward messages to your dropbox as they come in.
Also, as always - if you use Gmail's auto-forward feature to forward every single email you get to your Insightly drop box we will not import them.
- ► 2014 (51)
- ► 2013 (42)
- ► 2012 (16)
- ► 2011 (25)