<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 12pt;
font-family:Calibri
}
--></style></head>
<body class='hmmessage'><div dir='ltr'>Well, in my peticular case, these are *INCOMING* messages that need to be sent to specific 'AREA's.<BR>
<BR>
So, <U>all should be deliverable.</U> <BR>
<BR>
Unknown why they stop being distributed into AREA mailboxes as per rules in the rewrite file.<BR>
<BR>
But..... there they sit.<BR>
<BR>
:/ <BR> <BR>
<DIV>Date: Fri, 21 Mar 2014 15:24:45 -0400<BR>From: jjn@nuge.com<BR>To: nos-bbs@tapr.org<BR>Subject: Re: [nos-bbs] Message log jam<BR><BR><PRE>Greetings,<BR> <BR>On Fri, 21 Mar 2014, Wm Lewis wrote:<BR> <BR>><BR>> Tried SMTP KICK (Nothing happened)<BR>> Removed any 'lck' files, and re'kicked' (nothing happened)<BR>> Removed all files except the sequence file, (in /jnos/spool/mqueue) then waited. New messages instantly jam again.<BR>> Rebooted. No change, instant jam.<BR>><BR>> Only thing that seems to get them going again is if I delete all files <BR>> in /jnos/spool/mqueue *and* all files in /jnos/spool/mail<BR>><BR>> Of course deleting the later files mean deleting every last message on <BR>> my system. Not really the course of action I'm looking for.<BR>><BR>> So, as of now, they are still back-logging in the /jnos/spool/mqueue <BR>> directory waiting for some unknown force to kick in.<BR> <BR> <BR> If there are several messages stuck in the queue, and let's say that 3 <BR>of them cannot reach their destination, then those 3 will remain at the <BR>top of the queue and block ALL REMAINING MESSAGES from being delivered. <BR>JNOS does NOT push undeliverable messages to the back of the queue :(<BR> <BR> What controls how many messages are allowed to be in transit <BR>simultainiously is "SMTP MAXCLIENTS". In my scenario above, if this is <BR>set to 3 then the undeliverable messages will block all others in the <BR>queue. If we up the SMTP MAXCLIENTS to 4, then the 4th msg in the queue <BR>will be allowed to fly. Once it is completed the next message (now the <BR>new fouth message) will fly.<BR> <BR> But when you encounter a 4th message that is undeliverable, the queue <BR>will again be jammed :(<BR> <BR> What we need is for the queue to push "undeliverable" messages to the <BR>rear of the queue. Let the messages that CAN be delivered get moved <BR>toward the front of the queue and get sent. Whether we rear-queue <BR>undeliverables after one try, or two, or three might be open for <BR>discussion.<BR> <BR> <BR> ---- Jay Nugent WB8TKL<BR> Hamgate.Washtenaw.AMPR.org<BR> <BR> <BR></PRE><BR>_______________________________________________ nos-bbs mailing list nos-bbs@tapr.org http://www.tapr.org/mailman/listinfo/nos-bbs<BR>_______________________________________________ nos-bbs mailing list nos-bbs@tapr.org http://www.tapr.org/mailman/listinfo/nos-bbs</DIV> </div></body>
</html>