From: Jakob Hirsch <jh@plonk.de>
To: mlmmj@mlmmj.org
Subject: Re: mlmmj-1.2.12-RC1 released
Date: Mon, 11 Sep 2006 09:17:38 +0000 [thread overview]
Message-ID: <450529B2.4030106@plonk.de> (raw)
In-Reply-To: <34f6b3c998e8d4bb4bd464d07c87532c@mail.n0rd.dk>
Quoting Morten K. Poulsen:
>>> I do not like the idea of having MIME parsing in the list manager
>>> itself. Or any kind of mail body parsing, for that matter.
>> Um, we had this discussion on this list about 9 months ago. Mads
>> promised to include this in 1.2.10-RC1...
> Yes, I see. But he didn't keep that promise.
So you could do it for him :)
>> Most of the patch is simplyfing the "voodoo" and making it less
>> ugly, which I felt should be done because it got even more ugly
>> with the mime stuff in it. This should be done even without the
>> mime stuff.
> I still do not like the idea of having MIME parsing in the list
I understand your concern. MIME seems to have a bad reputation when it
comes to handling in software. But the patched mlmmj is really not doing
much: Take the message (with MIME headers, if present) and put it into a
new MIME envelope. This is really not rocket science.
And as Sven pointed out: There's already the functionality of adding a
footer. I think there is some feature, it should be done right, not half
hearted. Or at least there should be at warning in the description of
the feature about its limitation (euphemised). MIME is not something new
and fancy, many MUAs use it today, so any decent mail processing
software should at least be able to deal with its basics.
> manager, but I will have another look at the patch after the release
> of mlmmj-1.2.12.
Uh, I think I heard something like that before. :)
>> PS: For some strange reason, I cannot mail you directly. My MTA
>> times out after send its EHLO, but your SMTP greeting comes fast
>> when I telnet the smtp port of mail.n0rd.dk, so the connection
>> seems to be ok.
> worksforme
looked into it, again. It works here if I disable tcp window scaling
(RFC1323) with "echo 0 > /proc/sys/net/ipv4/tcp_window_scaling". This
indicates a broken firewall somewhere in the path (probably near your
server, I tested from various sites and all of them had this). See e.g.
http://kerneltrap.org/node/6723.
next prev parent reply other threads:[~2006-09-11 9:17 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-04 19:42 mlmmj-1.2.12-RC1 released Morten K. Poulsen
2006-09-04 21:02 ` Jakob Hirsch
2006-09-05 6:43 ` Christian Lackas
2006-09-05 17:02 ` Morten K. Poulsen
2006-09-05 17:21 ` Mads Martin Joergensen
2006-09-05 17:24 ` Morten K. Poulsen
2006-09-06 16:38 ` Henne Vogelsang
2006-09-06 18:22 ` Stefan Reinauer
2006-09-06 19:42 ` Jakob Hirsch
2006-09-06 21:26 ` Morten K. Poulsen
2006-09-06 21:28 ` Mads Martin Joergensen
2006-09-06 21:31 ` Morten K. Poulsen
2006-09-06 21:42 ` Morten K. Poulsen
2006-09-06 22:05 ` Morten K. Poulsen
2006-09-07 10:26 ` Mads Martin Joergensen
2006-09-07 13:03 ` Christoph Wilke
2006-09-07 23:53 ` Sven 'Darkman' Michels
2006-09-11 9:17 ` Jakob Hirsch [this message]
2006-09-11 19:04 ` Morten K. Poulsen
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=450529B2.4030106@plonk.de \
--to=jh@plonk.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.