From: brian@lorf.org (Brian)
Subject: [sup-talk] no message-id field in header
Date: Tue, 12 Jun 2007 19:42:12 -0500 [thread overview]
Message-ID: <1181694687-sup-7571@doses> (raw)
In-Reply-To: <1181693140-sup-3121@south>
Excerpts from William Morgan's message of Tue Jun 12 19:07:15 -0500 2007:
> Excerpts from Ian Taylor's message of Tue Jun 12 11:20:13 -0700 2007:
> > When doing...
> >
> > sup-sync -c
> >
> > ...I see lots of messages about ignoring erroneous messages missing the
> > message-id field.
>
> Do these messages have message id headers? If so, can you send a few my
> way so I can see why Sup is discarding them?
I'm seeing this too. Here's one:
[Tue Jun 12 16:38:42 -0500 2007] ignoring erroneous message at
imaps://localhost:9930/INBOX#11787508680015216: no message-id field in
header {"Subject"=>"Your Order with Amazon.com", "date"=>"Wed, 09 May
2007 15:47:20 -0700", "from"=>"\"auto-confirm at amazon.com\"
<auto-confirm at amazon.com>", "From"=>"\"auto-confirm at amazon.com\"
<auto-confirm at amazon.com>", "to"=>"bsl04 at uark.edu", "subject"=>"Your
Order with Amazon.com", "To"=>"bsl04 at uark.edu", "Date"=>"Wed, 09 May
2007 15:47:20 -0700"} (source imaps://localhost:9930/INBOX offset
11787508680015216)
Not sure if this is trustworthy, but when I look at this particular
message through the uark.edu web interface, it does seem to have a
message ID: <".AAA-notification-29733,6108.1181379197"@na-rte-app-1104.vdc.amazon.com>
This no message-id thing is kind of insidious because it seems to make
sup ignore stuff sent by programs. Like I'm not getting stuff from
Amazon or various JIRAs.
next prev parent reply other threads:[~2007-06-13 0:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-12 18:20 Ian Taylor
2007-06-13 0:07 ` William Morgan
2007-06-13 0:42 ` Brian [this message]
2007-06-13 2:08 ` Ian Taylor
2007-06-13 2:11 ` William Morgan
2007-06-13 2:32 ` Brian
2007-06-13 18:04 ` 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=1181694687-sup-7571@doses \
--to=brian@lorf.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