amavis-user ML guidelines

Be considerate of other subscribers on the mailing list.

• Plain text, 72 characters per line
  Many subscribers read their mail on text-based mailers (mail(1), emacs) and they find HTML-formatted messages, or lines that stretch beyond 72 characters often unreadable.
• Do your homework before you post
  If you have an installation question, make sure that you have read the relevant documents such as the README and README.* text files in the top level directory of the source distribution. The mailing list archive is also a valuable resource.
• Include a useful Subject line
  Including a relevant Subject in the message will ensure that more people actually read what you've written. Also, avoid Subject lines with excessive capitalization.
• Trim your signature
  Keep the signature lines at the bottom of your mail to a reasonable length. Posts are rarely critical enough to warrant a PGP signature, and those automatic address cards are merely annoying.
• Trim your replies
  Only quote those parts of older emails that are relevant for your reply. Specifically, please refrain from adding your reply at the top of the message you're replying to. This will avoid situations where the N-th message in a thread has N copies of personal signatures and N copies of the list signature.
• Stay on topic
  Please keep the subject of the post relevant to users of AMaViS.
• email address
  Please post with the email address you're subscribed to.
• Unwanted MIME-types will be blocked
  Mails with Content-Type: [.*multipart | .*mixed | .*rich ] will be held for approval due to a "suspicious header". Those mails will be later approved on a case-by-case basis. Once again, please send mails as plain ASCII text (not HTML or Rich Text)!

The active AMaViS development team is quite small. To make sure that all problem reports can be processed efficiently, please provide all necessary information in the initial report:

• version of amavis
• version of MTA
• MTA config details
• log file evidence
• other useful information, depending on the nature of the problem (OS, AV software, configure output etc.)

If you use the SF BugTracker and you do not have a SF account (i.e. you're posting as "nobody") please provide a valid eMail address so we're able to contact you via email if nacessary.

Please do not send private email to the AMaViS developers. Even if you think the request or information is hardly relevant for the mailing list, others might find it useful.

Translate this page to  Chinese (Simplified) French German Italian Japanese Korean Portuguese Spanish