CiviCRM Community Forums (archive)

Are you sure you’re actually sending out the mailings? By default, the CiviMail wizards schedules the mailings, but does not send them; the activities are created upon actual sending of the mailing.

Please check the CiviMail menu to see the status of your mailing (whether it’s Scheduled or Complete).

Yes the mailings are being sent. These ones get sent to a couple test users and do go through (had to wrestle with cron for a bit, but it's working now). The status is Complete

I assume ‘test users’ here do not mean the users targeted in the ‘Test Mailing’ step (as these emails are not turned into activities), but rather that the mailing is seen as ‘legitimate’ by CiviMail and only you consider it ‘a test’.

If so, can you test more or less the same conditions on our demo server and see whether it’s something specific to your configuration? (In my tests the mailings do get recorded, so it’s a bit hard to reproduce…)

Just confirming that civiMail are not being listed on the recipient or the senders Activities on our 2.0 set up.
The Test Mailings do show up on both the sender and the recipients Activities.
Emails sent through 'More Actions' do show up on both.

We, too, have noted this issue in one of our client's implementations.

I've tested the use case on the Drupal Demo site and was able to send the both test messages and a final message and have the activites logged against the relevant contacts.

However, in our production environment, only the test messages are logged as activities.

Currently, our production environment is using CiviCRM 2.0.5 and we are using a remote SMTP server, with authentication enabled.

I'm still investigating the differences between our configuration and that of the demo site, but can confirm that this issue is affecting us as well.

If I can provide any further details, please let me know.

No, to both questions.

Don't know then.

What I experienced is that the cron job somehow didn't find the contact.

Try running the cron job by hand, with the debug parameter, might get more info

X+

I fixed this by using the (newly-introduced on trunk, i.e., CiviCRM 2.2) field of civicrm_mailing.scheduled_id, so it’s not backportable to CiviCRM 2.1.

Let me know if you have a better idea on how to fix it for CiviCRM 2.1 (the problem is that we have to set civicrm_activity.source_contact_id to something).