All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ben Schmidt <mail_ben_schmidt@yahoo.com.au>
To: mlmmj@mlmmj.org
Subject: Re: [mlmmj] mlmmj and spf
Date: Fri, 11 May 2012 14:56:39 +0000	[thread overview]
Message-ID: <4FAD28A7.1030209@yahoo.com.au> (raw)
In-Reply-To: <4FACFAE7.60904@borm.org>

On 12/05/12 12:04 AM, theo borm wrote:
> On 05/11/2012 03:20 PM, Ben Schmidt wrote:
>>
>> I think it's pretty unlikely I would accept a change to Mlmmj to work
>> around a buggy SPF implementation.
>
> I would be the last to suggest a patch to work around a Sender-Id
> misconfiguration. ;-)
>
> However, a patch allowing slightly more advanced header manipulations
> (say regexp match/replace, between delheader and customheader), would
> /that/ be welcomed?

Hi, Theo,

Yes, I'd quite probably accept such a change, provided it is kept
simple, and particularly if some specifics are floated past the mailing
list prior to preparing a patch, so people have a chance to raise any
issues.

There are also some pending changes to header stuff in the bug tracker,
so it would be good to at least keep those in mind, or even implement
them along with the new code (probably in separate patches, but
nonetheless, the work is related and might be good to be implemented
together).

Cheers,

Ben.





      parent reply	other threads:[~2012-05-11 14:56 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-11 11:41 [mlmmj] mlmmj and spf theo borm
2012-05-11 11:54 ` Franky Van Liedekerke
2012-05-11 12:42 ` theo borm
2012-05-11 12:43 ` Christian Laursen
2012-05-11 13:20 ` Ben Schmidt
2012-05-11 13:42 ` Franky Van Liedekerke
2012-05-11 13:51 ` theo borm
2012-05-11 13:55 ` theo borm
2012-05-11 13:56 ` Franky Van Liedekerke
2012-05-11 13:57 ` theo borm
2012-05-11 14:33 ` theo borm
2012-05-11 14:50 ` Ben Schmidt
2012-05-11 14:56 ` Ben Schmidt [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=4FAD28A7.1030209@yahoo.com.au \
    --to=mail_ben_schmidt@yahoo.com.au \
    --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.