Re: An easy imap question

"S.A. Birl" <[email protected]>
Newsgroups gmane.mail.pine.general
Organization Temple University
Message-ID <Pine.GSO.4.63.0608161252140.8299@pbaprcg>
On Aug 16, 2006, Bert Driehuis ([email protected]) typed:

> On Wed, 16 Aug 2006, S.A. Birl wrote:
>
> 	[snip]
>
> >  But now that I look closer, you have your at "incoming folders"
> >  whereas my options reside at "folder-collections"
> >
> >  Maybe that's why it isnt working.  What an oversight on my part.
> >
> >  Hmmm... I dont want to access that IMAP server on constant basis.
> >  So having it in "incoming folders" is not an option for me.
>
> Have you tried it? I'm not accessing them on a constant basis either. I open
> them as I need them.



Im TAB'ing through my incoming folders.  In the past, Pine has always
made a connection to the IMAP server as soon as it hits that folder,
thus prompting for a password.




On Aug 16, 2006, Lucio Chiappetti ([email protected]) typed:

> Don't see the problem. As far as I can understand, having it in "incoming
> folders" does not imply it is kept open or checked, it's just a
> convenience to have it listed together with the INBOX.
>
> Maybe you do not have a pinerc syntax problem but a permission problem.
> Have you looked at the pine-debug files ?



Oddly, unless I overlooked an error message, I didnt see anything.
But here's what the journal has:

-----
Bad context, No '[' in context : {server.temple.edu/ssl/novalidate-cert}INBOX
  Debug file: /export/home/sbirl/.pine-debug1 (level=5 imap=4)
-----

I put this back into my rc file:
INBOX {server.temple.edu/ssl/novalidate-cert}INBOX,

I have pine aliased to pine -d flush,imap=4,numfiles=2,verbose=5,timestamp

I think the highest for verbose is 9?  I'll try that and see if
anything new pops up.

_______________________________________________
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.