AF:
NF:0
PS:10
SRH:1
SFN:
DSR:
MID:
CFG:
PT:0
S:andy.sharp@onstor.com
RQ:
SSV:exch1.onstor.net
NSV:
SSH:
R:<maxim.kozlovsky@onstor.com>,<brian.stark@onstor.com>,<jonathan.goldick@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	2779531E7C760D4491C96305019FEEB5175BE0A9E0@exch1.onstor.net
X-Sylpheed-End-Special-Headers: 1
Date: Mon, 3 Nov 2008 18:44:33 -0800
From: Andrew Sharp <andy.sharp@onstor.com>
To: Maxim Kozlovsky <maxim.kozlovsky@onstor.com>
Cc: Brian Stark <brian.stark@onstor.com>, Jonathan Goldick
 <jonathan.goldick@onstor.com>
Subject: Re: exim4 testing ideas
Message-ID: <20081103184433.59455bf7@ripper.onstor.net>
In-Reply-To: <2779531E7C760D4491C96305019FEEB5175BE0A9E0@exch1.onstor.net>
References: <20081103165035.025ec63e@ripper.onstor.net>
	<2779531E7C760D4491C96305019FEEB5175BE0A9E0@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

cool

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
