From: Michael Stapelberg <michael+sup@stapelberg.de>
To: sup-talk <sup-talk@rubyforge.org>
Subject: [sup-talk] About faking message IDs
Date: Thu, 15 Oct 2009 12:50:13 +0200 [thread overview]
Message-ID: <1255603625-sup-2558@midna.zekjur.net> (raw)
Hi,
I just noticed that the lack of emails from my backup program seems to be
because of the missing message ids in the mail script I use. In case of
no message id inside the header, sup uses the md5sum of the whole header
(see lib/sup/message.rb:74). This effectively means that messages having
the same md5sum of their header (which happened, since the header was also
generated completely by the script and the values did not change) will
"overwrite" the old message.
As a workaround, I now added the current time to my script, so that every
header will have a different md5 sum. But maybe we can think of a more
clever way to generate faked message ids? Maybe also hash the body of the
message?
Best regards,
Michael
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk
next reply other threads:[~2009-10-15 10:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-15 10:50 Michael Stapelberg [this message]
2009-10-15 13:47 ` William Morgan
2009-10-15 13:59 ` Michael Stapelberg
2009-10-15 15:29 ` William Morgan
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=1255603625-sup-2558@midna.zekjur.net \
--to=michael+sup@stapelberg.de \
--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