Re: Cannot extract an address component at foo+bar@baz.com.

2001-11-01 Thread Daniel Pittman
On Thu, 01 Nov 2001, Simon Josefsson wrote: Matt Armstrong [EMAIL PROTECTED] writes: [...] though perhaps other characters should be allowed as well (*=!%, etc. etc.). In fact, perhaps all non-whitespace should be allowed there -- or at least every character that doesn't require quoting.

Re: Cannot extract an address component at foo+bar@baz.com.

2001-10-31 Thread Matt Armstrong
Simon Josefsson [EMAIL PROTECTED] writes: Ronan Waide [EMAIL PROTECTED] writes: On October 30, [EMAIL PROTECTED] said: It seems as if BBDB doesn't like addresses with + in them: (bbdb-extract-address-components [EMAIL PROTECTED]) Is this somehow intentional? How can I fix it? What

Re: Cannot extract an address component at foo+bar@baz.com.

2001-10-31 Thread Simon Josefsson
Matt Armstrong [EMAIL PROTECTED] writes: Simon Josefsson [EMAIL PROTECTED] writes: Ronan Waide [EMAIL PROTECTED] writes: On October 30, [EMAIL PROTECTED] said: It seems as if BBDB doesn't like addresses with + in them: (bbdb-extract-address-components [EMAIL PROTECTED]) Is this

Re: Cannot extract an address component...

2001-07-29 Thread Ronan Waide
On April 12, [EMAIL PROTECTED] said: I must apologise again for my recent low profile; I'll try and get some good code updates in this weekend with, perhaps, a view towards a new release at the end of the month. damn. i'm denying i ever said this. waider. -- [EMAIL PROTECTED] / Yes, it /is/

Re: Cannot extract an address component...

2001-04-12 Thread Ronan Waide
On April 6, [EMAIL PROTECTED] said: - You have more control over the update type, i.e. you may add all or none of the new addresses with just one key press ... The various functions to display all records need to distinguish between the Sender address(es) and the Recipient address(es) for

Re: Cannot extract an address component...

2001-03-30 Thread Colin Rafferty
Alex Schroeder writes: [EMAIL PROTECTED] (Colin Rafferty) writes: Norbert Koch writes: Another header version which bbdb dislikes is 'To: [EMAIL PROTECTED] (Mr Foo)'. It works for me (BBDB version 2.00.06). See my `From'. Did this get broken? Well, a feature got added for Gnus, I

Re: Cannot extract an address component...

2001-03-29 Thread Norbert Koch
Robert Fenk [EMAIL PROTECTED] writes: Hi! Well it is accepting those, but not "foo"! And it is liberal, since those bad one will generate no error, but you will get a message complaining about them ... Yes, I see now what happens. The combination To: [EMAIL PROTECTED] (Mr Foo) Reply-To:

Re: Cannot extract an address component...

2001-03-29 Thread Robert Fenk
On Thursday, March 29 2001 10:21:34, Norbert Koch wrote: [...] Yes, I see now what happens. The combination To: [EMAIL PROTECTED] (Mr Foo) Reply-To: [EMAIL PROTECTED] (Mr Foo) And now I see it. It happens only if the last displayed header is one of those where we want to extract

Re: Cannot extract an address component...

2001-03-29 Thread Norbert Koch
Robert Fenk [EMAIL PROTECTED] writes: And now I see it. It happens only if the last displayed header is one of those where we want to extract addresses, but unfortunately I have sorted them differently ... A fix is in CVS and the diff attached! Thanks for the fix. I'm playing around

Re: Cannot extract an address component...

2001-03-28 Thread Colin Rafferty
Norbert Koch writes: Another header version which bbdb dislikes is 'To: [EMAIL PROTECTED] (Mr Foo)'. It works for me (BBDB version 2.00.06). See my `From'. Did this get broken? -- Colin ___ [EMAIL PROTECTED]

Re: Cannot extract an address component...

2001-03-28 Thread Robert Fenk
On , March 27 2001 22:30:54, Kai Grossjohann wrote: Technically, `To: foo' is not a valid mail header, it must be either `To: foo' or `To: bla foo'. Nevertheless, BBDB should not barf when reading this. Be liberal in what you accept, and so on... Well it is accepting those, but not "foo"!

Re: Cannot extract an address component...

2001-03-28 Thread Alex Schroeder
Robert Fenk [EMAIL PROTECTED] writes: My guess: One of the headers (From,To,Reply-To), probably the Reply-To header is not extracted correctly, as the closing "" seems to be missing. Do a "M-: (mail-fetch-field "Reply-To") RET" Does it return the complete header content? Remove this

Re: Cannot extract an address component...

2001-03-27 Thread Kai Großjohann
Technically, `To: foo' is not a valid mail header, it must be either `To: foo' or `To: bla foo'. Nevertheless, BBDB should not barf when reading this. Be liberal in what you accept, and so on... kai -- Be indiscrete. Do it continuously. ___ [EMAIL

Re: Cannot extract an address component...

2001-03-27 Thread Robert Fenk
On , March 27 2001 18:56:36, Alex Schroeder wrote: I am getting the following error on Oort Gnus v0.01, updated a few days ago, BBDB version 2.33 ($Date: 2001/03/26 14:35:42 $), GNU Emacs 20.7.1 (i686-pc-linux-gnu, X toolkit) of Sat Jun 24 2000 on snail. Any ideas? Cannot extract

Re: Cannot extract an address component...

2001-03-27 Thread Robert Fenk
on snail. Any ideas? Cannot extract an address component at "[EMAIL PROTECTED]". Can you generate a stacktrace for this? One usually would not get a stack trace for this unless bbdb-extract-address-component-handler is set to 'error, which is not the default. It is intended as

Re: Cannot extract an address component...

2001-03-27 Thread Norbert Koch
[EMAIL PROTECTED] (Kai Grojohann) writes: Hi! Technically, `To: foo' is not a valid mail header, it must be either `To: foo' or `To: bla foo'. Nevertheless, BBDB should not barf when reading this. Be liberal in what you accept, and so on... Another header version which bbdb dislikes is

Re: Cannot extract an address component...

2001-03-27 Thread Ronan Waide
On March 27, [EMAIL PROTECTED] said: Technically, `To: foo' is not a valid mail header, it must be either `To: foo' or `To: bla foo'. Nevertheless, BBDB should not barf when reading this. Be liberal in what you accept, and so on... kai Oddly enough, if I do

Re: Cannot extract an address component at .

2001-02-01 Thread Robert Fenk
On Thursday, February 1 2001 00:17:41, Sridhar Boovaraghavan wrote: [...] This might be some weird interaction with Emacs 21. I downloaded 21.0.97 (the latest pretest) today and the behavior was even worse. Now in addition to the error, VM doesn't display the messages properly (I see the

Re: Cannot extract an address component at .

2001-02-01 Thread Sridhar Boovaraghavan
s-component-handler ...) (bbdb-warn "Cannot extract an address component at \"%s\". See `bbdb-extract-address-component-handler' for more information." adstring)) ((equal bbdb-extract-address-component-handler ...) (message "Cannot extract an address component at \"

Re: Cannot extract an address component at .

2001-02-01 Thread Sridhar Boovaraghavan
Robert Fenk writes: On Thursday, February 1 2001 00:17:41, Sridhar Boovaraghavan wrote: [...] This might be some weird interaction with Emacs 21. I downloaded 21.0.97 (the latest pretest) today and the behavior was even worse. Now in addition to the error, VM doesn't display the

Re: Cannot extract an address component at .

2001-01-30 Thread Robert Fenk
On Monday, January 29 2001 23:00:21, Ronan Waide wrote: [...] many times. Now when I try to display/edit a user's notes by pressing ';', it doesn't come up. It displays the above message and exits. I couldn't get a meaningful stack trace also. Does this mean that some field(s) in my

Cannot extract an address component at .

2001-01-29 Thread Sridhar Boovaraghavan
Hi, I am using the latest BBDB out of CVS, VM 6.90, Emacs 21.0.96. I am getting this error -- Cannot extract an address component at " ". -- many times. Now when I try to display/edit a user's notes by pressing ';', it doesn't come up. It displays the above message and exits. I co

Re: Cannot extract an address component at .

2001-01-29 Thread Ronan Waide
On January 29, [EMAIL PROTECTED] said: Hi, I am using the latest BBDB out of CVS, VM 6.90, Emacs 21.0.96. I am getting this error -- Cannot extract an address component at " ". -- many times. Now when I try to display/edit a user's notes by pressing ';', it doesn