CiviCRM Community Forums (archive)

I just set up email-to-activity processing and it's working - perhaps a little *too* well.

I have an account crm /at/ mydomain.tld that users should cc: or bcc: so that the e-mail gets recorded as a CiviCRM activity. I expected that this would create an activity between the originator and the "main" recipient (and it does). However, it also creates a contact record for the crm /at/ mydomain.tld email address and associates an activity between the main recipient and the email-to-activity email address.

Is this as designed, or a "side-effect"? To my thinking, the EmailProcessor. php script should *NOT* create an activity for the address used for email-to-activity processing (you could potentially end up with THOUSANDS of activities in your database).

I guess it would not do this if I were polling an IMAP folder in each user's mailbox, but that would mean that I'd have to set up each new user in CiviMail with an email-to-activity configuration, and have user names and passwords stored. This setup will fall apart when passwords expire. It's also much easier to explain to users to just cc: an e-mail address than have them file an extra copy of the message.