From: wmorgan-sup@masanjin.net (wmorgan-sup)
Subject: [sup-talk] sup traceback
Date: Mon, 05 May 2008 17:59:55 -0700 [thread overview]
Message-ID: <1210035536-sup-7502@south> (raw)
In-Reply-To: <1209752246-sup-5510@junction.es.net>
Reformatted excerpts from Jon Dugan's message of 2008-05-02:
> looks like some SPAM in my inbox caused sup some serious heart burn:
>
> --- RuntimeError from thread: poll after loading inbox
> just added message "20080502075530.7980.qmail@\343\340\353\377" but couldn't
> find it in a search
Interesting. Non-ASCII characters in a message id. Haven't seen that one
before. Maybe I should SHA1 all message ids anyways.
--
William <wmorgan-sup at masanjin.net>
next prev parent reply other threads:[~2008-05-06 0:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-02 18:19 Jon Dugan
2008-05-06 0:59 ` wmorgan-sup [this message]
2008-05-08 0:56 ` Jon Dugan
2008-05-11 23:20 ` William Morgan
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=1210035536-sup-7502@south \
--to=wmorgan-sup@masanjin.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