Package: bugs.debian.org

Can you please stop sending users these out of the blue, without at
the same time,

1. Telling the user if his original message got thrown away or arrived
safely at its intended destination.

2. Telling the user what his original message was, and what line in it
triggered the interception.

3. Telling the user who exactly to complain too about erroneous interception.

Return-Path: <[email protected]>
Received: from m.jidanni.org (69.163.137.246:993) by jidanni5.jidanni.org
  with IMAP4-SSL; 09 Jul 2013 18:30:46 -0000
X-Spam-Checker-Version: SpamAssassin 3.4.0-r1197259-2009 (2011-11-03) on
        ps11007.dreamhostps.com
X-Spam-Level: 
X-Spam-Status: No, score=-106.3 required=1.9 tests=J_INREPLYTO,J_REFERENCES,
        RCVD_IN_DNSWL_HI,RCVD_IN_MSPIKE_H3,RCVD_IN_MSPIKE_WL,RP_MATCHES_RCVD,
        USER_IN_WHITELIST, RULESVERSION=1500228
X-Spam-Languages: en
X-Original-To: [email protected]
Delivered-To: [email protected]
Received: from homiemail-mx1.g.dreamhost.com (caiajhbdcaid.dreamhost.com 
[208.97.132.83])
        by ps11007.dreamhostps.com (Postfix) with ESMTP id 21415BC5800A
        for <[email protected]>; Tue,  9 Jul 2013 11:27:21 -0700 
(PDT)
Received: from bendel.debian.org (bendel.debian.org [82.195.75.100])
        (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
        (No client certificate requested)
        by homiemail-mx1.g.dreamhost.com (Postfix) with ESMTPS id E82EA768204
        for <[email protected]>; Tue,  9 Jul 2013 11:27:20 -0700 (PDT)
Received: by bendel.debian.org (Postfix, from userid 38)
        id 880BC3B7; Tue,  9 Jul 2013 18:27:19 +0000 (UTC)
X-Loop: [email protected]
X-Loop: [email protected]
To: [email protected]
Subject: Re: Bug#715493: [php-maint] Bug#715493: Unable to load dynamic library 
messages from cron started after upgrade
References: <caesznc6qzhlarfu6zj4n-otea8oz4wasazhsomw3lkggdg3...@mail.gmail.com>
 <[email protected]>
 <caljhhg-vtzd85zokok+7xm6bdnyttuk1prwjrkqm_lhyarx...@mail.gmail.com>
 <[email protected]>
 <caljhhg_3uut6zsa8svdgxqm6u6bxbmdqjwt+xeuo409fo4o...@mail.gmail.com>
 <[email protected]>
 <caljhhg8qjjreayodvznh0cf7kvcmtszxwgungihabcs_mw+...@mail.gmail.com> 
<[email protected]>
In-Reply-To: <[email protected]>
X-Loop: [email protected]
From: [email protected]
X-Gnus-Mail-Source: maildir:~/Maildir/cur
Message-Id: <[email protected]>
Date: Tue,  9 Jul 2013 18:27:19 +0000 (UTC)
X-getmail-retrieved-from-mailbox: INBOX
Lines: 66
Xref: jidanni5.jidanni.org mail.debianbugs:39

                        General info
                        ------------
Subscription/unsubscription/info requests should always be sent to
the -request address of a mailing list.

If a mailing list is called for example "[email protected]", then
the -request address can be inferred from this to be:
"[email protected]".

To subscribe to a mailing list, simply send a message with the word "subscribe"
in the Subject: field to the -request address of that list.

To unsubscribe from a mailing list, simply send a message with the word (you
guessed it :-) "unsubscribe" in the Subject: field to the -request address of
that list.

In the event of an address change, it would probably be the wisest to first
send an unsubscribe for the old address (this can be done from the new
address), and then a new subscribe to the new address (the order is important).

Most (un)subscription requests are processed automatically without human
intervention.

Do not send multiple (un)subscription or info requests in one mail.
Only one will be processed per mail.

NOTE: The -request server usually does quite a good job in discriminating
      between (un)subscribe requests and messages intended for the maintainer.
      If you'd like to make sure a human reads your message, make it look
      like a reply (i.e. the first word in the Subject: field should be "Re:",
      without the quotes of course); the -request server does not react to
      replies.


                        The archive server
                        ------------------
Every submission sent to this list is archived.  The size of the archive
depends on the limits set by the list maintainer (it is very well possible
that only, say, the last two mails sent to the list are still archived, the
rest might have expired).

You can look at the header of every mail coming from this list to see
under what name it has been archived.  The X-Mailing-List: field contains
the mailaddress of the list and the file in which this submission was
archived.

If you want to access this archive, you have to send mails to the -request
address with the word "archive" as the first word of your Subject:.
To get you started try sending a mail to the -request address with
the following:
                Subject: archive help


                          The listmaster
                          --------------
To reach a human being answering your mail you may contact the address
[email protected].  We will process your request as soon as
we can.

Mail sent to this address is pre-parsed, a little mail robot will
automatically answer all mails sent with the following Subject lines:

  help          sends this help

  lists         sends information on how to get a list of mailing lists

Reply via email to