From: "Torrens (lists)" <Lists@torrens.org.uk>
To: mlmmj@mlmmj.org
Subject: Re: Bugs
Date: Mon, 26 May 2008 12:55:40 +0000 [thread overview]
Message-ID: <4fa58773baLists@torrens.org.uk> (raw)
In-Reply-To: <4fa0f34d76Lists@torrens.org.uk>
In article <1211230254.20119.8.camel@mopo-laptop>,
Morten K. Poulsen <morten@afdelingp.dk> wrote:
> On Sat, 2008-05-17 at 16:32 +0100, Torrens (lists) wrote:
> > Sorry, I do not know which version of mlmmj is in use (should there be
> > a header line added with this info?).
> There could be a tunable for that, yes. Patches are welcome.
> > 1: mlmmj is over-sensitive to files not ending in a newline character.
> > I had a footer file that was like this - as a result about 65 zero
> > bytes get appended to the end of every outgoing email.
> >
> > The copy in the archive is however correct.
> I don't think that it is over-sensitive,
Well, it's a choice of wording! The 'effect' became a problem because some
servers reject emails containing zero bytes.
> but it definitely reacts in an impractical way. The outgoing mail is
> memory mapped, and a buffer is allocated for the SMTP-prepared mail (.
> is escaped in the beginning of a line, newlines are \r\n). The mail is
> copied, line for line, into this new buffer. The last line is not
> copied, because there is no \n.
> A special case should be added, which corrects such a mail. The SMTP
> code could also use a clean up.
Cure is eassy, once aware of the cause. But it's a fragility in the
software!
> > 2: Just had an email with three Content-type lines. mlmmj acted on the
> > third one - even though only the first was truly in the headers. Two
> > and three were separated from the headers by a blank line.
> mlmmj does not care about Content-Type headers. Perhaps you are using
> Sascha Sommer's recievestrip?
Please forget this one, I mis-interpreted what was happening.
> Morten
prev parent reply other threads:[~2008-05-26 12:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-17 15:32 Bugs Torrens (lists)
2008-05-19 20:50 ` Bugs Morten K. Poulsen
2008-05-26 12:55 ` Torrens (lists) [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4fa58773baLists@torrens.org.uk \
--to=lists@torrens.org.uk \
--cc=mlmmj@mlmmj.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox