Sponsored Content
Operating Systems OS X (Apple) postfix queue filling up (from sendmail?) Post 302224279 by PxT on Tuesday 12th of August 2008 06:06:45 PM
Old 08-12-2008
Run 'mailq' to see what's currently in the queue. Run 'sudo postcat -q <message_id>' to see the contents of a particular message. That should help you diagnose where they care coming from. If they are coming from cron it will say so somewhere in the headers.

You can clear the deferred queue with 'sudo postsuper -d ALL deferred'
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Postfix Problem under mailx/sendmail command

Update: Problem solved with this command: /opt/soc/bin/postfix-setup ================================ Hi, I am trying the following mailx command: sadm@edwardwi-z:/etc$ mailx ewijaya@gmail.com Subject: test foo . . EOT But it gives the following error ... (0 Replies)
Discussion started by: monkfan
0 Replies

2. Linux

Migrating from SENDMAIL on SUN SOLARIS to POSTFIX on Linux

Migrating from sendmail on SUN Solaris to POSTFIX on Linux. I have been asked to migrate our sendmail to postfix on Linux and would appreciate and information. Hints and tips on the process involved. Perhaps any links to useful site or documentation that you may know about. Many Thanks (2 Replies)
Discussion started by: Andrek
2 Replies

3. Shell Programming and Scripting

postfix queue filling up

What is filling up my postfix queue (/var/spool/postfix/deferred/)? I had a perl script running via crontab to monitor my IP connection and send me a mail via sendmail. Now I have a huge queue of emails I keep getting. I've removed the crontab and the script. If I clear out... (0 Replies)
Discussion started by: kumakuma
0 Replies

4. UNIX for Dummies Questions & Answers

postfix queue filling up (from sendmail?)

What is filling up my postfix queue (/var/spool/postfix/deferred/)? I had a perl script running via crontab to monitor my IP connection and send me a mail via sendmail. Now I have a huge queue of emails I keep getting. I've removed the crontab and the script. If I clear out... (0 Replies)
Discussion started by: kumakuma
0 Replies

5. IP Networking

postfix - reinject mail to postfix from hold queue directory

hi all. Am using smtpd_recipient_restrictions & check_recipient_access in postfix. The hash file looks like this: emailaddress1 HOLD emailaddress2 HOLD The aim is to place email from these recipients in the hold directory,check them then reinject them back in postfix on some... (0 Replies)
Discussion started by: coolatt
0 Replies

6. UNIX for Dummies Questions & Answers

Mail tranmission issue: Postfix/Sendmail

Hi, I have email that is being routed from one server to another server it seems. The sending server has postfix running and the receiving server has sendmail running. The sendmail status is receiving connection. The sending server cannot seem to reach the receiving server. Error logs state... (0 Replies)
Discussion started by: mojoman
0 Replies

7. Solaris

Replace sendmail with Postfix

Hi, I am assigned to replace sendmail with Postfix in solaris 10. Can anyone please tell what are the steps should be taken like files to backup and what are the configurations should be taken care and so on??????? Appreciate any help.... (0 Replies)
Discussion started by: bpsunadm
0 Replies

8. Linux

Postfix problem with hold messages queue

Hello, I'm having a problem with my Postfix server, all new messages stay on hold in the queue, I always have to un-hold messages and then flush the mail queue so that all messages are delivered. I do not know how to make postfix to always send the messages automatic. Can anybody assist me on... (0 Replies)
Discussion started by: marques_rmc
0 Replies

9. UNIX for Dummies Questions & Answers

ACL for postfix or sendmail

Hello, i want to know how to configure a MTA to relay somes domain by IP source, example : toto.com and titi.com can relay with ip sender 10.2.2.0/24 only lulu.com can relay with ip sender 192.168.0.4/32 only all domain can relay with ip sender 172.0.0.5/32 only It's possible with policy... (9 Replies)
Discussion started by: safsound
9 Replies

10. UNIX for Dummies Questions & Answers

French characters in postfix/sendmail

Hello again, How can I send emails via postfix with special characters like "à" via postfix. When I'm paste-ing the special character inside a editor (nano) it shows like this --> � ... any tips? (1 Reply)
Discussion started by: galford
1 Replies
queuedefs(4)							   File Formats 						      queuedefs(4)

NAME
queuedefs - queue description file for at, batch, and cron SYNOPSIS
/etc/cron.d/queuedefs DESCRIPTION
The queuedefs file describes the characteristics of the queues managed by cron(1M). Each non-comment line in this file describes one queue. The format of the lines are as follows: q.[njobj][nicen][nwaitw] The fields in this line are: q The name of the queue. a is the default queue for jobs started by at(1); b is the default queue for jobs started by batch (see at(1)); c is the default queue for jobs run from a crontab(1) file. njob The maximum number of jobs that can be run simultaneously in that queue; if more than njob jobs are ready to run, only the first njob jobs will be run, and the others will be run as jobs that are currently running terminate. The default value is 100. nice The nice(1) value to give to all jobs in that queue that are not run with a user ID of super-user. The default value is 2. nwait The number of seconds to wait before rescheduling a job that was deferred because more than njob jobs were running in that job's queue, or because the system-wide limit of jobs executing has been reached. The default value is 60. Lines beginning with # are comments, and are ignored. EXAMPLES
Example 1: A sample file. # # a.4j1n b.2j2n90w This file specifies that the a queue, for at jobs, can have up to 4 jobs running simultaneously; those jobs will be run with a nice value of 1. As no nwait value was given, if a job cannot be run because too many other jobs are running cron will wait 60 seconds before trying again to run it. The b queue, for batch(1) jobs, can have up to 2 jobs running simultaneously; those jobs will be run with a nice(1) value of 2. If a job cannot be run because too many other jobs are running, cron(1M) will wait 90 seconds before trying again to run it. All other queues can have up to 100 jobs running simultaneously; they will be run with a nice value of 2, and if a job cannot be run because too many other jobs are running cron will wait 60 seconds before trying again to run it. FILES
/etc/cron.d/queuedefs queue description file for at, batch, and cron. SEE ALSO
at(1), crontab(1), nice(1), cron(1M) SunOS 5.10 1 Mar 1994 queuedefs(4)
All times are GMT -4. The time now is 02:56 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy