Re: [Cooker] Reply-to test (ignore)
I've emptied mine too and it seems to fix the prob Eugenio Diaz-Maldonado wrote: This email was sent from netscape with the reply-to field empty to test for a probable problem in the list. Please ignore. -- Eugenio Diaz, BSEE/BSCE Linux Engineer [EMAIL PROTECTED] -- ~~ Alwyn Schoeman Systems Engineer Prism Secure Solutions
Re: [Cooker] Reply-to test (ignore)
Confirmed. There is a bug or misconfiguration with the cooker list. It should **always** re-write the "Reply-To" field to the cooker list email address. The field is not re-written when it was already set by the email client; this is wrong! Please check the previous two test messages I sent to the list. This has caused some of my beautifully long ;-) replies not to be posted several times in the past :- Please solve. --- Alwyn Schoeman [EMAIL PROTECTED] wrote: I've emptied mine too and it seems to fix the prob Eugenio Diaz-Maldonado wrote: This email was sent from netscape with the reply-to field empty to test for a probable problem in the list. Please ignore. -- Eugenio Diaz, BSEE/BSCE Linux Engineer [EMAIL PROTECTED] -- ~~ Alwyn Schoeman Systems Engineer Prism Secure Solutions = Eugenio Diaz, BSEE/BSCE Linux Engineer [EMAIL PROTECTED] __ Do You Yahoo!? Bid and sell for free at http://auctions.yahoo.com
Re: [Cooker] Reply-to test (ignore)
I do not understand what you are trying to say. My point is that using when I post a message to the list, any message in reply to my message **should always** go to the list by default. This is not happening when ever the original post has the "Reply-To" field set. In this case sympa does not re-write the field, and when somebody reply thinking it would go to the list, it really goes to where ever the original poster had set in the "Reply-To" field. I do not understand why you are suggesting things about procmail, etc. which has nothing to do, since this is not a **client** side problem; it is a list or server side problem. Actually I don't use a "Reply-To" field, and the problems arises when I want to reply to the posts of some other user that does use the field; and since I can not control how other people configure their email clients (much less ask them to change their email client configuration just so the list works as it "should"), it is clearly evident that it is a server side problem. If you have sympa well configured as per it's documentation, to re-write the field in every case, then there must be a bug in sympa, or some other place. --- Chmouel Boudjnah [EMAIL PROTECTED] wrote: Eugenio Diaz [EMAIL PROTECTED] writes: Confirmed. There is a bug or misconfiguration with the cooker list. It should **always** re-write the "Reply-To" field to the cooker list email address. The field is not re-written when it was already set by the email client; this is wrong! Please check the previous two test messages I sent to the list. This has caused some of my beautifully long ;-) replies not to be posted several times in the past :- i don't put a Reply-To: field and i have in one of my headers : --=-=-= From: Chmouel Boudjnah [EMAIL PROTECTED] Organisation: MandrakeSoft Date: 03 Nov 1999 17:02:13 +0100 In-Reply-To: Alwyn Schoeman's message of "Wed, 03 Nov 1999 10:46:23 +0200" X-Gnus-Mail-Source: file:/var/spool/mail/chmou Message-Id: [EMAIL PROTECTED] User-Agent: Gnus/5.070096 (Pterodactyl Gnus v0.96) XEmacs/21.1 (Biscayne) Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Reply-To: [EMAIL PROTECTED] X-Loop: [EMAIL PROTECTED] X-Sequence: 3705 Precedence: list --=-=-= so the field is set and the configuration of list i have : reply_to list and documentation of sympa say : 3.3.8 Reply-to parameter reply-to sender | list This parameter indicates whether the Reply-To: field should point to the sender of the message (sender) or to the list itself (list). If this parameter is not specified, the Reply-To: field is not modified by Sympa. Note: it is unadvisable to change this field, especially to point to the list. Experience demonstrates that numerous users, thinking they are responding to the sender, send private messages to a list. This can lead to an embarrassing situation. maybe if you use procmail you can set this : :0 fhw * ^Subject: \[Cooker\]* | formail -i "Reply-To: [EMAIL PROTECTED]" in your ~/.procmailrc, but i'm sure the Reply-To: is always set. --Chmouel = Eugenio Diaz, BSEE/BSCE Linux Engineer [EMAIL PROTECTED] __ Do You Yahoo!? Bid and sell for free at http://auctions.yahoo.com
Re: [Cooker] Reply-to test (ignore)
On Wed, Nov 03, 1999 at 08:43:04AM -0800, Eugenio Diaz wrote: I do not understand what you are trying to say. My point is that using when I post a message to the list, any message in reply to my message **should always** go to the list by default. This is not happening when ever the original post has the "Reply-To" field set. In this case sympa does not re-write the field, and when somebody reply thinking it would go to the list, it really goes to where ever the original poster had set in the "Reply-To" field. I do not understand why you are suggesting things about procmail, etc. which has nothing to do, since this is not a **client** side problem; it is a list or server side problem. Actually I don't use a "Reply-To" field, and the problems arises when I want to reply to the posts of some other user that does use the field; and since I can not control how other people configure their email clients (much less ask them to change their email client configuration just so the list works as it "should"), it is clearly evident that it is a server side problem. If you have sympa well configured as per it's documentation, to re-write the field in every case, then there must be a bug in sympa, or some other place. Sorry, but Chmouel and Sympa's documentation are right here. It would be nice if Reply-To: was set to list, but unfortunately, once in a while, someone comes with a badly configured autoresponder, or autovacation responder, and then things get *really* ugly. I mean, hundreds of messages add up until the list manager wakes up (usually someone calls him on the phone) hand kill the broken subscription. Of course, you cant always try to be smart and add filters to you mail list manager, but eventually things will blow up anyway. I've experienced such problems 2 or 3 times before and I can tell you it's really embarrassing, esp. for the list admin. S. -- Stéfane Fermigier, Tel: 06 63 04 12 77 (mobile). www.linbox.com - www.aful.org - www.linux-center.org. "In its pure form, Pascal is a toy language, suitable for teaching but not for real programming." Brian Kernighan.
Re: [Cooker] Reply-to test (ignore)
--- Stefane Fermigier [EMAIL PROTECTED] wrote: On Wed, Nov 03, 1999 at 08:43:04AM -0800, Eugenio Diaz wrote: I do not understand what you are trying to say. ... case, then there must be a bug in sympa, or some other place. Sorry, but Chmouel and Sympa's documentation are right here. It would be nice if Reply-To: was set to list, but unfortunately, once in a while, someone comes with a badly configured autoresponder, or autovacation responder, and then things get *really* ugly. I mean, hundreds of messages add up until the list manager wakes up (usually someone calls him on the phone) hand kill the broken subscription. I do not get it. Could you explain exactly why a vacation autoresponder would cause hundreds of emails to the list? = Eugenio Diaz, BSEE/BSCE Linux Engineer [EMAIL PROTECTED] __ Do You Yahoo!? Bid and sell for free at http://auctions.yahoo.com
Re: [Cooker] Reply-to test (ignore)
--- Stefane Fermigier [EMAIL PROTECTED] wrote: On Wed, Nov 03, 1999 at 11:41:12AM -0800, Eugenio Diaz wrote: --- Stefane Fermigier [EMAIL PROTECTED] wrote: On Wed, Nov 03, 1999 at 08:43:04AM -0800, Eugenio Diaz wrote: I do not understand what you are trying to say. ... case, then there must be a bug in sympa, or some other place. Sorry, but Chmouel and Sympa's documentation are right here. It would be nice if Reply-To: was set to list, but unfortunately, once in a while, someone comes with a badly configured autoresponder, or autovacation responder, and then things get *really* ugly. I mean, hundreds of messages add up until the list manager wakes up (usually someone calls him on the phone) hand kill the broken subscription. I do not get it. Could you explain exactly why a vacation autoresponder would cause hundreds of emails to the list? Someone send a message to the list. The (badly configured) autoresponder replies to the list. The (badly configured) autoresponder replies to its reply to the list. The (badly configured) autoresponder replies to its reply to its reply to the list. ... Ok, but I still think that this is very unlikely, and the convenience of having all of your replies posted, far out weight the risk of this happening. = Eugenio Diaz, BSEE/BSCE Linux Engineer [EMAIL PROTECTED] __ Do You Yahoo!? Bid and sell for free at http://auctions.yahoo.com
