Re: postfix-users "README-before-posting"

From: Wietse Venema (no email)
Date: Sat Dec 01 2001 - 21:03:39 EST


No-one can post to postfix-users before they have subscribed.

Every new subscribed gets a welcome message that stresses the
importance of including logging and "postconf -n" output.

Hardly anyone follows the instructions.

Maybe majordomo should be modified to include a little IQ test.

        Wietse

Meng Weng Wong:
> On Sat, Dec 01, 2001 at 10:30:31AM +0100, Ralf Hildebrandt wrote:
> | Official postfix-users mantra: post FULL log information when asking
> | questions, since most of us have no ESP abilities.
>
> The courier-imap FAQ contains a lengthy admonishment --- the
> sort of thing that should go without saying, but doesn't.
> Maybe we could borrow from it for the Postfix FAQ.
>
> Asking for help on the courier-users mailing list
>
> A: The courier-users mailing list should be the first place to look
> for assistance with resolving any issues. You only need to observe a
> few simple rules in order to increase your chances of getting a quick
> and helpful response:
> 1. Subscribe to the mailing list before you ask any questions. If you
> are not subscribed, you will not receive any replies that are
> mailed to the list only.
> 2. Do not send HTML E-mail messages, unless you want many people to
> automatically delete them, unread. If you are using MS-Outlook,
> turn off HTML formatting before sending mail to the list.
> 3. Before sending a question, check it to make sure that your message
> does not contain the words "doesn't work." Saying only that
> something doesn't work is not very useful in trying to analyze the
> problem. If something isn't working correctly, merely stating it
> will not make much progress. Be sure to always include in your
> messages:
> + The contents of any related configuration files.
> + What happens, exactly, that makes you think that something
> isn't working right.
> + The contents of your system log file (syslog, or
> /var/log/messages).
> + Be sure to describe any non-standard modifications to the
> operating system you're using, such as a kernel hacked with
> one of several varieties of the OpenWall patch, or
> filesystema mounted with a no-suid option. Many problems turn
> out to be unintentional conflicts with various unexpected
> side-effects of these custom modifications (but not after
> wasting a great deal of time chasing ghosts).
> 4. Do not send large attachments (over 10K bytes is a rule of thumb),
> to the list. Put it somewhere - on the web or on a FTP server -
> and include a link in your message instead.
> 5. Always mention what you've already tried to do in order to fix the
> problem. People are more likely to help you if they know that
> you've made some effort to figure it out by yourself, and you are
> only asking for help after running into a dead end.
> 6. If you do not get an answer in one hour, don't resend your
> message. If people open their mailbox and see five copies of the
> same message, they'll be ignored. Have patience. Either wait some
> more, or accept it as a fact of life. Try again to figure out the
> answer on your own. You can certainly ask again after you've tried
> to figure it out once more, and still didn't get anywhere. Don't
> just write again, and simply say that it still doesn't work.
> Provide some additional information, showing what else you've
> tried to do, to no avail.
>
> -
> To unsubscribe, send mail to with content
> (not subject): unsubscribe postfix-users
>
>

-
To unsubscribe, send mail to with content
(not subject): unsubscribe postfix-users








Hosted Email Solutions

Invaluement Anti-Spam DNSBLs



Powered By FreeBSD   Powered By FreeBSD