[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

ezmlm response



Hi! This is the ezmlm program. I'm managing the
suse-linux-e@xxxxxxxx mailing list.

I'm working for my owner, who can be reached
at suse-linux-e-owner@xxxxxxxxx

FAQ - Frequently asked questions of the suse-linux-e@xxxxxxxx list.

Note: This FAQ mainly deals with list-specific issues.  Togan
Muftuoglu maintains an unofficial FAQ for this that can be
found here:
	http://dinamizm.ath.cx
	Mirrors:
	http://toganm.tripod.com
	http://susefaq.sourceforge.net
	http://www.smaug42.com/susefaq
	http://www.bmtsolutions.com/suse_faq/index.html
	http://www.jon.fl.net.au/suse/unofficial-faq
	http://www.e-vega.info/mirrors/suse/
	http://www.ods.co.cr/mirrors/suse
	http://www.netbulans.com/susefaq


Thanks Togan!

Q1.  Why don't you provide searchable archives of this list?

A1.  The archives are far too large to be indexed by us.  Very
     complete archives that are searchable can be found here:
	http://www.netsys.com/suse-linux-e/index.html
	http://marc.theaimsgroup.com/
     Alternatively, you can prepend your search on Google.com
     with
        lists site:lists.suse.com
     E.g., to search for "lilo 1024" you would type
        lists site:lists.suse.com lilo 1024
     into the search field.


Q2.  Why do my replies go to the original poster and not the list?
A2.  We do not "munge" the mail headers by inserting
     a "Reply-To: suse-linux-e@xxxxxxxx" because it makes it more
     difficult subscribers to handle the mail the way they want to.
     Your mail client probably has a "reply" function as well as a 
     "reply to all" or "reply to list" one; Please use the latter if
     you want you message to go to the list and not just to the
     original poster.

     Also, please don't complain about this on the list, it has
     been discussed many, many, many times in the past already.

     For background information see
     http://www.unicom.com/pw/reply-to-harmful.html

     New!  Even Sourceforge has turned to the dark side:
       http://sourceforge.net/docman/display_doc.php?docid=6693&group_id=1

Q3.  How to I get the list in digest form instead of separate emails?
A3.  We don't offer digested lists for several reasons:
	1) Most of our lists (especially this one) are far to large to
	   make digests useful.  Are you really going to read an ~500K
	   email once per day?  Yes, it's the same amount that you 
	   would receive on as separate mail but it's easy to delete
	   or skip messages that don't interest you in that case; it's
	   not with a digest.

	2) In our experience, digests tend to decrease the quality of
	   list postings.  They do this by encouraging the sorts of 
	   behaviors that are often considered rude or in poor 
	   'netiquette': replying to mail with the incorrect subject
	   header or other headers that make it impossible for threaded
	   mail clients to work properly, replying to mail without
	   reading the entire thread first, and probably more.  Of 
	   course, people who do things like this are often the cause
	   of huge flame wars about proper netiquette that can go on for
	   days, often with the result of having very helpful and 
	   knowledgeable people leaving the list in disgust.

	3) Usually, when people request digests what they are really
	   asking for is a way to keep the list mail from flooding
	   their mailbox and making it harder to find and read non-list
	   mail.  This is a valid concern and one that is best handled
	   with mail filtering, not digests.  If your system is 
	   configured to use procmail to deliver mail locally (SuSE's
	   postfix and sendmail packages are) all you need to do is
	   create a file in your home directory named '.procmailrc' that
	   contains something like the following:
	   
		MAILDIR=$HOME/Mail   # where do you keep your mail?
		DEFAULT=$MAILDIR/inbox  # what's you default mail box?
		
		# if mail is from list put it in $MAILDIR/foo
 		:0
		* ^X-Mailinglist::.*suse-linux-e
		$MAILDIR/foo

	   Everything else will be placed in $DEFAULT.  By default,
	   procmail creates a normal mbox formatted mail box so if you
	   want to copy the file somewhere (e.g., to a PDA) you only
	   need to, in the above example, copy $MAILDIR/sle.  Of course,
	   procmail is capable of much more than what this simple example
	   shows, so please read procmailrc(5) and procmailex(5) for more
	   information.

Q4.  Can I send attachments to the list?
A4.  The short answer is 'no'.  We may strip attachments that
     contain something other than plain text and bounce email
     that only contains attachments.  Likewise, HTML email is
     *strongly* discouraged and may be blocked as well.

Q5.  How do I contact a human regarding problems with list?
A5.  Email suse-linux-e-owner@xxxxxxxxx

Q6.  Why to you restrict postings to subscribers?
A6.  suse-linux-e is a high-traffic mailing list with a huge number of
     subscribers; because of this we want to limit crossposting
     and SPAM.

Q7.  I receive the list without problems, but whenever I try to
     post or retrieve the archives my mail bounces with a warning
     that only subscribers are allowed to post.

A7.  Most likely your envelope and header From addresses are
     different.  There's nothing necessarily wrong with this
     (it's quite common on large domains, for example) but it
     does make things a little more complicated.  We use the
     envelope From for authentication, not the header From.  If
     you don't know what any of this means then email
     ml-admin@xxxxxxxx and ask them to subscribe you.
     Also, *please* do not send "test" messages to the list.  It's
     very annoying and rude; we have a special list just for this
     purpose: test-list@xxxxxxxxx  Send an email to
     test-list-subscribe@xxxxxxxx and read the information you'll
     receive.

Q8.  I just received a strange message from something called
     ezmlm about bouncing messages?  What's going on?

A8.  It means that one or more messages from the list to you were
     unable to be delivered within the lifetime of the message (currently
     3 days).  While the message is mainly for your information in that
     gives the message numbers of the messages you missed in case you
     want to retrieve them from the archive, it is also used as a probe
     to see if your address is still valid.  If this message is undeliverable
     for 3 days then your address will be removed from the list.

     Email suse-linux-e-help@xxxxxxxx to learn more about the archival commands
     but if you wanted to retrieve message number 10000 from the archive
     just send an email to
	suse-linux-e-get.10000@xxxxxxxx
     Even better, get the whole thread with an email to
        suse-linux-e-thread.10000@xxxxxxxx
     If you have questions about this please email suse-linux-e-owner@xxxxxxxx,
     not the list.

 
Q9.  I'm wondering if Linux is "better" than Windows.  Should I post
     ask on the list?
A9.  Please don't.  It's an extremely tired, overdiscussed topic and
     rarely results in anything approaching a useful conclusion.
     Questions like "I need to do BLAH and in Windows I could do it
     with the BLAH program.  How do I do that in Linux?" are entirely
     appropriate, of course.  We have now have a list specifically
     devoted to off-topic postings like this: email 
     suse-ot-subscribe@xxxxxxxx to subscribe

Q10. How do I pause deliveries from the list while I'm on vacation?
A10. You unsubscribe before you leave and resubscribe when you return.
     Please understand that you may be unsubscribed if you have an
     improperly configured auto-responder (e.g., vacation(1)) that is
     sending messages to the list or the other subscribers.

Q11. How do I post from multiple addresses?
A11. We don't allow aliased subscriptions in the interest of spam
     prevention.  If you absolutely must be able to post from multiple
     addresses you can subscribe both addresses and use procmail (see
     Q3 for more details) to automatically delete one copy by sending
     it to /dev/null.  To subscribe an address that is different from the
     address you are sending mail from, send mail to
        suse-linux-e-subscribe-address=otherdomain.tdl@xxxxxxxx
     For example, if I wanted to subscribe john@xxxxxxxx to #l# I would
     send an email to
        suse-linux-e-subscribe-john=acme.com@xxxxxxxx
     Of course, john@xxxxxxxx will get a confirmation request that he'll
     need to reply to.  

Q12. Where can I get ISOs of SuSE Linux?
Q12. Here is SuSE's official statement about no-cost ISO images:
	http://sdb.suse.de/sdb/en/html/lmuelle_suselinux_internet.html 
     This page also explains how to do an installation from ftp.suse.com
     or, preferably, one of it's mirrors.

     Before starting another "SuSE should/shouldn't provide ISO like
     everyone else" thread please read through the past threads in the
     archives; they are very tiresome and most likely a waste of time
     since the people who make these sorts of decisions don't read SLE.
     A more productive way to express your opinion on the matter is to
     email feedback@xxxxxxxx

Q13. I've been accused of 'thread hijacking'!  What does that mean?
A13. You probably replied to another post as a new topic.  If you aren't
     using a threaded mail reader you may not notice how annoying this
     is but a quick scroll through the archives on
     http://lists.suse.com/archive/suse-linux-e will give you some examplesi; Look
     for threads that suddenly change subject and topic.  'Thread hijacking'
     destroys the threading in mail clients and makes archives very hard to
     use.  If you want to start a new thread, *do not* just reply-all to a
     posting you just received.  Instead, post a new email to suse-linux-e@xxxxxxxxx
     Just replying to another post and changing the subject keeps the reference
     header intact which is used (usually in combination with the subject
     header) to place the message in its context.  Better yet, use a mail client
     that has a proper 'list reply' function.


Q14. Where can I find more documentation on the SuSE firewall script?
A14. Togan Muftuoglu has written a 30+ page manual for it.  Please see
     http://sourceforge.net/project/showfiles.php?group_id=42064&release_id=116688
     and http://dinamizm.ath.cx/articles/firewall2.pdf
     Thanks Togan!

Q15. How do I remove that annoying '[SLE]' from the subjects?
A15. If you use procmail, add something like the following to your .procmailrc.
     $SLE is the mailbox that you want the list postings to be stored in.
		:0fhw
		* ^Subject:.*\[SLE\]
     		| sed 's/\[SLE\]//'
		$SLE

Q16. Can I install SuSE Linux Professional/Personal on as many machines
     as I like?  Can I make copies and give them friends or my LUG?
A16. Yes.  Be aware that some packages that we distribute in the Professional
     and Personal distributions may not be redistributed.  If in doubt about
     a particular package check to see if it's available on ftp.suse.com or
     ask on the list.  Contrary to what you may have read about YaST
     elsewhere, its sources are available and you are free to modify them
     for personal use.  

     The business products such as SLES, SLD, and the OpenExchange Server
     fall under a different license. See the following for more information:
     http://www.suse.de/us/business/products/sld/license.html

     Further questions about licensing and maintenance should be addressed to
     customer service.
    
Q17. I was being polite and prefixed the subject of my off-topic posting
     with '[OT]'.  After posting it I received a nasty message about
     the thread being blocked and that if I persist in trying to start
     off-topic threads I'll be unsubscribed and blocked from resubscribing.
     What's up with that?
A17. Sorry, we really have no choice.  We've asked nicely over the years
     for people to take their off-topic threads elsewhere in the interest
     of keeping the messages per day on SLE under 200 and, well, that
     just didn't work.  We now have a list, suse-ot, that's devoted
     solely to off-topic discussions.  That's right, all off-topic all
     the time.  Email suse-ot-subscribe@xxxxxxxx to subscribe.
     


--- Administrative commands for the suse-linux-e 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:

To subscribe to the list, send a message to:
   <suse-linux-e-subscribe@xxxxxxxx>

To remove your address from the list, send a message to:
   <suse-linux-e-unsubscribe@xxxxxxxx>

Send mail to the following for info and FAQ for this list:
   <suse-linux-e-info@xxxxxxxx>
   <suse-linux-e-faq@xxxxxxxx>

To get message 12 from the archive, send a message to:
   <suse-linux-e-get.12@xxxxxxxx>

The messages do not really need to be empty, but I will ignore
their content. Only the ADDRESS you send to is important.

You can start a subscription for an alternate address,
for example "john@xxxxxxxxxxx", just add a hyphen and your
address (with '=' instead of '@') after the command word:
<suse-linux-e-subscribe-john=host.domain@xxxxxxxx>

To stop subscription for this address, mail:
<suse-linux-e-unsubscribe-john=host.domain@xxxxxxxx>

In both cases, I'll send a confirmation message to that address. When
you receive it, simply reply to it to complete your subscription.

If despite following these instructions, you do not get the
desired results, please contact my owner at
suse-linux-e-owner@xxxxxxxxx Please be patient, my owner is a
lot slower than I am ;-)

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

Return-Path: <linux-crypto@xxxxxxxxxxxx>
Received: (qmail 20837 invoked from network); 6 May 2004 20:10:28 -0000
Received: from unknown (HELO hermes.suse.de) (195.135.221.8)
  by 0 with SMTP; 6 May 2004 20:10:28 -0000
Received: from scanhost.suse.de (scanhost.suse.de [10.0.0.5])
	by hermes.suse.de (Postfix) with ESMTP id 378E311D56
	for <suse-linux-e-faq@xxxxxxxxxxxxxx>; Thu,  6 May 2004 22:10:26 +0200 (CEST)
Received: by scanhost.suse.de (Postfix, from userid 0)
	id 2C94252A3F; Thu,  6 May 2004 22:10:26 +0200 (CEST)
Delivered-To: virus-quarantine
X-Quarantine-id: <virus-20040506-220903-14352-14>
Received: from Cantor.suse.de (ns.suse.de [195.135.220.2]) (using TLSv1
  with cipher EDH-RSA-DES-CBC3-SHA (168/168 bits)) (No client
  certificate requested) by hermes.suse.de (Postfix) with ESMTP id
  9B49368CF3 for <suse-linux-e-faq@xxxxxxxx>; Thu,  6 May 2004 22:09:01
  +0200 (CEST)
Received: from suse.com (ppp-150-196.24-151.libero.it [151.24.196.150])
  by Cantor.suse.de (Postfix) with SMTP id 4EBF156069C for
  <suse-linux-e-faq@xxxxxxxx>; Thu,  6 May 2004 22:08:53 +0200 (CEST)
From: linux-crypto@xxxxxxxxxxxx
To: suse-linux-e-faq@xxxxxxxx
Subject: hi
Date: Thu, 6 May 2004 22:08:53 +0200
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Message-Id: <20040506200853.4EBF156069C@xxxxxxxxxxxxxx>
X-AMaViS-Alert: INFECTED, message contains virus: Worm.SomeFool.Gen-2
X-Converted-To-Plain-Text: from multipart/mixed by demime 1.1d
X-Converted-To-Plain-Text: Alternative section used was text/plain

here is the document.

[the SUSE virus scanner removed an attachment of type application/octet-stream which had a name of message.pif]
[if you need the message in its original form including all attachments, please ask the SENDER for a version free of viruses]

-
Linux-crypto:  cryptography in and on the Linux system
Archive:       http://mail.nl.linux.org/linux-crypto/