Re: New question (exchenge to addressee of BOUNCE-mail) 2

"Joe R. Jah" <[email protected]>
Newsgroups gmane.mail.majordomo.general
Message-ID <[email protected]>
On Tue, 22 Aug 2006, Masaaki OYA wrote:

> Date: Tue, 22 Aug 2006 16:48:16 +0900
> From: Masaaki OYA <[email protected]>
> To: [email protected]
> Subject: New question (exchenge to addressee of BOUNCE-mail) 2
> 
> Dear Joe R. Jah and users
> 
> I'm OYA. I've a new question.
> I imported the relevant parts of the patch to sequencer.
> ML that used resend have no problem. But ML that used sequencer
> have a problem. In detail, if non_member send to ML that used sequencer,
> it's no problem. But when a member send to ML that used sequencer,
> this mail sent to list-member and BOUNCE mail sent to sender.
> How shall I do?

As Dan suggested in May, you can post your patch to the list.  If you
cannot make a patch on your system you can send your modified sequencer
instead; the original sequencer is less than 15K.

Regards,

Joe
-- 
     _/   _/_/_/       _/              ____________    __o
     _/   _/   _/      _/         ______________     _-\<,_
 _/  _/   _/_/_/   _/  _/                     ......(_)/ (_)
  _/_/ oe _/   _/.  _/_/ ah        [email protected]

> > I'm Masaaki OYA. Thank you very much. I solved a problem.
> > I imported the relevant parts of the patch to sequencer. 
> > And I confirmed that a bounce-mail sended to sender and ML-owner. 
> > 
> >> Either switch back to resend, or if you can program in perl, import the
> >> relevant parts of the patch to sequencer script.
> >> 
> >>> >   ftp://ftp.ccsf.org/majordomo-patches/1.94.5/config_parse.pl-resend.3
> 
> Best Regards,
> ----------------------------------------------------------------------
> Nobeyama Radio Observatory, in Japan
> Computer Support Team       Masaaki Oya
> Tel. 81-267-98-4337   (NRO-SE-room)
> Fax. 81-267-98-2093 $B!!(B(   $B!!(B,,$B!!(B  )
> E-mail [email protected]
> ----------------------------------------------------------------------
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.