Great Circle Associates Majordomo-Workers
(November 1998)
 

Indexed By Date: [Previous] [Next] Indexed By Thread: [Previous] [Next]

Subject: Re: Recent developments
From: Jason L Tibbitts III <tibbs @ hpc . uh . edu>
Date: 19 Nov 1998 17:51:02 -0600
To: Bryan Fullerton <bryanf @ samurai . com>
Cc: majordomo-workers @ GreatCircle . COM
In-reply-to: Bryan Fullerton's message of "Thu, 19 Nov 1998 16:02:03 -0500"
References: <Pine.LNX.4.05.9811191848170.14470-100000@neviim.torah.org> <ufalnl78v3r.fsf@sina.hpc.uh.edu> <19981119160203.B1598@samurai.com>

>>>>> "BF" == Bryan Fullerton <bryanf@samurai.com> writes:

BF> The only cosmetic bug/change I've found is that messages bounced to the
BF> list-owner which have an X-MJ-Confirm: header are still not
BF> completed. ie, a while ago the header used to have the token number
BF> appended, but now it's just:

BF> X-MJ-Confirm: http://geisha.samurai.com/cgi-bin/mj_confirm

Is that what you set confirm_url to?  You can give it more info than that;
does it do what you want if you do

configset GLOBAL confirm_url =\
    http://geisha.samurai.com/cgi-bin/mj_confirm?t=$TOKEN

?  The $TOKEN is expanded to, well, the token, but the core itself doesn't
know about mj_confirm's arguments so it doesn't append them automatically.

I should probably auto-configure for the web stuff.  Perhaps I'll do that
now.

 - J<


References:
Indexed By Date Previous: Re: Recent developments
From: Brock Rozen <brozen@torah.org>
Next: MJ2 question...
From: Jason Rasku <jrasku@ArmispianSystems.Rossland.bc.ca>
Indexed By Thread Previous: Re: Recent developments
From: Bryan Fullerton <bryanf@samurai.com>
Next: Re: Recent developments
From: Brock Rozen <brozen@torah.org>

Google
 
Search Internet Search www.greatcircle.com