Hi,

I have setup exim (using eximconfig), and it works like I want it with sendmail (relaying my messages to my isp's smtp server).

When I run mailq however, i see a huge queue building up, for messages with destination to root@myisp. I don't want to send anything there. (I have figured out how to flush the queue manually, but it still builds up)

Everything else is working fine on the system, and I would just like to stop these messages.

I would guess that your root account isn't yet aliased to a real address, so all the status reports can't be forwarded on. Edit the aliases file and alias root to an active email address, then run the newaliases command to make the change active.

That could be it. I have no idea where to set that.

Currently the root's messages are trying to go to root@ my isp's domain. I obviously don't have that.

I don't want to receive the root messages anyway. I only want to send messages.

Maybe I should say rephrase. Maybe I should try to find whatever is generating these messages?

At least 20 messages intended for root has been generated since I started this thread.

By convention all built-in automated tasks send their reports and error warnings to root, which should be aliased to a real e-mail address. Depending on your distribution the aliases file is either /etc/aliases or /etc/exim/aliases. Again, you need to run newaliases after editing it for Exim to pick up the changes.

The log analyzer reports are your early warning system against system errors and hacking attempts, so I actually wouldn't recommend disabling email reports on any production server.

Thanks for the reply.

I have found that the error messages are being generated by samba: Every 30 minutes the pc tries to mount a network drive, and upload a report. However when that network computer is down, the mount cannot take place, and the error message is sent.

Any suggestions on how to stop the message from being sent?

And do I have to receive the root messages? Is it possible to point the root messages to a void or a null or something (obviously without building up the queue)?

Also, I don't have, nor do I want a pop server on the computer, and I really don't want these messages going to some valid email address, wasting bandwidth.

Any suggestions on how to stop the message from being sent?
If it's a scheduled mount then fix the network detection in the cronjob that tries to mount the drive. In cronjobs output goes to the email address defined in the cronjobs "MAILTO=" variable. For system and root cronjobs it obviously goes to root unless you set the variable to that of another email account, preferably one being read by a human user.


And do I have to receive the root messages? Is it possible to point the root messages to a void or a null or something (obviously without building up the queue)?
It's already been said that email sent to root can be valuable since it contains alerts to watch out for and errors to correct. So please don't ask again, don't dodge the issue and don't use arguments like "bandwidth waste" because that is not a valid reason. Period. Fix the cause and add an alias for root in /etc/(mail/)aliases linked to a mail account that is read by a human, then run "newaliases".

Thanks unSpawn, I think it does go to the cronjob's MAIL like you said, because I set the newaliases, and it still goes to the same place. (I'll try to set that today)

I'm sorry to mention this again, but the way I understand it, to not waste bandwidth, I have to setup a local pop server. Is that correct? I really don't want this messages going out, and back in over my internet connection, as I can only afford a 3gb cap (South Africa's internet very expensive).

But since you strongly recommend reading these messages, and considering it's the default behavior, I guess I'll try to figure out how to setup a pop server.