Re: {bb} 1.9h Using attachments instead of inline

[Philip Clark <bblist@cannae.uklinux.net>]

On Tue, 2005-09-20 at 04:27, Robert-Andre Croteau wrote:
> 
> If my memory does not fail me, I believe qmail was misbehaving.
> Also needed rfc compliance even if as you say MUA/MTA conversion.
> 
> Hummm, maybe I should make it that messages could be either <CR>
> or <CRLF).  So this way, both types of lines could be generated.
> 
> bye

Other options would appear to involve even larger cans of worms :(
This excerpt, from the manual page for "nail", would appear to be
the likely cause of the attachment issue:

  Nail expects input text to be in Unix format, with  lines  sepa-
  rated  by newline (^J, \n) characters only.  Non-Unix text files
  that use carriage return (^M, \r) characters in addition will be
  treated  as binary data; to send such files as text, strip these
  characters e. g. by

        tr -d '\015' <input | nail . . .

  or fix the tools that generate them.

Interestingly (since it is the likely instigator of the change),
"qmail" requires messages to be input using Unix style newlines
only.

  http://www.lifewithqmail.org/lwq.html#cr

If the original problem was "qmail" rejecting e-mail from BB
because it contained bare newline (LF) characters, I'd have
to conclude the following:

  1. The users local MUA (mail or mailx) is "broken" and is
     passing bare newlines to the local MTA.

  2. The local MTA is "lame" as it both accepts the mail and
     passes it on unmodified to the remote "qmail" server.

If that is correct, it would be difficult to produce an
effective work-around from inside BB.

Cheers, Phil.



-- 
Love is a snowmobile racing across the tundra and then suddenly it
flips over, pinning you underneath. At night, the ice weasels come.
(Matt Groening)

--
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-==-=-=-=-=-=-=-=-=-=-=-=
To unsubscribe from this list, or to subscribe to the bb-digest list
send e-mail to mailto:majordomo@bb4.com with unsubscribe bb -and/or-
subscribe bb-digest in the BODY of the message.