List Info

Thread: ezmlm warning




ezmlm warning
user name
2007-07-13 19:48:33
Hi! This is the ezmlm program. I'm managing the
solr-devlucene.apache.org mailing list.

I'm working for my owner, who can be reached
at solr-dev-ownerlucene.apache.org.


Messages to you from the solr-dev mailing list seem to
have been bouncing. I've attached a copy of the first
bounce
message I received.

If this message bounces too, I will send you a probe. If the
probe bounces,
I will remove your address from the solr-dev mailing list,
without further notice.


I've kept a list of which messages from the solr-dev mailing
list have 
bounced from your address.

Copies of these messages may be in the archive.
To retrieve a set of messages 123-145 (a maximum of 100 per
request),
send a short message to:
   <solr-dev-get.123_145lucene.apache.org>

To receive a subject and author list for the last 100 or so
messages,
send a short message to:
   <solr-dev-indexlucene.apache.org>

Here are the message numbers:

   4891
   4892
   4893
   4894
   4895
   4896
   4897
   4898
   4899
   4900
   4901
   4902
   4903
   4904
   4905
   4906
   4907
   4908
   4909
   4910
   4911
   4912
   4913
   4914
   4915
   4916
   4917
   4918
   4919
   4920
   4921
   4922
   4923
   4924
   4925
   4926
   4927
   4928
   4929
   4930
   4931
   4932
   4933
   4934
   4935
   4936
   4937
   4938
   4939
   4940
   4941
   4942
   4943
   4944
   4945
   4946
   4947
   4948
   4949
   4950
   4951
   4952
   4953
   4954
   4955
   4956
   4957
   4958
   4959
   4960
   4961
   4962
   4963
   4964
   4965
   4966
   4967
   4968
   4969
   4970
   4971
   4972
   4973
   4974
   4975
   4976
   4977
   4979
   4978
   4980
   4981
   4982
   4983
   4984
   4985
   4986
   4987
   4988
   4989
   4990
   4991
   4992
   4993
   4994
   4995
   4996
   4997
   4998
   4999
   5000
   5001
   5002
   5003
   5004
   5005
   5006
   5007
   5008
   5009
   5010
   5011
   5012
   5013
   5014
   5015
   5016
   5017
   5018
   5019
   5020
   5021
   5022
   5023
   5024
   5025
   5026
   5027
   5028
   5029
   5030
   5031
   5032
   5033
   5034
   5035
   5036
   5037
   5038
   5039
   5040
   5041
   5042
   5043
   5044
   5045
   5046
   5047
   5048
   5049
   5050
   5051
   5052
   5053
   5054
   5055
   5056
   5057
   5058
   5059
   5060
   5061
   5062
   5063
   5064
   5065
   5066
   5067
   5068
   5069
   5070
   5071
   5072
   5073
   5074
   5075
   5076
   5077
   5078
   5079
   5080
   5081
   5082
   5083
   5084
   5085
   5086
   5087
   5088

--- Enclosed is a copy of the bounce message I received.

Return-Path: <>
Received: (qmail 8066 invoked by uid 99); 2 Jul 2007
07:01:13 -0000
Received: from herse.apache.org (HELO herse.apache.org)
(140.211.11.133)
    by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 02 Jul
2007 00:01:13 -0700
X-ASF-Spam-Status: No, hits=-0.0 required=10.0
	tests=SPF_HELO_PASS
X-Spam-Check-By: apache.org
Received: from [66.98.192.98] (HELO starfire.yahoo.com)
(66.98.192.98)
    by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 02 Jul
2007 00:01:10 -0700
Received: by starfire.yahoo.com (Postfix)
	id D8DD1208060; Mon,  2 Jul 2007 02:01:06 -0500 (CDT)
Date: Mon,  2 Jul 2007 02:01:06 -0500 (CDT)
From: MAILER-DAEMONyahoo.com (Mail Delivery System)
Subject: Undelivered Mail Returned to Sender
To: solr-dev-return-4891-bond=yahoo.comlucene.apache.org
Auto-Submitted: auto-replied
MIME-Version: 1.0
Content-Type: multipart/report;
report-type=delivery-status;
	boundary="61A24208110.1183359666/starfire.yahoo.com&qu
ot;
Content-Transfer-Encoding: 8bit
Message-Id: <20070702070106.D8DD1208060starfire.yahoo.com>
X-Virus-Checked: Checked by ClamAV on apache.org

This is a MIME-encapsulated message.

--61A24208110.1183359666/starfire.yahoo.com
Content-Description: Notification
Content-Type: text/plain; charset=us-ascii

This is the mail system at host starfire.yahoo.com.

I'm sorry to have to inform you that your message could not
be delivered to one or more recipients. It's attached
below.

For further assistance, please send mail to postmaster.

If you do so, please include this problem report. You can
delete your own text from the attached returned message.

                   The mail system

<bondyahoo.com>: cannot update mailbox /var/mail/bond
for user bond. error
    writing message: File too large

--61A24208110.1183359666/starfire.yahoo.com
Content-Description: Delivery report
Content-Type: message/delivery-status

Reporting-MTA: dns; starfire.yahoo.com
X-Postfix-Queue-ID: 61A24208110
X-Postfix-Sender: rfc822;
solr-dev-return-4891-bond=yahoo.comlucene.apache.org
Arrival-Date: Mon,  2 Jul 2007 02:01:06 -0500 (CDT)

Final-Recipient: rfc822; bondyahoo.com
Original-Recipient: rfc822;bondyahoo.com
Action: failed
Status: 5.2.2
Diagnostic-Code: x-unix; input/output error

--61A24208110.1183359666/starfire.yahoo.com
Content-Description: Undelivered Message
Content-Type: message/rfc822
Content-Transfer-Encoding: 8bit

X-Virus-Scanned: amavisd-new at yahoo.com
Received: from starfire.yahoo.com ([127.0.0.1])
	by localhost (starfire.yahoo.com [127.0.0.1]) (amavisd-new,
port 10024)
	with ESMTP id hnN-dq5HL6pJ for <bondyahoo.com>;
	Mon,  2 Jul 2007 02:01:04 -0500 (CDT)
Received: from mail.apache.org (hermes.apache.org
[140.211.11.2])
	by starfire.yahoo.com (Postfix) with SMTP id 548CC208060
	for <bondyahoo.com>; Mon,  2 Jul 2007 02:01:04
-0500 (CDT)
Received: (qmail 7535 invoked by uid 500); 2 Jul 2007
07:00:48 -0000
Mailing-List: contact solr-dev-helplucene.apache.org; run by
ezmlm
Precedence: bulk
List-Help: <mailto:solr-dev-helplucene.apache.org>
List-Unsubscribe: <mailto:solr-dev-unsubscribelucene.apache.org>
List-Post: <mailto:solr-devlucene.apache.org>
List-Id: <solr-dev.lucene.apache.org>
Reply-To: solr-devlucene.apache.org
Delivered-To: mailing list solr-devlucene.apache.org
Received: (qmail 7522 invoked by uid 99); 2 Jul 2007
07:00:48 -0000
Received: from herse.apache.org (HELO herse.apache.org)
(140.211.11.133)
    by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 02 Jul
2007 00:00:48 -0700
X-ASF-Spam-Status: No, hits=-100.0 required=10.0
	tests=ALL_TRUSTED
X-Spam-Check-By: apache.org
Received: from [140.211.11.4] (HELO brutus.apache.org)
(140.211.11.4)
    by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 02 Jul
2007 00:00:44 -0700
Received: from brutus (localhost [127.0.0.1])
	by brutus.apache.org (Postfix) with ESMTP id E450D7141EA
	for <solr-devlucene.apache.org>; Mon,  2 Jul 2007
00:00:18 -0700 (PDT)
Message-ID: <33476909.1183359618875.JavaMail.jirabrutus>
Date: Mon, 2 Jul 2007 00:00:18 -0700 (PDT)
From: "Ryan McKinley (JIRA)" <jiraapache.org>
To: solr-devlucene.apache.org
Subject: [jira] Updated: (SOLR-139) Support
updateable/modifiable documents
In-Reply-To: <30063871.1170576125525.JavaMail.jirabrutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-Virus-Checked: Checked by ClamAV on apache.org


     [ 
https://issues.apache.org/jira/browse/SOLR-139?page=com.atla
ssian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ryan McKinley updated SOLR-139:
-------------------------------

    Attachment: SOLR-139-IndexDocumentCommand.patch

* Updated for new SolrDocument implementation.
* Testing via solrj.

I think this should be committed soon.  It should only
affect performance if you specify a 'mode' in the add
command.

> Support updateable/modifiable documents
> ---------------------------------------
>
>                 Key: SOLR-139
>                 URL: https:
//issues.apache.org/jira/browse/SOLR-139
>             Project: Solr
>          Issue Type: Improvement
>          Components: update
>            Reporter: Ryan McKinley
>         Attachments:
SOLR-139-IndexDocumentCommand.patch,
SOLR-139-IndexDocumentCommand.patch,
SOLR-139-IndexDocumentCommand.patch,
SOLR-139-IndexDocumentCommand.patch,
SOLR-139-IndexDocumentCommand.patch,
SOLR-139-IndexDocumentCommand.patch,
SOLR-139-IndexDocumentCommand.patch,
SOLR-139-IndexDocumentCommand.patch,
SOLR-139-IndexDocumentCommand.patch,
SOLR-139-IndexDocumentCommand.patch,
SOLR-139-IndexDocumentCommand.patch,
SOLR-139-XmlUpdater.patch
>
>
> It would be nice to be able to update some fields on a
document without having to insert the entire document.
> Given the way lucene is structured, (for now) one can
only modify stored fields.
> While we are at it, we can support incrementing an
existing value - I think this only makes sense for numbers.
> for background, see:
> http://www.nabble.com/loading-many-doc
uments-by-ID-tf3145666.html#a8722293

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue
online.


--61A24208110.1183359666/starfire.yahoo.com--

[1]

about | contact  Other archives ( Real Estate discussion Medical topics )