* [sup-talk] About faking message IDs
@ 2009-10-15 10:50 Michael Stapelberg
2009-10-15 13:47 ` William Morgan
0 siblings, 1 reply; 6+ messages in thread
From: Michael Stapelberg @ 2009-10-15 10:50 UTC (permalink / raw)
To: sup-talk
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
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [sup-talk] About faking message IDs
2009-10-15 10:50 [sup-talk] About faking message IDs Michael Stapelberg
@ 2009-10-15 13:47 ` William Morgan
2009-10-15 13:59 ` Michael Stapelberg
0 siblings, 1 reply; 6+ messages in thread
From: William Morgan @ 2009-10-15 13:47 UTC (permalink / raw)
To: sup-talk
Reformatted excerpts from Michael Stapelberg's message of 2009-10-15:
> 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.
Doesn't the header include the date?
--
William <wmorgan-sup@masanjin.net>
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [sup-talk] About faking message IDs
2009-10-15 13:47 ` William Morgan
@ 2009-10-15 13:59 ` Michael Stapelberg
2009-10-15 15:29 ` William Morgan
0 siblings, 1 reply; 6+ messages in thread
From: Michael Stapelberg @ 2009-10-15 13:59 UTC (permalink / raw)
To: sup-talk
Hi William,
Excerpts from William Morgan's message of Thu Oct 15 15:47:36 +0200 2009:
> Doesn't the header include the date?
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).
Best regards,
Michael
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [sup-talk] About faking message IDs
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
0 siblings, 2 replies; 6+ messages in thread
From: William Morgan @ 2009-10-15 15:29 UTC (permalink / raw)
To: sup-talk
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
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [sup-talk] About faking message IDs
2009-10-15 15:29 ` William Morgan
@ 2009-10-15 19:21 ` Nicolas Pouillard
2009-10-16 0:14 ` Carl Worth
1 sibling, 0 replies; 6+ messages in thread
From: Nicolas Pouillard @ 2009-10-15 19:21 UTC (permalink / raw)
To: William Morgan; +Cc: sup-talk
Excerpts from William Morgan's message of Thu Oct 15 17:29:29 +0200 2009:
> 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}").
This way we loose the reproducibility, but I concede that we can't have both.
--
Nicolas Pouillard
http://nicolaspouillard.fr
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [sup-talk] About faking message IDs
2009-10-15 15:29 ` William Morgan
2009-10-15 19:21 ` Nicolas Pouillard
@ 2009-10-16 0:14 ` Carl Worth
1 sibling, 0 replies; 6+ messages in thread
From: Carl Worth @ 2009-10-16 0:14 UTC (permalink / raw)
To: sup-talk
[-- Attachment #1.1: Type: text/plain, Size: 380 bytes --]
Excerpts from William Morgan's message of Thu Oct 15 08:29:29 -0700 2009:
> 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}").
Won't that then make sup insert duplicate documents into the index for
any run of sup-sync --all over the relevant sources?
-Carl
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 190 bytes --]
[-- Attachment #2: Type: text/plain, Size: 140 bytes --]
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk
^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2009-10-16 0:14 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2009-10-15 10:50 [sup-talk] About faking message IDs Michael Stapelberg
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
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox