CiviCRM Community Forums (archive)

I wish to setup autofiling (http://wiki.civicrm.org/confluence/display/CRMDOC41/Autofiling+email+activities+via+EmailProcessor) on a CiviCRM 4.1.x site with CiviSMTP enabled. However, I'm not too clear about CiviSMTP limitations and what I need to do to have both of them play well together.

As far as I understand, CiviSMTP mainly manages outgoing mails, and it uses the soap api to notify civicrm of eventual bounces... I assume that CiviMail also processes incoming mail to deal with replies and (un)subscribes as long as the MX records are set up properly. Do we have access to this mailbox in any other way or do we need a different email account to support autofiling?

I'm also bit confused about how little information we need to fill up when creating a new Mail account from/civicrm/admin/mailSettings. My guess is that we shouldn't need to be calling the fetch_bounces job (or the now deprecated EmailProcessor.php) when using CiviSMTP; and the instructions for Mail Accounts in http://new.uas.coop/drupal/node/1#Step_3.2 are just a way of telling CiviCRM that it doesn't need to worry about that. Am I right to assume this?

Back to the original question : what about autofiling? Is it supported by CiviSMTP? If so, does it require additional permissions? Otherwise, would configuring CiviSMTP for "Bounce Processing", a second account for "Email-to-Activity processing", and calling a scheduled job (fetch_activities?) normally do the trick?

Just wanting to make sure I'm on the right track... or not.

Thanks!

i think the two processes are quite orthogonal and not related to each other

SMTP is focussed on delivering email and processing specific civimail responses (bounces, unsub, optouts etc)

the AutoFiling is more for inbound email, and hence reads a mail folder via POP/IMAP/Dir protocols and then creates activities for the email

lobo