olibre

Thank you @JanusBahsJacquet, I appreciate your improvements of the question wording. I will delete this comment later, once you have read it to avoid polluting this comments list. Cheers

bye bye

More skilled experts will answer to your accurate new question for sure

Maybe you will find another similar question on SO...

Yes, I think this a good idea.

This is grate you find some stuff in crond logs.

I am sorry I have no clue after that point...

I do not remember where PAM logs are...

cronuser always runs crontab using other users

Because cronuser never runs crontab with user = cronuser

cronuser does not need a /home

What say the PAM logs ?

But I am not an expert on PAM and other administration security things

I am pretty sure PAM does not allow crond to run commands for your user...

it was ok ;-)

uname -a does not tell much about distro

To known what distro you use => cat /etc/issue

best is to use cat /etc/issue

Therefore PAM is configured at /etc/pam.d/crond

Do you use Red Hat, Ubuntu ?

crond logs may not be readable (only for root)

Do you have an administrator contact?

I am pretty sure the issue is well explain within the crond logs

What a pity you cannot have control on crond...

you can add CRONDARGS=-p this permit any crontab even if /etc/crontab has to many permissions (should be writable for root only). crond usually uses sendmail by default. You can also check whether sendmail is available...

perfect, this is correct to be allowed. I still do not see what is wrong. Can you restart the crond deamon? What say the crondlog?

Please give me the output of ps caxf | grep -6 crond --color in your question. => Please edit your question