Yes, that's what I did when I was writing my email app (just learning,
with Pike/GTK :). I think that is how the other clients do
it also.
Without a module, it would connect, list messages,
and foreach message, do a top [id] 0 (to just get the headers),
then parse out the Message-ID: field. I then kept a list
(in Pike, a multiset was easiest) of all msgid's I've seen already,
and only download a message (retr) that I hadn't seen.
Of course, the module would do most of the for you. You would just
have to keep a list of the msgid's.
The previous message said the same thing, I realize, but I wanted
to reiterate/confirm it.
Anyway...
riffraff
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
| |
For: |
|
Use: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.