newaliases

Started by Valken, March 16, 2004, 07:01:47 AM

Previous topic - Next topic

Valken

Hi,
It seems that I've lost the command newaliases from my system.

free1# ls -lah /usr/bin/newaliases lrwxrwxrwx  1 root  wheel  21B Feb 13 23:58 /usr/bin/newaliases -> /usr/sbin/mailwrapper


free1# ls -lah /usr/sbin/mailwrapper-r-xr-xr-x  1 root  wheel  5.7K Jan 11 03:48 /usr/sbin/mailwrapper


I want of course to receive system log to my email address so I've created an alias for root -> email@domain

But now I can't make newaliases.

It worked before I've reinstalled mail toaster 3.36

How can I reinstall this function ?

Regards

Valken

Valken

I just did found that there is a port containing the new_alias_patch for qmail.
But...
I don't dare to install it. Sad

Any advices ?

Thank a lot

Valken

happytommy

/etc/mail/mailer.conf

newaliases      /usr/libexec/sendmail/sendmail

then do newaliases

Valken

Thank, for newalias it seems to work well.
I don't know why this conf file has changed.

Now I must made some tries.
I'll see.

Regards

Valken

Valken

Thank.
Now in my /etc/aliases file I have an entry for root ...

root:   valken@mydomain

Then I do a newalias (as root of course)

> sudo newaliases/etc/mail/aliases: 25 aliases, longest 17 bytes, 267 bytes total


But if I try to send an email to root...

>mail root
Subject:
...
...

Ctrl-D

It doesn't go to my mail box.

Any idea where the problem can come from ?

Regards

Alex

davidcl

Do you have fastforward installed?

Without fastforward, qmail doesn't look at the /etc/aliases file at all.  That's why the mailer.conf file was changed-- qmail doesn't have a "newaliases" command as such.

Do you need to use /etc/aliases, or would creating the aliases in a different way work for you?  The usual qmail way is to create .qmail files, either in the user's directory, the domain's directory, or the /var/qmail/alias directory.

Valken

Thank a lot.

I've corrected the problem by adding my hostname (the one I can see by typing hostname) into /var/qmail/control/locals

Then restarted the services via...

>sudo services stop
>sudo services start

And everything is ok now.

Valken

PS: I always explain what I've done so for other newbies there is a more detailed procedure