Some problems with POP3 accounts

[email protected]
Newsgroups gmane.mail.pine.general
Message-ID <[email protected]>

Hello people,

I have some problems with pine 4.64. The problems are described bellow. I'm not
sure, if you can prepare the similar settings for your pine, therefore I
include journal.

The main problem is in selecting correct POP3 folder. Many time the pine uses
some function to find if two folders are the same. In my configuration I have
two accounts [email protected] and [email protected]. I can see
problem with (1) using filters, (2) informing about new email, (3) showing
cross X for "new mail" mark in list of incoming folders (this is probably only
in pine with Chappa patches), (4) when I abort login to POP3 account
[email protected], I cannot open any other POP3 or IMAP account,
even if I was already connected (this is also only in pine with Chappa
patches).


Here is the journal with debug level 7 for the problem (1). You can see it's
trying filter for account xxxxxxxxxxxxxxxxxxx and checks to INBOX definition on
the same server but with different username. And the function return "yes" - I
think this function should return "no" for these two streams. I have this
problem on original pine and on pine with Chappa patches.

17:15:12.950985: Trying filter "xxxxxxxxxxxxxxxxxxx@seznam"
17:15:12.951013: same_stream: name->{pop3.seznam.cz/service=pop3/ssl/user=xxxxxxxxxxxxxxxxxxx}INBOX == stream->{pop3.seznam.cz:995/pop3/s
17:15:12.951021: >sl/user="yyyy.yyyyyy"}INBOX: yes
17:15:12.951050: same_stream: name->{ssl.atlas.cz/ssl/user=z.zzzz/imap}xxxxxxxxxxxxxxxxxxx == stream->{pop3.seznam.cz:995/pop3/ssl/user="
17:15:12.951057: >yyyy.yyyyyy"}INBOX: no dice
17:15:12.951068: searchset=
17:15:12.951075:  1
17:15:12.951112: Opening "[email protected]" DONE [not actually shown]
17:15:12.951160: Processing filter "xxxxxxxxxxxxxxxxxxx@seznam"     



This is journal for problem (2) and probably for problem (3) - openning folder
[email protected] with 1 new message, but at the end it shows message about
new email in folder [email protected] (but the pine was not logged
in the account [email protected] since start). This problem is
similar to problem with reporting new messages in "incoming folder list"
window, there is a cross with "[1/1]" on line with account xxxxxxxxxxxxxxxxxxx.
I found this problem only on pine with Chappa patches, maybe there is not such
functionality in original pine.

17:15:12.481747: Opening "[email protected]"     
17:15:12.481850: IMAP DEBUG 17:15:12 5/17: QUIT
17:15:12.713508: IMAP DEBUG 17:15:12 5/17: +OK Closing connection, see you later.
17:15:12.713529: IMAP 17:15:12 5/17 mm_notify bye: {pop3.seznam.cz:995/pop3/ssl/user="yyyy.yyyyyy"}INBOX: Closing connection, see you lat
17:15:12.713537: >er.
17:15:12.744863: IMAP 17:15:12 5/17 mm_log babble: Trying IP address [194.228.32.46]
17:15:12.831512: IMAP DEBUG 17:15:12 5/17: +OK Hello, this is Seznam POP3 server 2.3.9-3.
17:15:12.831540: IMAP 17:15:12 5/17 mm_log babble: Hello, this is Seznam POP3 server 2.3.9-3.
17:15:12.831566: IMAP DEBUG 17:15:12 5/17: CAPA
17:15:12.836956: IMAP DEBUG 17:15:12 5/17: -ERR Unknown command.
17:15:12.836975: IMAP DEBUG 17:15:12 5/17: AUTH
17:15:12.847843: IMAP DEBUG 17:15:12 5/17: -ERR Unknown command.
17:15:12.847932: IMAP DEBUG 17:15:12 5/17: USER yyyy.yyyyyy
17:15:12.856206: IMAP DEBUG 17:15:12 5/17: +OK Enter your password please.
17:15:12.856226: IMAP DEBUG 17:15:12 5/17: <suppressed>
17:15:12.939368: IMAP DEBUG 17:15:12 5/17: +OK 1 6945
17:15:12.939390: IMAP DEBUG 17:15:12 5/17: STAT
17:15:12.950260: IMAP DEBUG 17:15:12 5/17: +OK 1 6945
17:15:12.950287: === mm_exists(1,{pop3.seznam.cz:995/pop3/ssl/user="yyyy.yyyyyy"}INBOX) called ===
17:15:12.950400: Opened folder "{pop3.seznam.cz:995/pop3/ssl/user="yyyy.yyyyyy"}INBOX" with 1 messages
17:15:12.950531: process_filter_patterns(stream={pop3.seznam.cz/service=pop3/ssl/user=yyyy.yyyyyy}INBOX, recent=0)
17:15:12.952215: Trying filters ...................
17:15:12.952307: filtering done
17:15:12.952389: Sorting by Date
17:15:12.952411: IMAP DEBUG 17:15:12 5/17: NOOP
17:15:12.957998: IMAP DEBUG 17:15:12 5/17: +OK 
17:15:12.958029: IMAP DEBUG 17:15:12 5/17: NOOP
17:15:12.973118: IMAP DEBUG 17:15:12 5/17: +OK 
17:15:12.973288: First_sorted_flagged returning winner = 1
17:15:12.973304:  ---- MAIL INDEX ----
17:15:12.973312:  ---- INDEX MANAGER ----
17:15:12.973791: IMAP DEBUG 17:15:12 5/17: NOOP
17:15:12.985499: IMAP DEBUG 17:15:12 5/17: +OK 
17:15:12.985531: IMAP DEBUG 17:15:12 5/17: RETR 1
17:15:13.047660: IMAP DEBUG 17:15:13 5/17: +OK Message follows (6945 bytes).
17:15:13.366392: Folder "[email protected]" opened with 1 message - 1 new
17:15:15.380247:  - process_cmd(cmd=505) -
17:15:15.380272:   -----  MAIL VIEW  -----
17:15:15.380832: -- gf_pipe: 
17:15:15.381008: done.
17:15:15.381025: - mailcap_can_display -
17:15:15.381034: - mc_get_command(Text/PLAIN) -
17:15:15.381064: - mc_init -
17:15:15.381104: mailcap: process_file: /home/user/.mailcap
17:15:15.395398: mailcap: process_file: /etc/mailcap
17:15:15.420565: mailcap: process_file: /usr/etc/mailcap
17:15:15.420594: mailcap: /usr/etc/mailcap doesn't exist
17:15:15.420603: mailcap: process_file: /usr/local/etc/mailcap
17:15:15.420629: mailcap: /usr/local/etc/mailcap doesn't exist
17:15:15.420642: mc_ctype_match: application/vnd.sun.xml.writer == Text / PLAIN ? + the others
17:15:15.420979: - mc_passes_test -
17:15:15.477577: -- gf_pipe: 
17:15:15.482137: done.
17:15:15.482262: -- gf_pipe: 
17:15:15.482307: done.
17:15:23.490222: IMAP DEBUG 17:15:23 5/17: 01000064 NOOP
17:15:23.516660: IMAP DEBUG 17:15:23 5/17: 01000064 OK NOOP completed
17:15:23.516735: IMAP DEBUG 17:15:23 5/17: 01000065 NOOP
17:15:23.549349: IMAP DEBUG 17:15:23 5/17: 01000065 OK NOOP completed
17:15:23.549647: IMAP DEBUG 17:15:23 5/17: NOOP
17:15:23.568315: IMAP DEBUG 17:15:23 5/17: +OK 
17:15:23.569426: IMAP DEBUG 17:15:23 5/17: NOOP
17:15:23.579289: IMAP DEBUG 17:15:23 5/17: +OK 
17:15:23.583745: New mail in folder "[email protected]"


Bellow is journal with debug level 8 for the problem (4). You can see
connecting to folder [email protected], then aborting login. Then I
wanted to open folder [email protected], but the pine said "cancelled by
user" and even didn't try to connect.

18:30:34.544134: About to open folder "[email protected]"    inbox is: "INBOX"
18:30:34.544159: broach_folder: nickname for {pop3.seznam.cz/service=pop3/ssl/user=xxxxxxxxxxxxxxxxxxx}INBOX is xxxxxxxxxxxxxxxxxxx@sezna
18:30:34.544166: >m.cz
18:30:34.544216: Opening "[email protected]"     
18:30:34.544276: pine_mail_open: opening "{pop3.seznam.cz/service=pop3/ssl/user=xxxxxxxxxxxxxxxxxxx}INBOX" (stream was NULL) openflags=0x
18:30:34.544284: >5000000  SP_USERFLDR SP_USEPOOL (18:30:34 5/17)
18:30:34.545713: IMAP 18:30:34 5/17 mm_log babble: Trying IP address [212.80.76.46]
18:30:34.633252: IMAP DEBUG 18:30:34 5/17: +OK Hello, this is Seznam POP3 server 2.3.9-3.
18:30:34.633278: IMAP 18:30:34 5/17 mm_log babble: Hello, this is Seznam POP3 server 2.3.9-3.
18:30:34.633307: IMAP DEBUG 18:30:34 5/17: CAPA
18:30:34.643321: IMAP DEBUG 18:30:34 5/17: -ERR Unknown command.
18:30:34.643345: IMAP DEBUG 18:30:34 5/17: AUTH
18:30:34.655320: IMAP DEBUG 18:30:34 5/17: -ERR Unknown command.
18:30:34.655451: === optionally_enter called ===
18:30:35.429699: IMAP 18:30:35 5/17 mm_log error: Login aborted
18:30:35.429737: IMAP DEBUG 18:30:35 5/17: QUIT
18:30:35.441352: IMAP DEBUG 18:30:35 5/17: +OK Closing connection, see you later.
18:30:35.441373: IMAP 18:30:35 5/17 mm_notify bye: {pop3.seznam.cz/service=pop3/ssl/user=xxxxxxxxxxxxxxxxxxx}INBOX: Closing connection, s
18:30:35.441380: >ee you later.
18:30:35.441530: Opened folder (nil) "nil" (context: "%s")
18:30:35.441549: Old folder: "INBOX"
18:30:35.441558: Reactivate inbox -1 0 0x8581d00
18:30:35.441633: conf_scroll_screen()
18:30:35.441676: ******** new mail returning -1  ********
18:30:35.441989: Login aborted
18:30:36.773313:     ---- FOLDER LISTER ----
18:30:36.773920: ******** new mail returning -1  ********
18:30:36.773960: Login aborted
18:30:37.165952: PROCESS_CMD return: 1
18:30:37.166001: About to open folder "INBOX"    inbox is: "INBOX"
18:30:37.166025:  ---- MAIL INDEX ----
18:30:37.166078:  ---- INDEX MANAGER ----
18:30:37.166135: ******** new mail returning -1  ********
18:30:37.166206: --update_index--
18:30:37.166549: --update_index done
18:30:37.938761:  - process_cmd(cmd=507) -
18:30:37.938772: MAIL_CMD: going to folder/collection menu
18:30:37.938789: === folder_screen called ====
18:30:37.938799:     ---- FOLDER LISTER ----
18:30:37.939407: ******** new mail returning -1  ********
18:30:37.939442: Login aborted
18:30:39.479891: PROCESS_CMD return: 1
18:30:39.479940: About to open folder "INBOX"    inbox is: "INBOX"
18:30:39.479957:  ---- MAIL INDEX ----
18:30:39.479966:  ---- INDEX MANAGER ----
18:30:39.480010: ******** new mail returning -1  ********
18:30:39.480079: --update_index--
18:30:39.480364: --update_index done
18:30:39.939413:  - process_cmd(cmd=507) -
18:30:39.939423: MAIL_CMD: going to folder/collection menu
18:30:39.939440: === folder_screen called ====
18:30:39.939450:     ---- FOLDER LISTER ----
18:30:39.940062: ******** new mail returning -1  ********
18:30:39.940098: ALL of folder list
18:30:41.199253: ******** new mail returning -1  ********
18:30:41.360423: ******** new mail returning -1  ********
18:30:42.545139: PROCESS_CMD return: 1
18:30:42.545186: About to open folder "[email protected]"    inbox is: "INBOX"
18:30:42.545210: broach_folder: nickname for {pop3.seznam.cz/service=pop3/ssl/user=yyyy.yyyyyy}INBOX is [email protected]
18:30:42.545260: Opening "[email protected]"     
18:30:42.545302: pine_mail_open: cancelled by user
18:30:42.545311: Opened folder (nil) "nil" (context: "%s")
18:30:42.545327: Old folder: "INBOX"
18:30:42.545336: Reactivate inbox -1 0 0x8581d00
18:30:42.545406: conf_scroll_screen()
18:30:42.545448: ******** new mail returning -1  ********


I have also one problem with Quoted printable in pine with and without chappa
patches. It's probably because of violation of RFC 2045-MIME about
quoted-printable length. The length should be up to 76 characters, but some
mailers (in my example it's seznam.cz) doesn't care of this limit and create
Subject header with quoted-printable encoded text longer. I have made
experiments with Subject line encoded QP and I found if the line is longer than
77 characters, pine doesn't decode the line. If the length is 77 and less
characters, Subject line is OK. Is there any possibility to update code to
parse these texts even if violating RFC?

This line is OK and subject is decoded from quoted printable:
Subject: =?ISO-8859-2?Q?P=F8=EDli=B9_=BElu=BBou=E8k=FD_k=F9=F2_=FAp=ECl_=EF=E1bel=E9?=

This line is not OK and pine show subject in QP encoding (which is hard to read):
Subject: =?ISO-8859-2?Q?P=F8=EDli=B9_=BElu=BBou=E8k=FD_k=F9=F2_=FAp=ECl_=EF=E1belsk=E9?=


Have a nice emailing with pine:)

Wolf.
_______________________________________________
Pine-info mailing list
[email protected]
http://mailman1.u.washington.edu/mailman/listinfo/pine-info
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.