Re: [cobalt-developers] Email piping problem

[Mailing Lists <listonly@xxxxxxxxxxxxxxxxxxxx>]

on 8/10/02 9:16 AM, Michele Neylon -Blacknight Solutions stated:

> This might be a very trivial problem, but I'm at a complete loss.
> I have been trying to setup PerlDesk on a RAQ4 for the last couple of days.
> Everything seems to work, except for the email piping.
> In /etc/mail/aliases I have:
> trouble:"|/usr/adm/sm.bin/email.pl"  (a copy of the email pipe from Perldesk)
> If I try sending a mail to that address I get 'user unknown' or similar
> 
> Second method.
> I created a user 'support'.
> In the user's directory I created a .forward with:
> /usr/adm/sm.bin/email.pl
> 
> the script is set:
> -rwxr-xr-x   1 root     root        18089 Aug  9 18:53 email.pl
> this gives a  550 Unsafe for mailing to files
> 
> I'm running out of ideas here, so any would be gratefully accepted!
> 
> 
> Mr. Michele Neylon

We have it running on a Raq3 and it was a bit picky on getting the email
function to work.

I see you have the email.pl in the /usr/adm/sm.bin/
Make sure it is chmod 755 email.pl

When you add the alias to the alias file, first you have to create the user
in the Raq GUI. The you will add that email account to the alias file.
Example, we added dns@xxxxxxxxxxxxxxxxxxxx to the user accounts for that
domain. Next go to the /etc/alias file, or it may be different on a Raq4.

This part is important, or at least it was for me, you don't want to just
put this::

dns: "|usr/adm/sm.bin/email.pl"

Instead put::

dns@xxxxxxxxxxxxxxxxxxxx:  "|/usr/adm/sm.bin/email.pl"

Seems that the Raq's want the full addy. Try that and let us know.

Dave
>