<br>It does seem as though the problem begins when MailScanner disposes of a message. Maybe someone could clarify the process whereby Sendmail picks up the message and decides to deliver it (locally or relay or whatever.)
<br><br>It doesn't look like a DNS issue. We've got a local resolver (that has a PTR record for the machine's IP) and a backup resolver. I've done a number of DNS tests and haven't been able to produce an error there.
<br><br>On other systems everything happens so quickly that it's hard to see what happens but does it resemble this:<br> - MailScanner finds message in <a href="http://mqueue.in">mqueue.in</a><br> - MailScanner processes message and dumps qf/df into mqueue
<br> - Sendmail daemon periodically scans mqueue<br><br>or:<br> - MailScanner finds message in <a href="http://mqueue.in">mqueue.in</a><br> - MailScanner processes message and spawns a sendmail process for delivery<br><br>
<br>What are the implications of the "Delivery Method" queue vs. batch option on the above?<br><br>Thanks for the input!<br><br>-Corey<br><br><br><br><br><div><span class="gmail_quote">On 8/1/07, <b class="gmail_sendername">
Scott Silva</b> <<a href="mailto:ssilva@sgvwater.com">ssilva@sgvwater.com</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Corey McFadden spake the following on 7/31/2007 9:46 PM:<br>><br>> Guys,<br>><br>> We're experiencing an issue on one of our boxes where messages (a good<br>> percentage) are hung in /var/spool/mqueue after being processed by
<br>> MailScanner. Even those to be delivered locally will sit for<br>> (sometimes) hours until they're finally delivered.<br>><br>> I've never seen this behavior before and something is definitely awry.
<br>><br>> Here's the environment:<br>><br>> This is CentOS release 4.5 (Final)<br>> This is Perl version 5.008008 (5.8.8)<br>><br>> This is MailScanner version 4.61.7<br>><br>> Executing 'sendmail -q -v' WILL process the stuck messages but can take
<br>> quite a long time to run because it will try to deliver everything<br>> queued in a linear fashion.<br>><br>Since it is in mqueue and not <a href="http://mqueue.in">mqueue.in</a>, mailscanner is pretty much out of the
<br>loop. Check if you have a FQDN that resolves properly as this will choke<br>sendmail quickly. Also try a local caching nameserver, as sendmail might be<br>taking a long time to resolve delivery addresses.<br><br>--<br>
<br>MailScanner is like deodorant...<br>You hope everybody uses it, and<br>you notice quickly if they don't!!!!<br><br>--<br>MailScanner mailing list<br><a href="mailto:mailscanner@lists.mailscanner.info">mailscanner@lists.mailscanner.info
</a><br><a href="http://lists.mailscanner.info/mailman/listinfo/mailscanner">http://lists.mailscanner.info/mailman/listinfo/mailscanner</a><br><br>Before posting, read <a href="http://wiki.mailscanner.info/posting">http://wiki.mailscanner.info/posting
</a><br><br>Support MailScanner development - buy the book off the website!<br></blockquote></div><br>