From: Carsten Dominik <carsten.dominik@gmail.com>
To: nicholas.dokos@hp.com
Cc: emacs-orgmode@gnu.org
Subject: Re: Nick Dokos (2nd attempt): [OT] Thanks!
Date: Mon, 29 Mar 2010 23:44:44 +0200 [thread overview]
Message-ID: <FF59EB76-2F99-4D83-A3B9-50D003E37017@gmail.com> (raw)
In-Reply-To: <12807.1269898748@alphaville.usa.hp.com>
On Mar 29, 2010, at 11:39 PM, Nick Dokos wrote:
> [I think this bit the dust because of the same problem: I forgot
> to update a setting. 2nd attempt.]
>
> ------- Forwarded Message
>
> Date: Mon, 29 Mar 2010 16:39:31 -0400
> From: Nick Dokos <nicholas.dokos@hp.com>
> To: emacs-orgmode@gnu.org
> cc: nicholas.dokos@hp.com, Mikael Fornius <mfo@abc.se>,
> Karl Berry <karl@freefriends.org>
> Subject: [OT] Thanks!
>
> As most here know already (sorry for spamming the list with the test
> message!), I was unable to post to the list for a while. But I have
> now
> been able to post three times and, as the Bellman said, "What I tell
> you
> three times is true": the problem[1] is solved[2].
>
> I owe a debt of gratitude to Mikael Fornius, who not only groped
> through
> the list logs looking for possible problems, but also pointed out a
> header that looked funny to him. Upon further investigation, a fix to
> this header started the flow again. Mikael, thanks for saving my
> sanity[3]. Also, thanks to Karl Berry who went looking through email
> logs at gnu.org looking for the problem.
>
> It felt pretty lonely out there for a while, so please allow me to
> express
> my hearfelt thanks to Mikael and Karl who came to my rescue[4].
Hi Nick, glad to have you back.
- Carsten
>
> Thanks very much!
>
> Nick
>
> -
> ---------------------------------------------------------------------------
> [1] The theory is that at some point around the middle of February,
> gnu.org's exim server started enforcing a Sender Verification
> test. See
>
> http://www.mail-archive.com/newbie@linux-mandrake.com/
> msg172919.html
>
> for some details. I don't know if the theory is correct, but the
> fix
> - changing my postfix configuration to make sure that the Sender:
> header contains an email address that the gnu.org server can test
> successfully - seems to work in any case.
>
> [2] Famous last words...
>
> [3] OTOH, my "friends" say that that is a non-existent entity - I beg
> to differ, but as they emphasize, that proves their point...
>
> [4] ... or, as many volunteers have heard before: "You did such a good
> job that you deserve to have your salary doubled." :-)
>
>
>
> ------- End of Forwarded Message
>
>
>
> _______________________________________________
> Emacs-orgmode mailing list
> Please use `Reply All' to send replies to the list.
> Emacs-orgmode@gnu.org
> http://lists.gnu.org/mailman/listinfo/emacs-orgmode
- Carsten
prev parent reply other threads:[~2010-03-29 21:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-29 21:39 Nick Dokos (2nd attempt): [OT] Thanks! Nick Dokos
2010-03-29 21:44 ` Carsten Dominik [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
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=FF59EB76-2F99-4D83-A3B9-50D003E37017@gmail.com \
--to=carsten.dominik@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=nicholas.dokos@hp.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).