Headers are always empty on Fetch

[bitdisaster]

I'm trying to get read the HeaderId.Importance when I fetch messages. However the Headers property is always null. On the other side the Headers property is never null when I use GetMessage for the same set of messages.

[jstedfast]

Can you get a protocol log so I can take a look at what command is being sent and what the server is sending back?

[jstedfast]

FWIW, I just tested this and it works for me.

var headers = new HashSet<HeaderId> (new [] { HeaderId.Importance });
var summaries = client.Inbox.Fetch (0, -1, MessageSummaryItems.UniqueId, headers);
foreach (var summary in summaries) {
    foreach (var header in summary.Headers)
        Console.WriteLine (header);
}

Is this how you are doing it?

[jstedfast]

This is what the protocol log should look like (more-or-less):

C: A00000008 FETCH 1:* (UID BODY.PEEK[HEADER.FIELDS (IMPORTANCE)])
S: * 1 FETCH (UID 343 MODSEQ (38846) BODY[HEADER.FIELDS (IMPORTANCE)] {22}
S: Importance: Normal
S: 
S: )

[jstedfast]

Is the issue that if the Importance header doesn't exist, the summary.Headers property is null?

If so, I've just fixed that.

[bitdisaster]

Ah, sorry. My bad. I wasn't aware that I have to explicitly request the headers on the fetch. The not null on the summary.Headers property is still a welcomed change.
Thanks for the fast reply.

[jstedfast]

The MessageSummaryItems flags tell the ImapFolder which fields of the IMessageSummary object to request and fill-in.

It's a lot like reading just a subset of the columns from a database record.

[bitdisaster]

I was aware of MessageSummaryItems . But it has no impact on headers except for References. The clue was to define var headers = new HashSet (new [] { HeaderId.Importance }); and pass it to fetch.

[jstedfast]

oh, gotcha.