Re: nameless records
* Roland Winkler jvax...@tah.bet [2012-07-10 00:16:48 -0500]: On Sun Jul 8 2012 Sam Steingold wrote: When I receive a confirmation message from no-re...@foo.com, I create a record and copy into its notes the url and all the relevant information about the service I just registered for. Since bbdb creates a record with first name no-reply and last name , This should be the other way round: first name and last name no-reply. Why is it reversed for you? not sure. the records may be coming from v2. loading the file becomes very slow because bbdb pauses for a second to report that I have a dozen duplicates for webmaster, no-reply, bugzilla-daemon c c. I don't think it makes much sense to add first name/last name to such records. It appears that binding bbdb-allow-duplicates to t is the easiest solution here. Thanks. Is it seriously expected that one's internet acquaintances should have unique names? I have over 5k records and I have quite a few legitimate dupes, like John Smith jsm...@foo.com and John Smith j...@bar.com. I seriously double that I am unique here. It seems that treating the e-mail names just like AKAs is better. I.e., right now a record is assumed to already have name X if X matches either bbdb-record-name or one of bbdb-record-aka. Proposal: additionally, assume a record to already have name X if X matches one of This is supposed to be relevant under which circumstances? How is this supposed to address the issue you describe above? when bbdb sees a message from foo@... without a name, it insists on adding foo to name or aka. I would like to avoid that. If for whatever reason Joe Smith has the email address f...@bar.com I wouldn't like to have Joe's record match a search for name Foo. I definitely would! -- Sam Steingold (http://sds.podval.org/) on Ubuntu 12.04 (precise) X 11.0.11103000 http://www.childpsy.net/ http://openvotingconsortium.org http://mideasttruth.com http://www.PetitionOnline.com/tap12009/ http://palestinefacts.org Lisp is not dead, it just smells funny. -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ bbdb-info@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bbdb-info BBDB Home Page: http://bbdb.sourceforge.net/
Re: nameless records
On Tue Jul 10 2012 Sam Steingold wrote: It appears that binding bbdb-allow-duplicates to t is the easiest solution here. Thanks. Is it seriously expected that one's internet acquaintances should have unique names? From the docstring of bbdb-allow-duplicates (which I did not change) I assume that the assumption that names are unique has been present in BBDB for quite some time. The assumption certainly underlies all bbdb-mua-* commands and functions. You need to rewrite these BBDB internals if you do not want to make this assumption. (I say you because I do not see a particularly high priority for doing this. BBDB has served many people well for many years with this assumption.) when bbdb sees a message from foo@... without a name, it insists on adding foo to name or aka. I would like to avoid that. Bind bbdb-message-mail-as-name to nil, if you do not like that. This user variable was introduced following your request. You can always add a name by hand that you find more meaningful (or use bbdb-create-hook if you want to do that automagically). -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ bbdb-info@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bbdb-info BBDB Home Page: http://bbdb.sourceforge.net/
Re: nameless records
* Roland Winkler jvax...@tah.bet [2012-07-10 10:06:50 -0500]: On Tue Jul 10 2012 Sam Steingold wrote: It appears that binding bbdb-allow-duplicates to t is the easiest solution here. Thanks. Is it seriously expected that one's internet acquaintances should have unique names? From the docstring of bbdb-allow-duplicates (which I did not change) I assume that the assumption that names are unique has been present in BBDB for quite some time. The assumption certainly underlies all bbdb-mua-* commands and functions. Until recently, I was not warned on such duplicates. The first loading of bbdb takes an extra second for each pair of dupes, so I have to wait for half a minute for bbdb to start. -- Sam Steingold (http://sds.podval.org/) on Ubuntu 12.04 (precise) X 11.0.11103000 http://www.childpsy.net/ http://iris.org.il http://jihadwatch.org http://www.PetitionOnline.com/tap12009/ http://camera.org C combines the power of assembler with the portability of assembler. -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ bbdb-info@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bbdb-info BBDB Home Page: http://bbdb.sourceforge.net/
Re: nameless records
On Tue Jul 10 2012 Sam Steingold wrote: Until recently, I was not warned on such duplicates. The first loading of bbdb takes an extra second for each pair of dupes, so I have to wait for half a minute for bbdb to start. Please read my mail [BBDB] ChangeLog 2012-06-24 As I said before It appears that binding bbdb-allow-duplicates to t is the easiest solution here. -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ bbdb-info@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bbdb-info BBDB Home Page: http://bbdb.sourceforge.net/
Re: nameless records
On Sun Jul 8 2012 Sam Steingold wrote: When I receive a confirmation message from no-re...@foo.com, I create a record and copy into its notes the url and all the relevant information about the service I just registered for. Since bbdb creates a record with first name no-reply and last name , This should be the other way round: first name and last name no-reply. Why is it reversed for you? loading the file becomes very slow because bbdb pauses for a second to report that I have a dozen duplicates for webmaster, no-reply, bugzilla-daemon c c. I don't think it makes much sense to add first name/last name to such records. It appears that binding bbdb-allow-duplicates to t is the easiest solution here. It seems that treating the e-mail names just like AKAs is better. I.e., right now a record is assumed to already have name X if X matches either bbdb-record-name or one of bbdb-record-aka. Proposal: additionally, assume a record to already have name X if X matches one of This is supposed to be relevant under which circumstances? How is this supposed to address the issue you describe above? If for whatever reason Joe Smith has the email address f...@bar.com I wouldn't like to have Joe's record match a search for name Foo. -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ bbdb-info@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bbdb-info BBDB Home Page: http://bbdb.sourceforge.net/
nameless records
When I receive a confirmation message from no-re...@foo.com, I create a record and copy into its notes the url and all the relevant information about the service I just registered for. Since bbdb creates a record with first name no-reply and last name , loading the file becomes very slow because bbdb pauses for a second to report that I have a dozen duplicates for webmaster, no-reply, bugzilla-daemon c c. I don't think it makes much sense to add first name/last name to such records. It seems that treating the e-mail names just like AKAs is better. I.e., right now a record is assumed to already have name X if X matches either bbdb-record-name or one of bbdb-record-aka. Proposal: additionally, assume a record to already have name X if X matches one of (defun address-name (address) (if (string-match @ address) (substring address 0 (match-beginning 0)) address)) (mapcar #'address-name (bbdb-record-mail record)) Thanks. -- Sam Steingold (http://sds.podval.org/) on Ubuntu 12.04 (precise) X 11.0.11103000 http://www.childpsy.net/ http://camera.org http://openvotingconsortium.org http://iris.org.il http://www.memritv.org http://pmw.org.il C combines the power of assembler with the portability of assembler. -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ bbdb-info@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bbdb-info BBDB Home Page: http://bbdb.sourceforge.net/
