Page MenuHomePhabricator

Scheduled Reminder sent from donate@ email address?
Closed, ResolvedPublic

Description

Hi,

Caitlin V, Jonathan and I received a Scheduled Reminder - General Reminder from Civi this am. Yay, this is good news. However. the reminder was sent to us from the donate@wikimedia.org email address and not from my email address. I did setup up a lot of scheduled reminders yesterday and wondered if I've done something wrong somewhere along the way. Here's the screenshot of what we received -

Screen_Shot_2015-04-09_at_9.14.55_AM.png (287×740 px, 32 KB)

Here's the link the the Scheduled Reminders I've created so far for you to look at:

https://civicrm.wikimedia.org/civicrm/admin/scheduleReminders?reset=1

I noticed for the General Reminder rule I created I hadn't included any details in the subject of the email, which I have since added in to give more context to the reminder.

I also wondered if this reminder was one we setup on the staging version of Civi, is there anyway to tell?

Let me know if you need any further details from me.

Event Timeline

RLewis assigned this task to atgo.
RLewis raised the priority of this task from to Needs Triage.
RLewis updated the task description. (Show Details)
RLewis added subscribers: RLewis, CaitVirtue, awight, Ejegg.

Hey @RLewis - I'm not sure what the problem is here. What's the rationale for wanting the email sent from your email address instead of donate@?

Hey @atgo - we just assumed the reminder would come from the email address of whoever created the activity/reminder in Civi i.e. myself, Jonathan or Caitlin V as this is what has happened previously. It just seemed a bit weird to come from the donate@ email address since this isn't an email address that would have been associated with any contact records in Civi.

If this is the way it setup thats fine, we just wanted to check something was wrong here as it seemed odd to us to receive the reminder from the donate@ email address.

atgo subscribed.
Eileenmcnaughton claimed this task.
Eileenmcnaughton subscribed.

I think this is fixed by now