linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Pollei <stephen_pollei@comcast.net>
To: Adrian Bunk <bunk@stusta.de>
Cc: linux-kernel@vger.kernel.org, postmaster@list.drzeus.cx,
	postmaster@stusta.mhn.de,
	spf discuss <spf-discuss@v2.listbox.com>
Subject: Re: [2.6 patch] remove SPF-using wbsd lists from MAINTAINERS
Date: 10 Jan 2005 11:55:09 -0800	[thread overview]
Message-ID: <1105386915.980.10.camel@fury> (raw)
In-Reply-To: <20050110184307.GB2903@stusta.de>

[-- Attachment #1: Type: text/plain, Size: 1621 bytes --]

On Mon, 2005-01-10 at 10:43, Adrian Bunk wrote:

Perhaps a better approach might be to try and resolve why your emails
got rejected. Are there invalid spf records involved? Is something at
list.drzeus.cx misconfigured ?

> <wbsd-devel@list.drzeus.cx>:
> Connected to 213.115.189.212 but sender was rejected.
> Remote host said: 417 SPF error mailout.stusta.mhn.de: Address does not 
> pass the
> +Sender Policy Framework
> I'm not going to try again; this message has been in the queue too long.
> 
> <drzeus-wbsd@drzeus.cx>:
> Connected to 213.115.189.212 but sender was rejected.
> Remote host said: 417 SPF error mailout.stusta.mhn.de: Address does not 
> pass the
> +Sender Policy Framework
> I'm not going to try again; this message has been in the queue too long.
> 
> <--  snip  -->
> 
> 
> 
> IMHO lists rejecting emails based on some non-standard extension don't 
> belong into MAINTAINERS.
> 
> 
> Signed-off-by: Adrian Bunk <bunk@stusta.de>
> 
> --- linux-2.6.10-mm2-full/MAINTAINERS.old	2005-01-10 19:20:32.000000000 +0100
> +++ linux-2.6.10-mm2-full/MAINTAINERS	2005-01-10 19:26:24.000000000 +0100
> @@ -2539,8 +2539,6 @@
>  
>  W83L51xD SD/MMC CARD INTERFACE DRIVER
>  P:	Pierre Ossman
> -M:	drzeus-wbsd@drzeus.cx
> -L:	wbsd-devel@list.drzeus.cx
>  W:	http://projects.drzeus.cx/wbsd
>  S:	Maintained


-- 
http://dmoz.org/profiles/pollei.html
http://sourceforge.net/users/stephen_pollei/
http://www.orkut.com/Profile.aspx?uid=2455954990164098214
http://stephen_pollei.home.comcast.net/
GPG Key fingerprint = EF6F 1486 EC27 B5E7 E6E1  3C01 910F 6BB5 4A7D 9677

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  parent reply	other threads:[~2005-01-10 19:55 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-10 18:43 [2.6 patch] remove SPF-using wbsd lists from MAINTAINERS Adrian Bunk
2005-01-10 19:08 ` Russell King
2005-01-10 19:21   ` Adrian Bunk
2005-01-10 21:11     ` Russell King
2005-01-11 16:10     ` Alan Cox
2005-01-10 22:49   ` David Woodhouse
2005-01-10 19:23 ` Alan Cox
2005-01-10 21:21   ` Pierre Ossman
2005-01-10 21:29     ` Russell King
2005-01-10 22:04     ` Adrian Bunk
2005-01-10 22:22       ` Pierre Ossman
2005-01-10 22:42         ` Adrian Bunk
2005-01-11 11:14           ` Ondrej Zary
2005-01-10 23:36   ` David Schwartz
2005-01-11  1:03     ` Pierre Ossman
2005-01-10 19:55 ` Stephen Pollei [this message]
2005-01-11  5:54 ` Valdis.Kletnieks

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=1105386915.980.10.camel@fury \
    --to=stephen_pollei@comcast.net \
    --cc=bunk@stusta.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=postmaster@list.drzeus.cx \
    --cc=postmaster@stusta.mhn.de \
    --cc=spf-discuss@v2.listbox.com \
    /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;
as well as URLs for NNTP newsgroup(s).