From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] inferno-list
Date: Wed, 26 Aug 2009 08:54:33 -0400 [thread overview]
Message-ID: <f9f60b34b4ac7aeae7eaa9db00f30414@quanstro.net> (raw)
In-Reply-To: <bb9aee10908260550o762121f7m6606027d6a150f03@mail.gmail.com>
> > Technical details of permanent failure:
> > Google tried to deliver your message, but it was rejected by the
>
> > other server returned was: 554 554 5.7.1 rejected: SPF record does not
> > match sender (state 15).
>
> Seems to be fine for me @ gmail (now anyway).
the headers seemed to be truncated. if you were sending
mail as you@gmail.com from another domain, then you
are likely to be rejected. this *is* a violation of google's
spf policy.
- erik
next prev parent reply other threads:[~2009-08-26 12:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-26 3:55 hiro
2009-08-26 12:50 ` Michaelian Ennis
2009-08-26 12:54 ` erik quanstrom [this message]
2009-08-26 14:13 ` hiro
2009-08-26 20:53 ` Uriel
2009-08-26 22:23 ` hiro
2009-08-26 22:28 ` erik quanstrom
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=f9f60b34b4ac7aeae7eaa9db00f30414@quanstro.net \
--to=quanstro@quanstro.net \
--cc=9fans@9fans.net \
/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).