# DOI Confirmation e-mail not sent

**URL:** <https://forum.mautic.org/t/doi-confirmation-e-mail-not-sent/28995>\
**Category:** Product Support\
**Created:** [August 19, 2023, 4:13am UTC](https://forum.mautic.org/t/doi-confirmation-e-mail-not-sent/28995 "2023-08-19T04:13:28Z")\
**Posts on this page:** 13\
**Page:** 1

<div class="post-metadata">

**Author:** ![dm\_michael](https://avatars.discourse-cdn.com/v4/letter/d/7feea3/32.png) [@dm\_michael](https://forum.mautic.org/u/dm_michael)\
**Post date:** [August 19, 2023, 4:13am UTC](https://forum.mautic.org/t/doi-confirmation-e-mail-not-sent/28995/1 "2023-08-19T04:13:28Z")

</div>

**Your software**  
My Mautic version is: 4.4.9  
My PHP version is: 7.4.3  
My Database type and version is: mySQL 5.7.25

**Your problem**  
My problem is:

I have created a very simple Double Opt in campain. Registratration form, confirmation e-mail, confirmation page are set up. Campaing workflow too.

User enters data  
check if user e-mail is already in database  
if yes - stop  
if no - send confirmation mail  
then proceed to add contact to segment  
then end

very simple.

Entering the user details goes fine, data is also transfered to Mautic and contact put into the right segment. BUT no confirmation e-mail is sent. (Sending a test mail to the address works fine)

These errors are showing in the log: No errors show up

Steps I have tried to fix the problem: Set up a super simple DOI workflow, but had the same result.

---

<div class="post-metadata">

**Author:** ![EJL](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.mautic.org/ejl/32/12155_2.png) [@EJL](https://forum.mautic.org/u/EJL)\
**Post date:** [August 19, 2023, 1:29pm UTC](https://forum.mautic.org/t/doi-confirmation-e-mail-not-sent/28995/2 "2023-08-19T13:29:44Z")

</div>

Check your var/spool folder to see if the email is still in queue.

Do you have the appropriate cron jobs tested and enabled?

If the emails are queued use **… /bin/console swiftmailer:spool:send --message-limit=1 --time-limit=10 --recover-timeout=900 --mailer=default**

to send from queue to test.

---

<div class="post-metadata">

**Author:** ![dm\_michael](https://avatars.discourse-cdn.com/v4/letter/d/7feea3/32.png) [@dm\_michael](https://forum.mautic.org/u/dm_michael)\
**Post date:** [August 21, 2023, 5:38am UTC](https://forum.mautic.org/t/doi-confirmation-e-mail-not-sent/28995/3 "2023-08-21T05:38:18Z")

</div>

Where do I find this folder in the backend? Or do I have to look elsewhere?

---

<div class="post-metadata">

**Author:** ![robm](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.mautic.org/robm/32/260_2.png) [@robm](https://forum.mautic.org/u/robm)\
**Post date:** [August 21, 2023, 11:00am UTC](https://forum.mautic.org/t/doi-confirmation-e-mail-not-sent/28995/4 "2023-08-21T11:00:37Z")

</div>

spool folder is in the var folder

For me that path is /var/spool from root.

The cron is added via the cron interface which will vary depending on how yur hosting set up.

---

<div class="post-metadata">

**Author:** ![dm\_michael](https://avatars.discourse-cdn.com/v4/letter/d/7feea3/32.png) [@dm\_michael](https://forum.mautic.org/u/dm_michael)\
**Post date:** [August 21, 2023, 11:16am UTC](https://forum.mautic.org/t/doi-confirmation-e-mail-not-sent/28995/5 "2023-08-21T11:16:13Z")

</div>

Found it, thanks.

Folder is empty.

Cron jobs are enabled via the hoster:

Mautic Segment update: every 5 minutes  
Mautic Campaign update: every 15 minutes  
Mautic Campaign Trigger Cronjob: every 5 minutes

---

<div class="post-metadata">

**Author:** ![EJL](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.mautic.org/ejl/32/12155_2.png) [@EJL](https://forum.mautic.org/u/EJL)\
**Post date:** [August 21, 2023, 1:57pm UTC](https://forum.mautic.org/t/doi-confirmation-e-mail-not-sent/28995/6 "2023-08-21T13:57:34Z")

</div>

Need to setup your crons to actually process and send your emails. [Cron jobs | Mautic](https://docs.mautic.org/en/setup/cron-jobs#process-email-queue)

---

<div class="post-metadata">

**Author:** ![dm\_michael](https://avatars.discourse-cdn.com/v4/letter/d/7feea3/32.png) [@dm\_michael](https://forum.mautic.org/u/dm_michael)\
**Post date:** [August 28, 2023, 4:16am UTC](https://forum.mautic.org/t/doi-confirmation-e-mail-not-sent/28995/7 "2023-08-28T04:16:26Z")

</div>

I think here is where the problem lies…

I have set up the cron jobs via my hoster and

- **mautic:campaigns:update**

- **mautic:campaigns:trigger**  
seem to work but. (Because mails are sent out)

- mautic:segments:update  
doesnt.

Although if I start the cronjob manually, it works fine and the segment is updated.

The cronjob is set to run every 10 minutes.

Mautic error log does not give me any information. Webhoster error log also not. Support cannot help me here.

I have set the cronjob to run via URL (SSL / https).

Anyone has an idea what to look for?

---

<div class="post-metadata">

**Author:** ![robm](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.mautic.org/robm/32/260_2.png) [@robm](https://forum.mautic.org/u/robm)\
**Post date:** [August 28, 2023, 10:38am UTC](https://forum.mautic.org/t/doi-confirmation-e-mail-not-sent/28995/8 "2023-08-28T10:38:15Z")

</div>

Compare the full path and command for the crons that are working with the ones that are not and look for differences. I can only think there has been a mistake in how the segment cron has been loaded.

---

<div class="post-metadata">

**Author:** ![dm\_michael](https://avatars.discourse-cdn.com/v4/letter/d/7feea3/32.png) [@dm\_michael](https://forum.mautic.org/u/dm_michael)\
**Post date:** [August 28, 2023, 10:59am UTC](https://forum.mautic.org/t/doi-confirmation-e-mail-not-sent/28995/9 "2023-08-28T10:59:45Z")

</div>

Just did… all identical but the command.

Another thing that came to my mind… could it be that the segment is somehow faulty? I have imported my contacts from another newsletter tool and maybe there ist something wrong here…?

Any way to check the data in the contacts list?

---

<div class="post-metadata">

**Author:** ![robm](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.mautic.org/robm/32/260_2.png) [@robm](https://forum.mautic.org/u/robm)\
**Post date:** [August 28, 2023, 2:06pm UTC](https://forum.mautic.org/t/doi-confirmation-e-mail-not-sent/28995/10 "2023-08-28T14:06:11Z")

</div>

If the segment is updating as expected when you run cron’s manually then I suspect your segment is fine. But to double check create a new segment, apply a filter and see if the new segment updates when the crons fire on schedule. That way you can test if the segment ofthe imported contats is the issue or some deeper system issue.

---

<div class="post-metadata">

**Author:** ![dm\_michael](https://avatars.discourse-cdn.com/v4/letter/d/7feea3/32.png) [@dm\_michael](https://forum.mautic.org/u/dm_michael)\
**Post date:** [August 28, 2023, 2:27pm UTC](https://forum.mautic.org/t/doi-confirmation-e-mail-not-sent/28995/11 "2023-08-28T14:27:30Z")

</div>

That is exactly what I am doing right now. Created a second segment with just a few contacts. Looking forward to see if the cron is working on that one.

---

<div class="post-metadata">

**Author:** ![dm\_michael](https://avatars.discourse-cdn.com/v4/letter/d/7feea3/32.png) [@dm\_michael](https://forum.mautic.org/u/dm_michael)\
**Post date:** [August 29, 2023, 4:37pm UTC](https://forum.mautic.org/t/doi-confirmation-e-mail-not-sent/28995/12 "2023-08-29T16:37:40Z")

</div>

OK same result. The segment cannot be updated. Means the cron job is not working. Whatever reason there is. The other cron jobs are working.

---

<div class="post-metadata">

**Author:** ![EJL](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.mautic.org/ejl/32/12155_2.png) [@EJL](https://forum.mautic.org/u/EJL)\
**Post date:** [October 3, 2023, 2:42pm UTC](https://forum.mautic.org/t/doi-confirmation-e-mail-not-sent/28995/13 "2023-10-03T14:42:44Z")

</div>

> [@dm\_michael](#):
>
> mautic:campaigns:update

Try mautic:campaigns:rebuild command  
If that doesn’t work double check the filters within the segment to make sure they are correct. Sometimes disabling the segment and re-enable with “unstick” a “stuck” segment
