Looking at the get_rfc822_body code in Net::IMAP::Client and the FETCH section in RFC 3501 (pp. 53-57), I think this is part of the IMAP spec: "The \Seen flag is implicitly set; if this causes the flags to change, they SHOULD be included as part of the FETCH responses.".

There is a BODY.PEEK data item for the FETCH command that, unlike BODY (and thus RFC822, which is what this function uses), will avoid setting the flag. The module does not currently appear to support getting message bodies that way, but maybe the author could be persuaded to add that functionality.

In reply to Re: How to stop get_rfc822_body method of Net::IMAP::Client package to mark an unread email as read ? by AppleFritter
in thread How to stop get_rfc822_body method of Net::IMAP::Client package to mark an unread email as read ? by pankaj_it09

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • 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:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.