X-Junk-Score: 0 [] X-Cloudmark-Score: 0 [] Return-Path: Received: from bigsky.scconsult.com ([66.73.230.187] verified) by mail.stalker.com (CommuniGate Pro SMTP 5.2.3) with ESMTP id 44917542 for SIMS@mail.stalker.com; Thu, 22 May 2008 07:51:20 -0700 Received-SPF: pass receiver=mail.stalker.com; client-ip=66.73.230.187; envelope-from=listbill@scconsult.com Received: from bigsky.scconsult.com (localhost [127.0.0.1]) by bigsky.scconsult.com (Postfix) with ESMTP id E3744C761FA for ; Thu, 22 May 2008 10:49:59 -0400 (EDT) Mime-Version: 1.0 Message-Id: In-Reply-To: References: X-Message-Flag: Use of Microsoft mail clients is the primary cause of cracked systems. Please switch! Date: Thu, 22 May 2008 10:49:53 -0400 To: "SIMS Discussions" From: Bill Cole Subject: Re: Backup Content-Type: text/plain; charset="us-ascii" ; format="flowed" At 10:11 AM -0400 5/22/08, lcs@spellnetwork.com imposed structure on a stream of electrons, yielding: >I want to thank everyone that answered. I tried changing the R E to >R W and restart the machine - however even after saving each file >with the change somehow it revert immediately back to the R E and >would not attempt to send the mail. I made a backup of the Q since >I didn't want to lose those messages but I really need to send them >off to the primary. Should I try copying the text files into the >primary? The mail belongs to clients and I'm sure some of it is >important. >Thanks for any suggestion. You could make the E/W flag changes, manually copy the files to the primary, and restart SIMS so that it pick them up, but then you'll never know what is causing these to fail and that latent problem will remain. What does the SIMS log show? If you try the status flag change with logging cranked up all the way, you should get something detailing why SIMS is failing the messages. We also could be missing something on the flag change. I don't have an active SIMS machine any more to test with and I don't have any detailed notes on this, but I did find example queue files that I marked 'failed' and 'retry' for future reference. The "retry" one has two recipient status lines, and they look like this: R W 29-10-1998 11:56:59 0001 rcpt.1.domain rcpt.1.user R T 29-10-1998 11:26:17 0000 rcpt.2.domain rcpt.2.user I *THINK* the 'R T' one indicates that the message has already been delivered to My deduction (i.e. could be wrong...) based on how SIMS queueing is configured (and the Date header of the example message) is that the date and time fields denote (in GMT) the last delivery attempt and the 4-digit number in the 5th field is a counter of how many delivery attempts have been made for that recipient. You MAY get a fix from changing both the E to a W and that counter to 0000. Maybe. > >------------------------------------------------------------- >LCS >On May 19, 2008, at 12:18 PM, Bill Christensen wrote: > >>At 11:55 AM -0400 5/19/08, Bill Cole wrote: >>> >>>The S.* files in the SIMS queue are plain text files consisting of >>>the message and its headers prefaced with lines containing the >>>SMTP envelope and queue state. I don't know that Stalker ever >>>fully documented the semantics, and I don't remember everything I >>>used to know about SIMS, but I THINK that you can change a >>>terminally failed message back into a retryable message by editing >>>the envelope recipient line(s) at the top starting with 'R E ' to >>>start with 'R W ' >> >>That is correct. >> >>You'll have to restart SIMS for it to pick up the change. > > >############################################################# >This message is sent to you because you are subscribed to > the mailing list . >To unsubscribe, E-mail to: >To switch to the DIGEST mode, E-mail to >To switch to the INDEX mode, E-mail to >Send administrative queries to -- Bill Cole bill@scconsult.com