Hi. > Hi, if you can give us a sample of messages that generate the > "unparsable address..." strings, we can see how to handle them. They > should not be getting bound to the variable 'addresses'.
Unfortunately I am not using VM any longer, after maybe 10 years. I have switched to GNUs. I have converted all my mailboxes, so I do not have the original messages any longer. Best, -- +------------------------------------------------------------------------------+ | Manuel Carro --- Facultad de Informática -- U. Politécnica de Madrid (UPM) | | Campus de Montegancedo --- E-28660 Boadilla del Monte --- Spain | | Phone: +34-913363747 --- FAX: +34-913363669 | -- vm-8.0.12 breaks on unparseable addresses https://bugs.launchpad.net/bugs/302562 You received this bug notification because you are a member of VM development team, which is the registrant for VM (defunct). Status in VM - Goto http://launchpad.net/vm for active development: Incomplete Bug description: In function vm-su-du-recipients (file summary.el), at the end, the call (vm-set-to-of m (mapconcat 'identity addresses ", ")) can fail (it failed for me) because the paremeter addresses can be bound to a string such as "(Unparsable address -- Strange character \\; found: \";_^_>\")" and mapconcat expects a list as second argument. The kludge I made was to convert it anyway to a list: ;; Patched by MCL for addresses which are not a list of addresses (vm-set-to-of m (mapconcat 'identity (if (eq (type-of addresses) 'string) (list addresses) addresses ) ", ")) I could not test it thoroughly yet - and of course it is a kludge, but it points out to where the problem is. Cheers, MCL _______________________________________________ Mailing list: https://launchpad.net/~vm Post to : [email protected] Unsubscribe : https://launchpad.net/~vm More help : https://help.launchpad.net/ListHelp
