From: William Morgan <wmorgan-sup@masanjin.net>
To: sup-talk <sup-talk@rubyforge.org>
Subject: Re: [sup-talk] About faking message IDs
Date: Thu, 15 Oct 2009 08:29:29 -0700 [thread overview]
Message-ID: <1255620476-sup-8113@masanjin.net> (raw)
In-Reply-To: <1255615018-sup-5653@midna.zekjur.net>
Reformatted excerpts from Michael Stapelberg's message of 2009-10-15:
> No, in my case it did not. The reason for that is calling "deliver"
> directly, that is without talking SMTP to a mailserver. Thus, no
> headers are getting added. Surely this is a corner case, but I think
> it will cause headache for system administrators running into this
> one, if they notice it all (overwriting messages is quite dangerous).
Ok. I think it's fine to generate the message id via another mechanism,
e.g. the way we do it in edit-message-mode ("<#{Time.now.to_i}-sup-#{rand 10000}@#{hostname}").
--
William <wmorgan-sup@masanjin.net>
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk
next prev parent reply other threads:[~2009-10-15 15:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-15 10:50 Michael Stapelberg
2009-10-15 13:47 ` William Morgan
2009-10-15 13:59 ` Michael Stapelberg
2009-10-15 15:29 ` William Morgan [this message]
2009-10-15 19:21 ` Nicolas Pouillard
2009-10-16 0:14 ` Carl Worth
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=1255620476-sup-8113@masanjin.net \
--to=wmorgan-sup@masanjin.net \
--cc=sup-talk@rubyforge.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox