From: Sven 'Darkman' Michels <sven@darkman.de>
To: mlmmj@mlmmj.org
Subject: [Fwd: Re: [Fwd: Re: Mails in incoming cause of "invalid from"]]
Date: Sun, 17 Sep 2006 20:55:49 +0000 [thread overview]
Message-ID: <450DB655.50604@darkman.de> (raw)
In-Reply-To: <450C3D28.8080907@darkman.de>
[-- Attachment #1: Type: text/plain, Size: 308 bytes --]
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
shame on me... maybe we could force reply-to? (i know, bad
thing etc..)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (GNU/Linux)
iD8DBQFFDbZUQoCguWUBzBwRAsvoAJsGQ3lBnn63fddlvq/7Uni4T4Yh7wCggnQt
Be50f7nFlcGto6l/BXPWAJA=
=e7Og
-----END PGP SIGNATURE-----
[-- Attachment #2: Re: [Fwd: Re: Mails in incoming cause of "invalid from"] --]
[-- Type: message/rfc822, Size: 1943 bytes --]
From: Sven 'Darkman' Michels <sven@darkman.de>
To: Mads Martin Joergensen <mmj@mmj.dk>
Subject: Re: [Fwd: Re: Mails in incoming cause of "invalid from"]
Date: Sun, 17 Sep 2006 22:53:07 +0200
Message-ID: <450DB5B3.7050006@darkman.de>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Mads Martin Joergensen wrote:
> mlmmj should stop parsing headers when two newlines are met like the
> spec claims.
ahem? 2? maybe i'm missunderstand you, but i thought header ends
when one empty line shows up...?
> That's why when I add a From: on the beginning of a line after a
> newline, that From: isn't picked up.
>
> Could you look in a hex editor or such, to see if there's something
> making mlmmj believe there's more headers? Space or tab is enough to
> make it continue.
>
>> I also tested this with thunderbird: when i add some
>> "fake headers", it works with the following "code":
>> bla fasel
>
> Well, can you trigger it with Thunderbird, by writing From: somewhere
> after a newline?
No, couldn't. But i played around with, the following did trigger
it:
<space><space>text\n
\n
<space><space>text\n
From: test+help@c3f2m.de [mailto:test+help@c3f2m.de]
looks like:
bla fasel
bla
From: test+help@c3f2m.de [mailto:test+help@c3f2m.de]
Does that help?
Regards,
Sven
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (GNU/Linux)
iD8DBQFFDbWyQoCguWUBzBwRAiBUAJ9X2rrMewvoxmv6DkJmwcB/kdZHqACeL9b0
+O+hYWPYYEkXYEWuKOExPWY=
=atrz
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2006-09-17 20:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-16 18:06 [Fwd: Re: [Fwd: Re: Mails in incoming cause of "invalid from"]] Sven 'Darkman' Michels
2006-09-17 20:55 ` Sven 'Darkman' Michels [this message]
2006-09-17 21:05 ` Mads Martin Joergensen
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=450DB655.50604@darkman.de \
--to=sven@darkman.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.