Over a month ago I reported a bug in how mutt processes to/cc/bcc lines: it
still isn't fixed.
[ Notably that editing to enter an additional name produced the effect of
removing the last name on the list _prior_ to editing ]

Now I've found a similar problem with adding attachments. If I hit [a] and
then input a valid file name like
        /home/jrhett/docs/client stuff/myfile.txt

I'll actually end up with
        /home/jrhett/docs/ <- not a valid file.

Quoting it makes no difference. There is absolutely nothing in MIME or any
other standard I can think of which prevents me from sending a filename
that contains spaces. And certainly not the space is simply within the path.

-- 
Joe Rhett                                                 Systems Engineer
[EMAIL PROTECTED]                                          ISite Services

PGP keys and contact information:          http://www.noc.isite.net/Staff/

Reply via email to