Re: WELCOME to suse-amd64@suse.com

On Wednesday 05 April 2006 12:10, suse-amd64-help@suse.com wrote:

Hi! This is the ezmlm program. I'm managing the suse-amd64@suse.com mailing list.

I'm working for my owner, who can be reached at suse-amd64-owner@suse.com.

Acknowledgment: I have added the address

bhargavi_karanam@infosys.com

to the suse-amd64 mailing list.

Welcome to suse-amd64@suse.com!

Please save this message so that you know the address you are subscribed under, in case you later want to unsubscribe or change your subscription address.

To unsubscribe, send a message to:

If you ever want to unsubscribe this address from another address you can email the custom address in the List-Unsubscribe header.

Before posting, please take a moment to read to read the following frequently asked questions. If you plan on participating in any off-topic discussions that might arise you may want to also subscribe to suse-ot by emailing

and following the instructions.

Please do not send test messages to the list -- it's annoying and rude. Instead, use our test list. Send an email to

and reply to the confirmation request you will receive (just like you did to subscribe to suse-amd64). To unsubscribe, send an email to

or do nothing...you'll be automatically unsubscribed within 24 hours. The list also has a small FAQ explaining the most common posting problems. There's no need to subscribe to the test list to see it, just email test-list-faq@suse.com.

Q1. What is the suse-amd64 mailing list? A1. A general list about running SuSE Linux on the AMD-64 platforms.

Q2. What is appropriate content for the list? A2. Technical discussions related to the above.

Q3. What is not appropriate content for the list? A3. Commercial postings of any kind, job postings, non-computer/Linux related material.

Q4. How can I retrieve the FAQ? A4. Send an email to suse-amd64-faq@suse.com

Q5. Can I send attachments to the list? A5. The short answer is 'no', you can't but see the FAQ more details.

Q6. Are there archives of the list? A6. Yes, http://lists.suse.com/archive/suse-amd64/ Currently, they are not searchable.

Q7. Why do my replies go to the original poster and not the list? A7. There is a more complete answer in FAQ, but the short answer is that it's better this way. Trust us on this one, please.

Q8. Can I get the list in digest form? A8. Not from us. There's a much more complete discussion about this in the FAQ as well.

Q9. How do I pause deliveries from the list while I'm on vacation? A9. You unsubscribe before you leave and resubscribe when you return.

Q10. How do I contact a human regarding a problem I'm having with the list? A10. Send an email to suse-amd64-owner@suse.com

--- Administrative commands for the suse-amd64 list ---

I can handle administrative requests automatically. Please do not send them to the list address! Instead, send your message to the correct command address:

For help and a description of available commands, send a message to:

To subscribe to the list, send a message to:

To remove your address from the list, just send a message to the address in the ``List-Unsubscribe'' header of any list message. If you haven't changed addresses since subscribing, you can also send a message to:

For addition or removal of addresses, I'll send a confirmation message to that address. When you receive it, simply reply to it to complete the transaction.

If you need to get in touch with the human owner of this list, please send a message to:

Please include a FORWARDED list message with ALL HEADERS intact to make it easier to help you.

--- Enclosed is a copy of the request I received.

Return-Path: Received: (qmail 16364 invoked from network); 5 Apr 2006 06:40:32 -0000 Received: from unknown (HELO Relay1.suse.de) (195.135.221.8) by 0 with SMTP; 5 Apr 2006 06:40:32 -0000 Received: from Relay1.suse.de (localhost [127.0.0.1]) by Relay1.suse.de (Postfix) with ESMTP id A93126957D for ; Wed, 5 Apr 2006 08:40:32 +0200 (CEST) Received: from Relay1.suse.de ([127.0.0.1]) by Relay1.suse.de (Relay1 [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id 03260-19 for ; Wed, 5 Apr 2006 08:40:32 +0200 (CEST) Received: from mx1.suse.de (ns1.suse.de [195.135.220.2]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by Relay1.suse.de (Postfix) with ESMTP id 5AACD61A13 for ; Wed, 5 Apr 2006 08:40:32 +0200 (CEST) Received: from Kecgate06.infosys.com (kecgate06.infosys.com [61.95.162.82]) by mx1.suse.de (Postfix) with ESMTP id 2FC6BEDBC for ; Wed, 5 Apr 2006 08:40:30 +0200 (CEST) Received: from indhubbhs01.ad.infosys.com ([192.168.200.81]) by Kecgate06.infosys.com with InterScan Messaging Security Suite; Wed, 05 Apr 2006 12:10:03 +0530 Received: from BLRKECMSG04.ad.infosys.com ([172.25.213.134]) by indhubbhs01.ad.infosys.com with Microsoft SMTPSVC(6.0.3790.1830); Wed, 5 Apr 2006 12:09:51 +0530 Received: from BLRKECOWA01.ad.infosys.com ([192.168.200.65]) by BLRKECMSG04.ad.infosys.com with Microsoft SMTPSVC(6.0.3790.1830); Wed, 5 Apr 2006 12:09:29 +0530 Received: from myshec44234d.ad.infosys.com ([172.22.10.39]) by BLRKECOWA01.ad.infosys.com with Microsoft SMTPSVC(6.0.3790.1830); Wed, 5 Apr 2006 12:09:28 +0530 From: Bhargavi Organization: Infosys To: suse-amd64-sc.1144218924.fohcapnkbokofonoopfe-bhargavi_karanam=inf@suse.de, osys.com@suse.com Subject: Re: confirm subscribe to suse-amd64@suse.com Date: Wed, 5 Apr 2006 12:10:10 +0530 User-Agent: KMail/1.8.2 References: <1144218924.11210.ezmlm@suse.com> In-Reply-To: <1144218924.11210.ezmlm@suse.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200604051210.10609.bhargavi_karanam@infosys.com> X-OriginalArrivalTime: 05 Apr 2006 06:39:28.0880 (UTC) FILETIME=[B04E9700:01C6587B] X-Virus-Scanned: by amavisd-new at Relay1.suse.de X-Spam-Status: No, hits=0.2 tagged_above=-20.0 required=5.0 tests=BAYES_50, DNS_FROM_RFC_ABUSE X-Spam-Level:

On Wednesday 05 April 2006 12:05, suse-amd64-help@suse.com wrote:

...

Hi! This is the ezmlm program. I'm managing the suse-amd64@suse.com mailing list.

I'm working for my owner, who can be reached at suse-amd64-owner@suse.com.

To confirm that you would like

bhargavi_karanam@infosys.com

added to the suse-amd64 mailing list, please send an empty reply to this address:

suse-amd64-sc.1144218924.fohcapnkbokofonoopfe-bhargavi_karanam=infosys.co m@ suse.com

Usually, this happens when you just hit the "reply" button. If this does not work, simply copy the address and paste it into the "To:" field of a new message.

or click here: mailto:suse-amd64-sc.1144218924.fohcapnkbokofonoopfe-bhargavi_karanam=in fo sys.com@suse.com

This confirmation serves two purposes. First, it verifies that I am able to get mail through to you. Second, it protects you in case someone forges a subscription request in your name.

--- Administrative commands for the suse-amd64 list ---

I can handle administrative requests automatically. Please do not send them to the list address! Instead, send your message to the correct command address:

For help and a description of available commands, send a message to:

To subscribe to the list, send a message to:

To remove your address from the list, just send a message to the address in the ``List-Unsubscribe'' header of any list message. If you haven't changed addresses since subscribing, you can also send a message to:

For addition or removal of addresses, I'll send a confirmation message to that address. When you receive it, simply reply to it to complete the transaction.

If you need to get in touch with the human owner of this list, please send a message to:

Please include a FORWARDED list message with ALL HEADERS intact to make it easier to help you.

--- Enclosed is a copy of the request I received.

Return-Path: Received: (qmail 11173 invoked from network); 5 Apr 2006 06:35:24 -0000 Received: from unknown (HELO Relay2.suse.de) (195.135.221.8) by 0 with SMTP; 5 Apr 2006 06:35:24 -0000 Received: from Relay2.suse.de (localhost [127.0.0.1]) by Relay2.suse.de (Postfix) with ESMTP id 474A36A845 for ; Wed, 5 Apr 2006 08:35:24 +0200 (CEST) Received: from Relay2.suse.de ([127.0.0.1]) by Relay2.suse.de (Relay2 [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id 05540-05 for ; Wed, 5 Apr 2006 08:35:24 +0200 (CEST) Received: from mx1.suse.de (ns1.suse.de [195.135.220.2]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by Relay2.suse.de (Postfix) with ESMTP id 0AFFB6A832 for ; Wed, 5 Apr 2006 08:35:23 +0200 (CEST) Received: from turing.suse.de (turing.suse.de [195.135.220.3]) by mx1.suse.de (Postfix) with ESMTP id D2962EDBC for ; Wed, 5 Apr 2006 08:35:23 +0200 (CEST) Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Content-Type: text/plain MIME-Version: 1.0 X-Mailer: MIME::Lite 2.117 (F2.71; T0.16; A1.47; B2.12; Q2.03) Date: Wed, 5 Apr 2006 06:35:23 UT From: bhargavi_karanam@infosys.com To: suse-amd64-subscribe@suse.com Message-Id: <20060405063523.BA3AB2EA01@turing.suse.de> X-Virus-Scanned: by amavisd-new at Relay2.suse.de X-Spam-Status: Yes, hits=5.3 tagged_above=-20.0 required=5.0 tests=BAYES_50, DNS_FROM_RFC_ABUSE, EMPTY_MESSAGE, MISSING_SUBJECT, NO_REAL_NAME X-Spam-Level: ***** Subject: SPAM: X-Spam-Flag: YES

**************** CAUTION - Disclaimer ***************** This e-mail contains PRIVILEGED AND CONFIDENTIAL INFORMATION intended solely for the use of the addressee(s). If you are not the intended recipient, please notify the sender by e-mail and delete the original message. Further, you are not to copy, disclose, or distribute this e-mail or its contents to any other person and any such actions are unlawful. This e-mail may contain viruses. Infosys has taken every reasonable precaution to minimize this risk, but is not liable for any damage you may sustain as a result of any virus in this e-mail. You should carry out your own virus checks before opening the e-mail or attachment. Infosys reserves the right to monitor and review the content of all messages sent to or from this e-mail address. Messages sent to or from this e-mail address may be stored on the Infosys e-mail system. ***INFOSYS******** End of Disclaimer ********INFOSYS***