Ben Kennedy writes:

Apr 10 19:38:07 paleale courieresmtp: Permission denied
Apr 10 19:38:07 paleale courierd: completed,id=00000000001364E7.000000004F84C45F.00003185 Apr 10 19:38:07 paleale courieresmtp: Crashed child process 12678, while delivering to zygoat.ca Apr 10 19:38:07 paleale courierd: Waiting. shutdown time=Tue Apr 10 20:35:39 2012, wakeup time=Tue Apr 10 19:40:39 2012, queuedelivering=400, inprogress=0

I've done this same setup (using the same config, build process and OS) half a dozen times in the past several years and don't recall encountering this particular symptom.

How can I diagnose the cause? "courieresmtp: Permission denied" is a markedly inscrutable message.

Yes, something went wrong. The error message could be better.

Look in your /etc/courier directory, and check the ownership and the permissions of your configuration files, both the ones you edit yourself, and stuff that gets created by makesmtpaccess, etc. That's probably the only thing that courieresmtp cares about. If you built a new install, but then copied config files from a backup or somewhere else, and they have the wrong ownership or permissions, that's going to cause some chaos.


Attachment: pgpj9fmknzYeP.pgp
Description: PGP signature

------------------------------------------------------------------------------
Better than sec? Nothing is better than sec when it comes to
monitoring Big Data applications. Try Boundary one-second 
resolution app monitoring today. Free.
http://p.sf.net/sfu/Boundary-dev2dev
_______________________________________________
courier-users mailing list
courier-users@lists.sourceforge.net
Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users

Reply via email to