[exim-dev] [Fwd: Mail delivery failed: returning message to …

トップ ページ
このメッセージを削除
このメッセージに返信
著者: B. Johannessen
日付:  
To: exim-dev
題目: [exim-dev] [Fwd: Mail delivery failed: returning message to sender]
Any way to have Bugzilla auto-generate users in cases like this? Seems
appropriate as long as the list receives all the Bugzilla messages...


    Bob

This message was created automatically by mail delivery software.

A message that you sent could not be delivered to one or more of its
recipients. This is a permanent error. The following address(es) failed:

  bug294@???
    SMTP error from remote mail server after end of data:
    host sesame.csx.cam.ac.uk [131.111.8.41]: 550-You tried to post a comment to Bugzilla, but your address (bob@???) does
    550 not correspond to a registered user name.


------ This is a copy of the message, including all the headers. ------

Return-path: <bob@???>
Received: from ti122110a081-15751.bb.online.no ([85.166.125.135] helo=[192.168.1.100])
    by maildialog.com with esmtpsa (TLSv1:AES256-SHA:256)
    (Exim 4.51-maildialog)
    id 1H9kYW-0005De-B7
    for bug294@???; Wed, 24 Jan 2007 16:01:00 +0000
Message-ID: <45B782BB.4030305@???>
Date: Wed, 24 Jan 2007 17:00:59 +0100
From: "B. Johannessen" <bob@???>
User-Agent: Thunderbird 1.5.0.9 (X11/20061206)
MIME-Version: 1.0
To:  bug294@???
Subject: Re: [exim-dev] [Bug 294] Make smtp_accept_count available as a variable
References: <E1H9YPS-00065d-Em@???>
In-Reply-To: <E1H9YPS-00065d-Em@???>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit


holmgren@??? wrote:
> Philip has implemented this now, but called the variable
> $smtp_count_at_connection_start, which more accurately reflects what it is.
> Is it definitely impossible to implement a way of getting the true count?
> Otherwise this wish should perhaps remain, possibly for eternal times...


It's not impossible, and the only moderately hard part is making it
portable.

If I find a need for this value in the future, I'm probably going to
implement it using some kind of shared memory. Not that that's any
reason to leave the bug/wish open :-)


    Bob