11-08-2012 11:05 PM
send mail process running in every 15 minutes
and take out 50% cpu usages.
and my server folder
/var/spool/mqueue also kept many files.
11-08-2012 11:54 PM
Run "mailq" as root to get a better overview of the contents of the /var/spool/mqueue directory. Also check the postmaster notifications in the local mail inbox of the root user, i.e. /var/mail/root file.
If the output includes messages that are sent from outside your organization to destinations outside your organization, your mail server is probably an open relay that is being abused by spammers. This is a serious configuration error and other mail server administrators may hate you for it.
If the system is your main mail server, it should accept mail in two categories:
- from inside your organization to any destinations
- from outside your organization to destinations within your organization only
You should never allow a mail server to accept mail from anywhere for delivery to anywhere: such a configuration will be abused by spammers eventually.
If the system is not (one of) your main mail server(s), its port 25 should not be accessible from the Internet at all, and it should normally be configured to deliver all outgoing mail to your main mail server(s) only. The main mail server(s) would use their configuration rules to determine if the message can be forwarded to its actual destination or not.
If the mailq output includes only bounce messages for mails that clearly are not sent by you, a spammer has used your domain name as a fake source address in a spam campaign, and you are getting the error messages as backscatter. If this system is one of your main mail servers, there is not much you can do to completely block this, but there may be some ways to limit the flood. If this system is not used as an actual mail server, just block access from Internet to port 25.
If the messages in your mail queue are bounce messages for mails that are actually sent by your system, you may have a malfunctioning e-mail generator software that is sending messages to invalid destinations. Look at the bounce messages to identify the origin of the failed messages, find the e-mail generator and fix it.
11-09-2012 12:04 AM - edited 11-09-2012 12:16 AM
>sendmail process running in every 15 minutes.
>and my server folder /var/spool/mqueue also kept many files.
I too had this directory fill up with messages and N bounces for those messages. Due to a hardware error and a bad root alias.
I basically created a script to look for the bounce text and remove them. Then I could look at the originals and find why they were bouncing.
What does mailq show?
>H??Subject: Postmaster notify: see transcript for details
You need to look at the corresponding dfqA96xcD0010198 for the details.
See these topics: