How to Force Mail Queue Processing in the Mail Queue, /var/spool/mqueue

Use this procedure, for example, to process messages to a system that was previously unable to receive messages.

1. Become root or assume an equivalent role.

   For information about roles, refer to "Using Privileged Applications" in System Administration Guide: Security Services.

2. Force queue processing and display the progress of the jobs as the queue is cleared.

   # /usr/lib/sendmail -q -v

   
   

How to Run a Subset of the Mail Queue, /var/spool/mqueue

Use this procedure, for example, to force a substring of an address, such as a host name, to be processed. Also, use this procedure to force a particular message from the queue.

1. Become root or assume an equivalent role.

   For information about roles, refer to "Using Privileged Applications" in System Administration Guide: Security Services.

2. Run a subset of the mail queue at any time with -qRstring.

   # /usr/lib/sendmail -qRstring

   
   

   string

   Use a recipient's alias or a substring of user@host.domain, such as a host name.

   Alternately, you can run a subset of the mail queue with -qInnnnn.

   # /usr/lib/sendmail -qInnnnn

   
   

   nnnnn

   Use a queue ID.

How to Move the Mail Queue, /var/spool/mqueue

If you are moving the mail queue, follow these instructions.

1. Become root on the mail host or assume an equivalent role.

   For information about roles, refer to "Using Privileged Applications" in System Administration Guide: Security Services.

2. Kill the sendmail daemon.

   # /etc/init.d/sendmail stop

   
   

   Now, sendmail is no longer processing the queue directory.

3. Change to the /var/spool directory.

   # cd /var/spool

   
   

4. Move the directory, mqueue, and all its contents to the omqueue directory. Then create a new empty directory that is named mqueue.

   # mv mqueue omqueue; mkdir mqueue

   
   

5. Set the permissions of the directory to read/write/execute by owner, and read/execute by group. Also, set the owner and group to daemon.

   # chmod 750 mqueue; chown root:bin mqueue

   
   

6. Start sendmail.

   # /etc/init.d/sendmail start

   
   

How to Run the Old Mail Queue, /var/spool/omqueue

To run an old mail queue, follow these instructions.

1. Become root or assume an equivalent role.

   For information about roles, refer to "Using Privileged Applications" in System Administration Guide: Security Services.

2. Run the old mail queue.

   # /usr/lib/sendmail -oQ/var/spool/omqueue -q

   
   

   The -oQ flag specifies an alternate queue directory. The -q flag says to run every job in the queue. Use the -v flag if you are displaying the verbose output on the screen.

3. Remove the empty directory.

   # rmdir /var/spool/omqueue

   
   

Administering .forward Files (Task Map)

The following table describes the procedures for administering .forward files. For more information, refer to .forward Files in Chapter 23, Mail Services (Reference).

Administering .forward Files (Tasks)

This section contains several procedures that are related to .forward file administration. Because these files can be edited by users, the files can cause problems. For more information, refer to .forward Files in Chapter 23, Mail Services (Reference).

How to Disable .forward Files

This procedure, which prevents automated forwarding, disables the .forward file for a particular host.

1. Become root or assume an equivalent role.

   For information about roles, refer to "Using Privileged Applications" in System Administration Guide: Security Services.

2. Make a copy of /usr/lib/mail/domain/solaris-generic.m4 or your site-specific domain m4 file.

   # cd /usr/lib/mail/domain # cp solaris-generic.m4 mydomain.m4

   
   

   mydomain

   Use the file name of your choice.

3. Add the following line to the file that you just created.

   define(`confFORWARD_PATH',`')dnl

   
   

   If a value for confFORWARD_PATH already exists in the m4 file, replace the value with this null value.

4. Build and install a new configuration file.

   If you need help with this step, refer to How to Build a New sendmail.cf File.

   ---

   Note - When you edit the .mc file, remember to change DOMAIN(`solaris-generic') to DOMAIN(`mydomain').

   ---

How to Change the .forward File Search Path

If, for example, you want to put all .forward files in a common directory, follow these instructions.

1. Become root or assume an equivalent role.

   For information about roles, refer to "Using Privileged Applications" in System Administration Guide: Security Services.

2. Make a copy of /usr/lib/mail/domain/solaris-generic.m4 or your site-specific domain m4 file.

   # cd /usr/lib/mail/domain # cp solaris-generic.m4 mydomain.m4

   
   

   mydomain

   Use the file name of your choice.

3. Add the following line to the file that you just created.

   define(`confFORWARD_PATH',`$z/.forward:/var/forward/$u')dnl

   
   

   If a value for confFORWARD_PATH already exists in the m4 file, replace the value with this new value.

4. Build and install a new configuration file.

   If you need help with this step, refer to How to Build a New sendmail.cf File.

   ---

   Note - When you edit the .mc file, remember to change DOMAIN(`solaris-generic') to DOMAIN(`mydomain').

   ---