Search Text         
Search Tips?
Search By   And   Or   Boolean   Exact Match   TA #
Search In   Whole Doc   Keywords Sort By  
Product   Sub Product  

View Technical Articles (sorted by Product) New/Updated in the last:    7 days      14 days      30 days             
TA # Date Created Date Updated Resolved Issue?   Printer Friendly Version of This TA   Print Article
  E-mail This TA   E-mail Article
112461 02/08/2001 09:34 AM 02/21/2006 03:05 PM
Yes No
Local MMDF email is not being delivered locally and is waiting in queue.
Keywords
openserver open server oses osr5 v5 5.0.5 5.0.6 505 506 mmdf deliver retry queuing not deliverable now email queue locally 507 5.0.7
Release
          SCO OpenServer Enterprise System Release 5.0.5, 5.0.6, 5.0.7 
          SCO OpenServer Desktop System Release 5.0.5, 5.0.6, 5.0.7 
          SCO OpenServer Host System Release 5.0.5, 5.0.6, 5.0.7 
Problem
          Local MMDF email is not delivered locally. It is sitting in
          the MMDF local mail queue waiting for delivery. You can see
          the problem if you try to force the mail manually with the
          command:

                /usr/mmdf/bin/deliver -w -clocal

                [ Checking for Local delivery (local) mail ]
                sorting the queue.
                1 messages, 1 to be processed

                Message 'msg.aa16430', from
                '@server.domain.com: User.Name@domain.com'
                Queued: 0 Days, 0 Hours
                [ Accessing local (Local delivery)]
                Channel: local
                <user_name>:
                not deliverable now, queuing for retry
                End of processing for msg.aa16430
                deliver:  normal end

CAUSES: There are a number of potential causes:

        1. The user account information may be corrupted.

        2. It may not be possible to log in as or su to that user.

        3. If the user's $HOME directory is not owned by the user
        or the user has insufficient rights to write to their $HOME
        directory then this will prohibit MMDF to deliver the mail
        locally.

        4. MMDF's configuration or installation may be corrupted.


Solution
          1. Check the user in /etc/passwd and in /etc/group making
          sure the user is correctly defined.

          To check the user's account information within the tcb database
          use these commands:

                /tcb/bin/authck -av
                /tcb/bin/integrity -e

          and correct any problems detailed.

          2. Can the user telnet to the server and successfully log on?
          This will check to ensure that passwords are okay, the account
          is not locked and no "profile" inhibitors are present to stop
          the user from logging on successfully.

          3. Ensure the user's $HOME directory is correctly owned by
          the user and that the user has sufficient rights to write
          files in their own $HOME directory.  See chmod(C) and chown(C)

          4a. Check the MMDF log files in /usr/mmdf/log.  For more
          information on configuring these log files, see Technical Article 107230,
          "MMDF Troubleshooting Techniques."

          4b. Check the MMDF aliases to see if the user's local mail
          is routed somewhere else.

          To do this "su - mmdf ; cd table" and view any configured
          alias files there.  See mmdf(ADM)

          4c. Run "/usr/mmdf/bin/checkup" to verify MMDF's installation
          on the server.  See checkup(ADM)

          4d. Run "/usr/mmdf/bin/checkque" to see the number of messages
          waiting to be delivered.  Check the following directories for
          any corrupted files:

                /usr/spool/mmdf/lock/home/addr - the address portion
                /usr/spool/mmdf/lock/home/q.local - link to above
                /usr/spool/mmdf/lock/home/msg - the message portion

          Each message will be identified with a unique number, in the
          format:

                msg.xxyyyyy

	  4e.  Check the permissions in the /usr/mmdf/chans directory:

	  -rwx--x--x   1 mmdf     mmdf      113100 Jul 24 07:49 delay@
	  -rwx--x--x   1 mmdf     mmdf      117192 Jul 24 07:49 list@
	  -rws--x--x   1 root     mmdf      137208 Jul 24 07:49 local@
	  -rwx--x--x   1 mmdf     mmdf      110512 Jul 24 07:49 micnet@
	  -rwx--x--x   1 mmdf     mmdf      116576 Jul 24 07:49 smtp@
	  -rws--s--x   1 root     mmdf       84320 Jul 24 07:49 smtpd@
	  -rwx--x--x   1 mmdf     mmdf      115556 Jul 24 07:49 smtpsrvr@
	  -rwx--x--x   1 mmdf     mmdf      114004 Jul 24 07:49 uucp@


          See checkque(ADM)

NOTES:
          If the originator requests a Delivery Receipt of the email
          being sent, and the email has reached the recipient's server
          but is unable to be delivered locally, then the originator
          will get a Delivery Receipt for each time MMDF attempts to
          deliver the mail locally.  By default this is every minute.

    TROUBLESHOOTING:

          To send a test message locally:

                mail -s "Test Message" <local_user>
                Test Message
                CTRL-D

            /usr/mmdf/bin/deliver -w -clocal

          and you will force the delivery process manually.

SEE ALSO:
          Technical Article 107230, "MMDF Troubleshooting Techniques."

          Technical Article 106274, "MMDF doesn't deliver mail or delivers it twice."
Back to Search ResultsBack to Search Results