AF:
NF:0
PS:10
SRH:1
SFN:
DSR:
MID:<20081104145626.64238ca7@ripper.onstor.net>
CFG:
PT:0
S:andy.sharp@onstor.com
RQ:
SSV:exch1.onstor.net
NSV:
SSH:
R:<maxim.kozlovsky@onstor.com>,<ed.kwan@onstor.com>,<jonathan.goldick@onstor.com>,<brian.stark@onstor.com>,<sandrine.boulanger@onstor.com>
MAID:1
X-Sylpheed-Privacy-System:
X-Sylpheed-Sign:0
SCF:#mh/Mailbox/sent
RMID:#imap/andys@onstor.net@exch1.onstor.net/INBOX	0	2779531E7C760D4491C96305019FEEB5175BE0AE07@exch1.onstor.net
X-Sylpheed-End-Special-Headers: 1
Date: Tue, 4 Nov 2008 14:57:32 -0800
From: Andrew Sharp <andy.sharp@onstor.com>
To: Maxim Kozlovsky <maxim.kozlovsky@onstor.com>
Cc: Ed Kwan <ed.kwan@onstor.com>, Jonathan Goldick
 <jonathan.goldick@onstor.com>, Brian Stark <brian.stark@onstor.com>,
 Sandrine Boulanger <sandrine.boulanger@onstor.com>
Subject: Re: exim4 testing ideas
Message-ID: <20081104145732.4ff8830f@ripper.onstor.net>
In-Reply-To: <2779531E7C760D4491C96305019FEEB5175BE0AE07@exch1.onstor.net>
References: <20081103165035.025ec63e@ripper.onstor.net>
	<2779531E7C760D4491C96305019FEEB5175BE0A9E0@exch1.onstor.net>
	<20081104140759.3acc3c07@ripper.onstor.net>
	<20081104142520.0d7249bd@ripper.onstor.net>
	<2779531E7C760D4491C96305019FEEB5175BE0AE07@exch1.onstor.net>
Organization: Onstor
X-Mailer: Sylpheed-Claws 2.6.0 (GTK+ 2.8.20; x86_64-pc-linux-gnu)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit

Based on the checkin comments for these changes, I agree.

On Tue, 4 Nov 2008 14:51:38 -0800 Maxim Kozlovsky
<maxim.kozlovsky@onstor.com> wrote:

> Let's integrate the changes 30354 and 30414 in the release. Not
> having these changes could potentially have contributed to the
> problem.



> >-----Original Message-----
> >From: Andy Sharp
> >Sent: Tuesday, November 04, 2008 2:25 PM
> >To: Maxim Kozlovsky
> >Subject: Re: exim4 testing ideas
> >
> >Oops, that doesn't work, since there is no r_endp in r401rel.  Can
> >you give me a code snippet for r401rel?  I can try and xlate it
> >myself...
> >
> >
> >On Tue, 4 Nov 2008 14:07:59 -0800 Andrew Sharp
> ><andy.sharp@onstor.com> wrote:
> >
> >> I'm working in r401rel, for sanity sake, here is the diff:
> >>
> >>
> >>
> >> p4 diff nfx-tree/code/ssc-rmc/rmc.c
> >> ==== //depot/r401rel/nfx-tree/code/ssc-rmc/rmc.c#1
> >> - /homes/andys/src/r401rel/nfx-tree/code/ssc-rmc/rmc.c ====
> >> 1011a1012,1019
> >> > if (memcmp(r_endp.appnm, "exim4", strlen("exim4")) == 0) {
> >> > 	static cnt;
> >> > 	if (++cnt % 2) {
> >> > 		// drop odd open messages from exim4
> >> >             rmc_discard_data(sess, msg, addr, &addr_len);
> >> >             return RMC_BADMSG;
> >> > 	}
> >> > }
> >>
> >>
> >>
> >>
> >>
> >>
> >>
> >> On Mon, 3 Nov 2008 17:05:42 -0800 Maxim Kozlovsky
> >> <maxim.kozlovsky@onstor.com> wrote:
> >>
> >> > You can add something like this into
> >> > ssc-rmc/rmc.c:rmc_internal_getmsg():
> >> >
> >> > ~line 1082, after the call to rmc_internal_gethdr()
> >> >
> >> > if (memcmp(r_endp.appnm, "exim4", strlen("exim4")) == 0) {
> >> > 	static cnt;
> >> > 	if (++cnt % 2) {
> >> > 		// drop odd open messages from exim4
> >> >             rmc_discard_data(sess, msg, addr, &addr_len);
> >> >             return RMC_BADMSG;
> >> > 	}
> >> > }
> >> >
> >> > Also check if the rmc_timer_intr() is indeed the function that is
> >> > installed as the signal handler for SIGALRM.
> >> >
> >> >
> >> >
> >> > >-----Original Message-----
> >> > >From: Andy Sharp
> >> > >Sent: Monday, November 03, 2008 4:51 PM
> >> > >To: Maxim Kozlovsky
> >> > >Cc: Brian Stark; Jonathan Goldick
> >> > >Subject: exim4 testing ideas
> >> > >
> >> > >So I've produced a new version of exim4 which I hope will
> >> > >address the issues, but I have no way of testing to see if it
> >> > >has the same problems as the previous version.  Is there a way
> >> > >to cause RMC to retry always or something?  If that is even the
> >> > >problem?  I have removed the use of setitimer in exim (which
> >> > >uses SIGALRM) and added a rmc_shutdown() call after all the RMC
> >> > >related function calls have returned ... I think.
> >> > >
> >> > >Any ideas or help appreciated.
> >> > >
> >> > >Thanks,
> >> > >
> >> > >a
