imap troubles, especially with storing outgoing mail

imap troubles, especially with storing outgoing mail

[Alexander Kotelnikov]

[-- Attachment #1: Type: text/plain, Size: 146 bytes --]

Hello.

I just noticed that my outgoing mail is not stored in INBOX.outbox on
by imap server, switched imap-log to t and look, what I have seen:


[-- Attachment #2: imap-log --]
[-- Type: text/plain, Size: 3984 bytes --]

* STATUS INBOX.junk.wad (UIDNEXT 61 UIDVALIDITY 1102336563 UNSEEN 0)
3309 OK Completed
* BAD Invalid tag
* STATUS INBOX.lj (UIDNEXT 228 UIDVALIDITY 1051612554 UNSEEN 0)
3310 OK Completed
* BAD Invalid tag
3311 SELECT "INBOX.outbox"
* FLAGS (\Answered \Flagged \Draft \Deleted \Seen gnus-forward)
* OK [PERMANENTFLAGS (\Answered \Flagged \Draft \Deleted \Seen gnus-forward \*)] 
* 599 EXISTS
* 0 RECENT
* OK [UIDVALIDITY 1046385103] 
3311 OK [READ-WRITE] Completed
3312 UID SEARCH UNSEEN UNDELETED
* BAD Invalid tag
* SEARCH
3312 OK Completed
* BAD Invalid tag
3313 UID SEARCH SEEN
* SEARCH 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 241 242 243 244 245 246 247 248 249 250 251 252 253 254 255 256 257 258 259 260 261 262 263 264 265 266 267 268 269 270 271 272 273 274 275 276 277 278 279 280 281 282 283 284 285 286 287 288 289 290 291 292 293 294 295 296 297 298 299 300 301 302 303 304 305 306 307 308 309 310 311 312 313 314 315 316 317 318 319 320 321 322 323 324 325 326 327 328 329 330 331 332 333 334 335 336 337 338 339 340 341 342 343 344 345 346 347 348 349 350 351 352 353 354 355 356 357 358 359 360 361 362 363 364 365 366 367 368 369 370 371 372 373 374 375 376 377 378 379 380 381 382 383 384 385 386 387 388 389 390 391 394 395 396 397 398 399 400 401 402 403 404 405 406 407 408 409 410 411 412 413 414 415 416 417 418 419 420 421 422 423 424 425 426 427 428 429 432 433 434 435 436 437 438 439 440 441 442 443 444 445 446 447 448 449 450 451 452 453 454 455 456 457 458 459 460 461 462 463 464 465 466 467 468 469 470 471 472 473 474 475 476 477 478 479 480 481 482 483 484 485 486 487 488 489 490 491 492 493 494 495 496 497 498 499 500 501 502 503 504 505 506 507 508 509 510 511 512 513 514 515 516 517 519 520 521 522 523 524 525 526 527 528 529 530 531 532 533 534 535 536 537 538 539 540 541 542 543 544 545 546 547 548 549 550 551 552 553 554 555 556 557 558 559 560 561 562 563 564 565 566 567 568 569 570 571 572 573 574 575 576 577 578 579 580 581 582 583 584 585 586 587 588 589 590 591 597 598 599 600 601 602 603 604 605 606 607 608 609 610 611
3313 OK Completed
3314 UID SEARCH FLAGGED
* BAD Invalid tag
* SEARCH
3314 OK Completed
* BAD Invalid tag
3315 UID SEARCH ANSWERED
* SEARCH 314 315 339 484
3315 OK Completed
3316 UID SEARCH KEYWORD gnus-forward
* BAD Invalid tag
* SEARCH 485
3316 OK Completed
* BAD Invalid tag
3317 UID SEARCH RECENT
* SEARCH
3317 OK Completed
3318 FETCH 1,* UID
* BAD Invalid tag
* 1 FETCH (UID 3)
* 599 FETCH (UID 611)
3318 OK Completed
* BAD Invalid tag
3319 UNSELECT
3319 OK Completed
3320 APPEND "INBOX.outbox" {441}
* BAD Invalid tag
+ go ahead
From: Alexander Kotelnikov <sacha@myxomop.com>
To: Alexander Kotelnikov <sacha@debian.org>
Subject: test again
Organization: Global disintoxication
Mail-Copies-To: never
Date: Tue, 11 Oct 2005 21:20:10 +0400
Message-ID: <87k6gkged1.fsf@vinci.loc>
User-Agent: Gnus/5.110004 (No Gnus v0.4) Emacs/21.4 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii

..
-- 
Alexander Kotelnikov
Saint-Petersburg, Russia
3320 NO Message contains invalid header
* BAD Invalid tag
* BAD Invalid tag

[-- Attachment #3: Type: text/plain, Size: 115 bytes --]


BAD Invalid tag after almost any command. What does this mean?

-- 
Alexander Kotelnikov
Saint-Petersburg, Russia

Re: imap troubles, especially with storing outgoing mail

[Simon Josefsson]

Alexander Kotelnikov <sacha@myxomop.com> writes:

> Hello.
>
> I just noticed that my outgoing mail is not stored in INBOX.outbox on
> by imap server, switched imap-log to t and look, what I have seen:
>
> * STATUS INBOX.junk.wad (UIDNEXT 61 UIDVALIDITY 1102336563 UNSEEN 0)
> 3309 OK Completed
> * BAD Invalid tag
...
> BAD Invalid tag after almost any command. What does this mean?

Could this be that you are using a transport that strips CRLF and that
imap.el still send CRLF?  The CRLF might confuse the server's parser,
and it might be seen as a new command tag, or something.  If so, try
frobbing imap-client-eol or possibly imap-server-eol to "\n".

Re: imap troubles, especially with storing outgoing mail

[Alexander Kotelnikov]

>>>>> On Wed, 12 Oct 2005 02:47:00 +0200
>>>>> "SJ" == Simon Josefsson <jas@extundo.com> wrote:
SJ> 
SJ> Alexander Kotelnikov <sacha@myxomop.com> writes:
>> Hello.
>> 
>> I just noticed that my outgoing mail is not stored in INBOX.outbox on
>> by imap server, switched imap-log to t and look, what I have seen:
>> 
>> * STATUS INBOX.junk.wad (UIDNEXT 61 UIDVALIDITY 1102336563 UNSEEN 0)
>> 3309 OK Completed
>> * BAD Invalid tag
SJ> ...
>> BAD Invalid tag after almost any command. What does this mean?
SJ> 
SJ> Could this be that you are using a transport that strips CRLF and that
SJ> imap.el still send CRLF?  The CRLF might confuse the server's parser,
SJ> and it might be seen as a new command tag, or something.  If so, try
SJ> frobbing imap-client-eol or possibly imap-server-eol to "\n".

(setq imap-client-eol "\n") helped me, thanks.

Does this means that my transport (stunnel) translated each 
<command> CRLF 
into
<command> CR CRLF
?

-- 
Alexander Kotelnikov
Saint-Petersburg, Russia

Re: imap troubles, especially with storing outgoing mail

[Alexander Kotelnikov]

>>>>> On Wed, 12 Oct 2005 14:42:38 +0400
>>>>> "AK" == Alexander Kotelnikov <sacha@myxomop.com> wrote:
AK> 
>>>>> On Wed, 12 Oct 2005 02:47:00 +0200
>>>>> "SJ" == Simon Josefsson <jas@extundo.com> wrote:
SJ> 
SJ> Alexander Kotelnikov <sacha@myxomop.com> writes:
>>> Hello.
>>> 
>>> I just noticed that my outgoing mail is not stored in INBOX.outbox on
>>> by imap server, switched imap-log to t and look, what I have seen:
>>> 
>>> * STATUS INBOX.junk.wad (UIDNEXT 61 UIDVALIDITY 1102336563 UNSEEN 0)
>>> 3309 OK Completed
>>> * BAD Invalid tag
SJ> ...
>>> BAD Invalid tag after almost any command. What does this mean?
SJ> 
SJ> Could this be that you are using a transport that strips CRLF and that
SJ> imap.el still send CRLF?  The CRLF might confuse the server's parser,
SJ> and it might be seen as a new command tag, or something.  If so, try
SJ> frobbing imap-client-eol or possibly imap-server-eol to "\n".
AK> 
AK> (setq imap-client-eol "\n") helped me, thanks.

Sorry, it did not. I realised this sending the previous
message. Tweaking imap-(server|client)-eol leads to one of two
scenarios:
1. either gnus hangs after 
72 APPEND "INBOX.outbox" {431}
appears in *imap-log*, in this case no '* BAD Invalid tag' are found.
2. or *imap-log* shows something like
72 APPEND "INBOX.outbox" {431}
* BAD Invalid tag
+ go ahead
<message here>
72 NO Message contains invalid header
* BAD Invalid tag
* BAD Invalid tag

-- 
Alexander Kotelnikov
Saint-Petersburg, Russia

Re: imap troubles, especially with storing outgoing mail

[Simon Josefsson]

Alexander Kotelnikov <sacha@myxomop.com> writes:

>>>>>> On Wed, 12 Oct 2005 02:47:00 +0200
>>>>>> "SJ" == Simon Josefsson <jas@extundo.com> wrote:
> SJ> 
> SJ> Alexander Kotelnikov <sacha@myxomop.com> writes:
>>> Hello.
>>> 
>>> I just noticed that my outgoing mail is not stored in INBOX.outbox on
>>> by imap server, switched imap-log to t and look, what I have seen:
>>> 
>>> * STATUS INBOX.junk.wad (UIDNEXT 61 UIDVALIDITY 1102336563 UNSEEN 0)
>>> 3309 OK Completed
>>> * BAD Invalid tag
> SJ> ...
>>> BAD Invalid tag after almost any command. What does this mean?
> SJ> 
> SJ> Could this be that you are using a transport that strips CRLF and that
> SJ> imap.el still send CRLF?  The CRLF might confuse the server's parser,
> SJ> and it might be seen as a new command tag, or something.  If so, try
> SJ> frobbing imap-client-eol or possibly imap-server-eol to "\n".
>
> (setq imap-client-eol "\n") helped me, thanks.
>
> Does this means that my transport (stunnel) translated each 
> <command> CRLF 
> into
> <command> CR CRLF
> ?

Yes, or perhaps LF CRLF.  In any case, I remember that some of the
various tunnel tools did not like CRLF and behaved strange when they
saw them.

If you have trouble with APPEND, you may also want to investigate
imap-calculate-literal-size-first.

Re: imap troubles, especially with storing outgoing mail

[Simon Josefsson]

Alexander Kotelnikov <sacha@myxomop.com> writes:

>>>>>> On Wed, 12 Oct 2005 14:42:38 +0400
>>>>>> "AK" == Alexander Kotelnikov <sacha@myxomop.com> wrote:
> AK> 
>>>>>> On Wed, 12 Oct 2005 02:47:00 +0200
>>>>>> "SJ" == Simon Josefsson <jas@extundo.com> wrote:
> SJ> 
> SJ> Alexander Kotelnikov <sacha@myxomop.com> writes:
>>>> Hello.
>>>> 
>>>> I just noticed that my outgoing mail is not stored in INBOX.outbox on
>>>> by imap server, switched imap-log to t and look, what I have seen:
>>>> 
>>>> * STATUS INBOX.junk.wad (UIDNEXT 61 UIDVALIDITY 1102336563 UNSEEN 0)
>>>> 3309 OK Completed
>>>> * BAD Invalid tag
> SJ> ...
>>>> BAD Invalid tag after almost any command. What does this mean?
> SJ> 
> SJ> Could this be that you are using a transport that strips CRLF and that
> SJ> imap.el still send CRLF?  The CRLF might confuse the server's parser,
> SJ> and it might be seen as a new command tag, or something.  If so, try
> SJ> frobbing imap-client-eol or possibly imap-server-eol to "\n".
> AK> 
> AK> (setq imap-client-eol "\n") helped me, thanks.
>
> Sorry, it did not. I realised this sending the previous
> message. Tweaking imap-(server|client)-eol leads to one of two
> scenarios:
> 1. either gnus hangs after 
> 72 APPEND "INBOX.outbox" {431}
> appears in *imap-log*, in this case no '* BAD Invalid tag' are found.
> 2. or *imap-log* shows something like
> 72 APPEND "INBOX.outbox" {431}
> * BAD Invalid tag
> + go ahead
> <message here>
> 72 NO Message contains invalid header
> * BAD Invalid tag
> * BAD Invalid tag

I think (setq imap-calculate-literal-size-first t) would fix this.

Re: imap troubles, especially with storing outgoing mail

[Alexander Kotelnikov]

>>>>> On Wed, 12 Oct 2005 18:08:11 +0200
>>>>> "SJ" == Simon Josefsson <jas@extundo.com> wrote:
SJ> 
SJ> Alexander Kotelnikov <sacha@myxomop.com> writes:
>>>>>>> On Wed, 12 Oct 2005 14:42:38 +0400
>>>>>>> "AK" == Alexander Kotelnikov <sacha@myxomop.com> wrote:
AK> 
>>>>>>> On Wed, 12 Oct 2005 02:47:00 +0200
>>>>>>> "SJ" == Simon Josefsson <jas@extundo.com> wrote:
SJ> 
SJ> Alexander Kotelnikov <sacha@myxomop.com> writes:
>>>>> Hello.
>>>>> 
>>>>> I just noticed that my outgoing mail is not stored in INBOX.outbox on
>>>>> by imap server, switched imap-log to t and look, what I have seen:
>>>>> 
>>>>> * STATUS INBOX.junk.wad (UIDNEXT 61 UIDVALIDITY 1102336563 UNSEEN 0)
>>>>> 3309 OK Completed
>>>>> * BAD Invalid tag
SJ> ...
>>>>> BAD Invalid tag after almost any command. What does this mean?
SJ> 
SJ> Could this be that you are using a transport that strips CRLF and that
SJ> imap.el still send CRLF?  The CRLF might confuse the server's parser,
SJ> and it might be seen as a new command tag, or something.  If so, try
SJ> frobbing imap-client-eol or possibly imap-server-eol to "\n".
AK> 
AK> (setq imap-client-eol "\n") helped me, thanks.
>> 
>> Sorry, it did not. I realised this sending the previous
>> message. Tweaking imap-(server|client)-eol leads to one of two
>> scenarios:
>> 1. either gnus hangs after 
>> 72 APPEND "INBOX.outbox" {431}
>> appears in *imap-log*, in this case no '* BAD Invalid tag' are found.
>> 2. or *imap-log* shows something like
>> 72 APPEND "INBOX.outbox" {431}
>> * BAD Invalid tag
>> + go ahead
>> <message here>
>> 72 NO Message contains invalid header
>> * BAD Invalid tag
>> * BAD Invalid tag
SJ> 
SJ> I think (setq imap-calculate-literal-size-first t) would fix this.

Unfortunately, it does not.

-- 
Alexander Kotelnikov
Saint-Petersburg, Russia

Re: imap troubles, especially with storing outgoing mail

[Simon Josefsson]

Alexander Kotelnikov <sacha@myxomop.com> writes:

> AK> (setq imap-client-eol "\n") helped me, thanks.
>>> 
>>> Sorry, it did not. I realised this sending the previous
>>> message. Tweaking imap-(server|client)-eol leads to one of two
>>> scenarios:
>>> 1. either gnus hangs after 
>>> 72 APPEND "INBOX.outbox" {431}
>>> appears in *imap-log*, in this case no '* BAD Invalid tag' are found.
>>> 2. or *imap-log* shows something like
>>> 72 APPEND "INBOX.outbox" {431}
>>> * BAD Invalid tag
>>> + go ahead
>>> <message here>
>>> 72 NO Message contains invalid header
>>> * BAD Invalid tag
>>> * BAD Invalid tag
> SJ> 
> SJ> I think (setq imap-calculate-literal-size-first t) would fix this.
>
> Unfortunately, it does not.

Maybe you could use tcpdump or similar to find out exactly what is
sent and where the error is?  I.e., check the EOL variant used, and
the literal size ("431" above) and compare it against the message size
(including CRLF).  And then try some modifications to imap.el to see
if it works.

Hm, just an idea: i-c-l-s-f is a buffer local variable.  You should
ideally set it in the " *nnimap* foo" (note leading space) buffer, if
your server is called "foo".