Hi! This is the ezmlm program. I'm managing the
email@example.com mailing list.
I'm working for my owner, who can be reached
FAQ - Frequently asked questions of the firstname.lastname@example.org list.
Note: This FAQ mainly deals with list-specific issues. Togan
Muftuoglu maintains an unofficial FAQ for this that can be
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:
Alternatively, you can prepend your search on Google.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: email@example.com" 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
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
New! Even Sourceforge has turned to the dark side:
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
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
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 firstname.lastname@example.org.
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
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
email@example.com 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: firstname.lastname@example.org. Send an email to
email@example.com and read the information you'll
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 firstname.lastname@example.org to learn more about the archival commands
but if you wanted to retrieve message number 10000 from the archive
just send an email to
Even better, get the whole thread with an email to
If you have questions about this please email email@example.com,
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
firstname.lastname@example.org 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
For example, if I wanted to subscribe email@example.com to #l# I would
send an email to
Of course, firstname.lastname@example.org 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:
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
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 email@example.com.
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
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.
| sed 's/\[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:
Further questions about licensing and maintenance should be addressed to
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 firstname.lastname@example.org 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:
To remove your address from the list, send a message to:
Send mail to the following for info and FAQ for this list:
To get message 12 from the archive, send a message to:
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 "email@example.com", just add a hyphen and your
address (with '=' instead of '@') after the command word:
To stop subscription for this address, mail:
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
firstname.lastname@example.org. Please be patient, my owner is a
lot slower than I am ;-)
--- Enclosed is a copy of the request I received.
Received: (qmail 19921 invoked from network); 5 Apr 2004 14:41:03 -0000
Received: from unknown (HELO hermes.suse.de) (18.104.22.168)
by 0 with SMTP; 5 Apr 2004 14:41:03 -0000
Received: from scanhost.suse.de (scanhost.suse.de [10.0.0.5])
by hermes.suse.de (Postfix) with ESMTP id 512B71AB71
for <email@example.com>; Mon, 5 Apr 2004 16:41:03 +0200 (CEST)
Received: by scanhost.suse.de (Postfix, from userid 0)
id 482841E7C2; Mon, 5 Apr 2004 16:41:03 +0200 (CEST)
Received: from Cantor.suse.de (ns.suse.de [22.214.171.124]) (using TLSv1
with cipher EDH-RSA-DES-CBC3-SHA (168/168 bits)) (No client
certificate requested) by hermes.suse.de (Postfix) with ESMTP id
C3CBB1AE99 for <firstname.lastname@example.org>; Mon, 5 Apr 2004 16:37:41
Received: from suse.com (zux006-040-128.adsl.green.ch [126.96.36.199]) by
Cantor.suse.de (Postfix) with SMTP id EA84C3EEB7A for
<email@example.com>; Mon, 5 Apr 2004 16:35:38 +0200 (CEST)
Date: Mon, 5 Apr 2004 16:36:57 +0200
Content-Type: text/plain; charset="us-ascii"
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
read the details.
[the SUSE virus scanner removed an attachment of type application/x-zip-compressed which had a name of bill.zip]
[if you need the message in its original form including all attachments, please ask the SENDER for a version free of viruses]