From: Eric Hodel Date: 2012-06-19T07:00:28+09:00 Subject: How to Unsubscribe On Jun 18, 2012, at 11:22, Cathy Alomari wrote: > DITTO! Very hard to get off the list. Tried several times. Someone even butted in with instructions with proof that he/she was unsubscribed. Did exactly what the instructions said, and still here. > > I'm sure that although I've responded to this email - I'll never be unsubscribed. I have even considered changing my email address to get OFF the list I just unsubscribed, confirmed I was unsubscribed, then resubscribed. Here's what I did: Send an email to ruby-talk-ctl@ruby-lang.org with a body of unsubscribe. It looked like this: > From: Eric Hodel > To: ruby-talk-ctl@ruby-lang.org > Subject: > > unsubscribe I received an email from ruby-talk-ctl: > From: ruby-talk-admin@ruby-lang.org > Subject: Unsubscribe confirmation request > To: drbrain@segment7.net > > >>> unsubscribe > unsubscribe-confirm 2012061906284781468055226 drbrain segment7.net > > Please reply this mail to confirm your unsubscribe request > and send this to ruby-talk-ctl@ruby-lang.org > If confirmed, you are removed from MAILING LIST . > > --ruby-talk@ruby-lang.org, Be Seeing You! > […] I replied to this message, including the unsubscribed text in the body: > From: Eric Hodel > To: ruby-talk-ctl@ruby-lang.org > Subject: Re: Unsubscribe confirmation request > > On Jun 18, 2012, at 14:28, ruby-talk-admin@ruby-lang.org wrote: > > > > >>>> unsubscribe > > unsubscribe-confirm 2012061906284781468055226 drbrain segment7.net > > > > Please reply this mail to confirm your unsubscribe request > > and send this to ruby-talk-ctl@ruby-lang.org > > If confirmed, you are removed from MAILING LIST . > > > > --ruby-talk@ruby-lang.org, Be Seeing You! > […] I received a response saying I was unsubscribed: > From: ruby-talk-admin@ruby-lang.org > Subject: Unsubscribe and confirmation result > To: drbrain@segment7.net > > > >>> unsubscribe-confirm 2012061906284781468055226 drbrain segment7.net > set UNSUBSCRIBE-CONFIRM => BYE > BYE [drbrain@segment7.net] accepted. > change member and recipient lists > > > --ruby-talk@ruby-lang.org, Be Seeing You! > […] I then sent an email to ruby-talk@ruby-lang.org which bounced: > From: ruby-talk-admin@ruby-lang.org > To: drbrain@segment7.net > Subject: You drbrain@segment7.net are not member (ruby-talk ML) > > You are not a member of this mailing list . > > If you want to know the general guide of this list, please send an email > with the body (case-insensitive): > > # guide > > to the address > > ruby-talk-ctl@ruby-lang.org > > Note that the mail should not be encoded in base64. Hrm, this note: ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ seems pertinent to unsubscribe problems. I think Chad Perrin is on to something in [ruby-talk:396612]: > This may be a dumb question, but . . . did you use HTML email to reply? Sending text/html or multipart/alternative email when talking to robots is likely going to be unproductive. Additionally, for technical mailing lists it's generally recommended that you stick to text/plain email so that code samples, example output and whatnot are all properly formatted. I'm not the only person who has unsubscribed (and resubscribed) with no problem today. If you are still having problems unsubscribing from this list the fault is likely in your mail client, not in the mailing list. I also note that you continually say "it didn't work" without showing what you sent the ruby-talk-ctl and what ruby-talk-ctl sent to you. Like any problem you want help fixing on this mailing list, saying "it didn't work" without showing exactly what "it" is and showing exactly how "it" "didn't work" we'll be unable to help you. Like I have shown above, please show: Your email to ruby-talk-ctl@ruby-lang.org including From, To and Subject headers and the body. The confirmation request mail from ruby-talk-ctl@ruby-lang to you including the same headers and body. Your confirmation mail responding to ruby-talk-ctl@ruby-lang.org including the same headers and body. The unsubscribe confirmation mail from ruby-talk-ctl@ruby-lang.org including the same headers and body. (That's four emails with From, To, Subject and body)