From: Wes Hardaker <wes@hardakers.net>
Subject: dummy line marked E breaks imap
Date: Wed, 22 Dec 2004 10:25:19 -0800 [thread overview]
Message-ID: <sd652ugpgw.fsf@wes.hardakers.net> (raw)
I occasionally accidentally mark a dummy line as expired. This is
obviously a bad thing to do, but gnus should die on it. The end
result is that when I try to exit that buffer next I get a internal
error from the imap syncing:
Signaling: (error "Internal error, tag 708 status BAD code nil text Bogus sequence in UID STORE: Syntax error in sequence")
signal(error ("Internal error, tag 708 status BAD code nil text Bogus sequence in UID STORE: Syntax error in sequence"))
cerror("Internal error, tag %s status %s code %s text %s" 708 BAD nil "Bogus sequence in UID STORE: Syntax error in sequence")
apply(cerror "Internal error, tag %s status %s code %s text %s" (708 BAD nil "Bogus sequence in UID STORE: Syntax error in sequence"))
error("Internal error, tag %s status %s code %s text %s" 708 BAD nil "Bogus sequence in UID STORE: Syntax error in sequence")
imap-parse-response()
imap-arrival-filter(#<process "imap" pid 12773 state:run> "708 BAD Bogus sequence in UID STORE: Syntax error in sequence\r\n")
accept-process-output(#<process "imap" pid 12773 state:run> 0 100)
imap-wait-for-tag(708 nil)
imap-send-command-wait("UID STORE -33,33862:33866,33900,33903:33904,33928,34008,34013:34014,34621,34623,34628:34655,34660:34662,34671:34672,34681:34692,34694:34697,34701,34703:34704,34706,34710,34716:34719,34721:34723,34725:34734,34737,34739:34742,34745:34749,34753:34755,34759:34764,34766:34771,34775:34781,34786:34787,34789,34791:34797,34800:34908,34910:34914 +FLAGS (gnus-expire)")
imap-message-flags-add("-33,33862:33866,33900,33903:33904,33928,34008,34013:34014,34621,34623,34628:34655,34660:34662,34671:34672,34681:34692,34694:34697,34701,34703:34704,34706,34710,34716:34719,34721:34723,34725:34734,34737,34739:34742,34745:34749,34753:34755,34759:34764,34766:34771,34775:34781,34786:34787,34789,34791:34797,34800:34908,34910:34914" "gnus-expire")
nnimap-request-set-mark("ucd-snmp.mail" (((-33 ... 33900 ... 33928 34008 ... 34621 34623 ... ... ... ... ... 34701 ... 34706 34710 ... ... ... 34737 ... ... ... ... ... ... ... 34789 ... ... ...) add (expire)) ((34742 34746 34802 ... 34839 34866 34868 34871 34884 34889 34893 34906 34908) add (reply))) "hardakers")
gnus-request-set-mark("nnimap+hardakers:ucd-snmp.mail" (((-33 ... 33900 ... 33928 34008 ... 34621 34623 ... ... ... ... ... 34701 ... 34706 34710 ... ... ... 34737 ... ... ... ... ... ... ... 34789 ... ... ...) add (expire)) ((34742 34746 34802 ... 34839 34866 34868 34871 34884 34889 34893 34906 34908) add (reply))))
gnus-update-marks()
gnus-summary-update-info()
--
"In the bathtub of history the truth is harder to hold than the soap,
and much more difficult to find." -- Terry Pratchett
next reply other threads:[~2004-12-22 18:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-22 18:25 Wes Hardaker [this message]
2004-12-22 19:11 ` Simon Josefsson
2004-12-23 5:03 ` Wes Hardaker
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=sd652ugpgw.fsf@wes.hardakers.net \
--to=wes@hardakers.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;
as well as URLs for NNTP newsgroup(s).