Argggggghhhhh
Mar. 14th, 2008 06:33 pm![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
furrbear*head* *desk* *head* *desk* *head* *desk* *head* *desk* *head* *desk*
Another project I've been working on is an email robot. I fixed all the flaws from it being
very old code, using very old versions. But testing is driving me nuts.
If it is invoked via the mail aliases, the GPGme library returns an "Invalid engine"
error.
Here's the entry from etc/mail/aliases:
*BUT*
Another project I've been working on is an email robot. I fixed all the flaws from it being
very old code, using very old versions. But testing is driving me nuts.
If it is invoked via the mail aliases, the GPGme library returns an "Invalid engine"
error.
Here's the entry from etc/mail/aliases:
That chokes.rosie: /home/rosie/rosie-log, "|/home/rosie/rosie-wrapper"
*BUT*
rosie@yogi:~$ cat /home/rosie/rosie-log | /home/rosie/rosie-wrapperworks fine and mails me the results I expect.
![[identity profile]](https://www.dreamwidth.org/img/silk/identity/openid.png){kind=small}
no subject
Date: 2008-03-15 06:40 pm (UTC)The error you're getting makes me think there's some environment variable or something that's present for the rosie user, but not for sendmail.
su -l(or whatever the less-privliged sendmail user is) and see if piping stuff throughrosie-wrapperstill works.Alternatively, strip down the alias listing to just the pipe to
rosie-wrapperand see if that makes a difference.