Chuck Norcutt wrote:
> But cut and paste is not required if you remember to enclose your links
> in angle brackets
> <https://images-na.ssl-images-amazon.com/images/G/01/00/00/00/83/02/01/83020190.pdf>
only if you also:
a:are using a mail client that knows about that on the sending end,
b:aren't sending it through any mail server which takes the more
conservative approach to RFC 2822 2.1.1
If this list software didn't nuke non-plaintext bodies, then you could
add in an extra mime-type which could have html in there, but then you
could also have images, all sorts of stuff, which presumably is the
reason why it's plaintext or nothing.
tinyurl is probably a more reliable solution.
-- dan
> Chuck Norcutt
>
> Dan Mitchell wrote:
>> (sorry if this is already posted somewhere in the giant e-3 thread;
>> I'm still working through that..)
>>
>> Courtesy of someone on dpreview -- the link will probably need gluing
>> together due to length, though.
>>
>> https://images-na.ssl-images-amazon.com/images/G/01/00/00/00/83/02/01/83
>> 020190.pdf
>>
>> -- dan
>
> ==============================================
> List usage info: http://www.zuikoholic.com
> List nannies: olympusadmin@xxxxxxxxxx
> ==============================================
>
==============================================
List usage info: http://www.zuikoholic.com
List nannies: olympusadmin@xxxxxxxxxx
==============================================
|