Ole Jacobsen | 17 Jun 2012 02:33
Picon
Favicon

That dreaded "message shrank" error


It seems that this new Exchange 2010 server has some IMAP issues.
Some message notifications when Alpine is running come in the
form of:

"[{mail.cisco.com:143/imap/tls/novalidate-cert/user="ole"}inbox : 
Unknown message data: 2 RECENT]"

Instead of the familiar new header.

Alpine gets confused about the size of the message, I guess it
does not agree with what the server says and when I try to save
the message it warns that there may be 'data corruption' and
that the message has shrunk.

I understand that this is a known problem, but I haven't seen
a real solution, Eduardo are you listening?

I am running Alpine 2.01(1266), with Eduardo's auto-indentation
fix.

Ole

Ole J. Jacobsen
Editor and Publisher,  The Internet Protocol Journal
Cisco Systems
Tel: +1 408-527-8972   Mobile: +1 415-370-4628
E-mail: ole@...  URL: http://www.cisco.com/ipj
Skype: organdemo

(Continue reading)

Joshua Miller | 17 Jun 2012 07:42
Picon

Re: That dreaded "message shrank" error

Sorry this is probably not the solution you are looking for, but fetchmail works.


See "man fetchmail" and look at the "-r" option. For example:

fetchmail -r "Sent Items"

I know what you mean though... I'm not sure what's going on there.

See also: 

That's an MS incident opened regarding a similar issue related to this. Basically, it was started because S/MIME signing of messages broke when viewing the message over IMAP on an exchange server. This was confirmed by setting up outlook, which did see the signature as valid using exchange protocol, to use IMAP to connect to the same account. When using IMAP, even outlook showed the signature was invalid, meaning the message contents changed in transit. Since it saw it as fine using exchange protocol, and through other tests (ex. CC'ing an account on a normal IMAP server and comparing the results), we know that Exchange is mucking about with the message contents when you get them over IMAP.

One "work around" I found was to add a newline after my signature.

When looking at the messages, it appeared that Exchange was stuffing an extra newline in between message parts when  you fetched it over IMAP. It wants to have a newline between the last piece of text and the message separator (I think).

FWIW, it's very unlikely you'll get alpine to "fix" this issue. The issue also exists with any mail client talking to Exchange over IMAP. Alpine just happens to note the issue. Adding S/MIME signing of messages just added a way to pinpoint the issue... it worked before, and the CC signature worked to a different server, and exchange protocol worked, but outlook talking to exchange over IMAP caused signature validation to fail due to the issue you're reporting.

I'd recommend referencing the MS incident above and contacting MS. Their IMAP protocol support is, IMO, broken.
Best of luck,
--
Josh I.

On Sat, Jun 16, 2012 at 8:33 PM, Ole Jacobsen <ole-FYB4Gu1CFyUAvxtiuMwx3w@public.gmane.org> wrote:

It seems that this new Exchange 2010 server has some IMAP issues.
Some message notifications when Alpine is running come in the
form of:

"[{mail.cisco.com:143/imap/tls/novalidate-cert/user="ole"}inbox :
Unknown message data: 2 RECENT]"

Instead of the familiar new header.

Alpine gets confused about the size of the message, I guess it
does not agree with what the server says and when I try to save
the message it warns that there may be 'data corruption' and
that the message has shrunk.

I understand that this is a known problem, but I haven't seen
a real solution, Eduardo are you listening?

I am running Alpine 2.01(1266), with Eduardo's auto-indentation
fix.

Ole


Ole J. Jacobsen
Editor and Publisher,  The Internet Protocol Journal
Cisco Systems
Tel: +1 408-527-8972   Mobile: +1 415-370-4628
E-mail: ole-FYB4Gu1CFyUAvxtiuMwx3w@public.gmane.org  URL: http://www.cisco.com/ipj
Skype: organdemo

_______________________________________________
Alpine-info mailing list
Alpine-info <at> u.washington.edu
http://mailman2.u.washington.edu/mailman/listinfo/alpine-info

<div>
<p>Sorry this is probably not the solution you are looking for, but fetchmail works.</p>
<div><br></div>
<div>See "man fetchmail" and look at the "-r" option. For example:</div>
<div><br></div>
<div>fetchmail -r "Sent Items"</div>
<div><br></div>
<div>I know what you mean though... I'm not sure what's going on there.</div>
<div><br></div>
<div>See also:&nbsp;<br><div><a href="https://premier.microsoft.com/viewincidents.aspx?&amp;incno=111022459547948">https://premier.microsoft.com/viewincidents.aspx?&amp;incno=111022459547948</a></div>
<div><br></div>
<div>That's an MS incident opened regarding a similar issue related to this. Basically, it was started because S/MIME signing of messages broke when viewing the message over IMAP on an exchange server. This was confirmed by setting up outlook, which did see the signature as valid using exchange protocol, to use IMAP to connect to the same account. When using IMAP, even outlook showed the signature was invalid, meaning the message contents changed in transit. Since it saw it as fine using exchange protocol, and through other tests (ex. CC'ing an account on a normal IMAP server and comparing the results), we know that Exchange is mucking about with the message contents when you get them over IMAP.</div>
<div><br></div>
<div>One "work around" I found was to add a newline after my signature.</div>
<div><br></div>
<div>When looking at the messages, it appeared that Exchange was stuffing an extra newline in between message parts when &nbsp;you fetched it over IMAP. It wants to have a newline between the last piece of text and the message separator (I think).</div>
<div><br></div>
<div>FWIW, it's very unlikely you'll get alpine to "fix" this issue. The issue also exists with any mail client talking to Exchange over IMAP. Alpine just happens to note the issue. Adding S/MIME signing of messages just added a way to pinpoint the issue... it worked before, and the CC signature worked to a different server, and exchange protocol worked, but outlook talking to exchange over IMAP caused signature validation to fail due to the issue you're reporting.</div>
<div><br></div>
<div>I'd recommend referencing the MS incident above and contacting MS. Their IMAP protocol support is, IMO, broken.</div>
<div>Best of luck,</div>
<div>--</div>
<div>Josh I.</div>
<div>
<br><div class="gmail_quote">
On Sat, Jun 16, 2012 at 8:33 PM, Ole Jacobsen <span dir="ltr">&lt;<a href="mailto:ole@..." target="_blank">ole@...</a>&gt;</span> wrote:<br><blockquote class="gmail_quote">
<br>
It seems that this new Exchange 2010 server has some IMAP issues.<br>
Some message notifications when Alpine is running come in the<br>
form of:<br><br>
"[{<a href="http://mail.cisco.com:143/imap/tls/novalidate-cert/user=" target="_blank">mail.cisco.com:143/imap/tls/novalidate-cert/user=</a>"ole"}inbox :<br>
Unknown message data: 2 RECENT]"<br><br>
Instead of the familiar new header.<br><br>
Alpine gets confused about the size of the message, I guess it<br>
does not agree with what the server says and when I try to save<br>
the message it warns that there may be 'data corruption' and<br>
that the message has shrunk.<br><br>
I understand that this is a known problem, but I haven't seen<br>
a real solution, Eduardo are you listening?<br><br>
I am running Alpine 2.01(1266), with Eduardo's auto-indentation<br>
fix.<br><br>
Ole<br><br><br>
Ole J. Jacobsen<br>
Editor and Publisher, &nbsp;The Internet Protocol Journal<br>
Cisco Systems<br>
Tel: <a href="tel:%2B1%20408-527-8972" value="+14085278972">+1 408-527-8972</a> &nbsp; Mobile: <a href="tel:%2B1%20415-370-4628" value="+14153704628">+1 415-370-4628</a><br>
E-mail: <a href="mailto:ole@...">ole@...</a> &nbsp;URL: <a href="http://www.cisco.com/ipj" target="_blank">http://www.cisco.com/ipj</a><br>
Skype: organdemo<br><br>
_______________________________________________<br>
Alpine-info mailing list<br><a href="mailto:Alpine-info <at> u.washington.edu">Alpine-info <at> u.washington.edu</a><br><a href="http://mailman2.u.washington.edu/mailman/listinfo/alpine-info" target="_blank">http://mailman2.u.washington.edu/mailman/listinfo/alpine-info</a><br>
</blockquote>
</div>
<br>
</div>
</div>
</div>
Ole Jacobsen | 17 Jun 2012 16:43
Picon
Favicon

Re: That dreaded "message shrank" error


Joshua,

Thanks for the explanation. I was looking for a way to supress the
error messages in alpine, sort of like you can tell it to ignore
certificate checking on the incoming/outgoing mail server. I thought
I had seen an alpine patch that mentioned this...

I also found this info:

http://social.technet.microsoft.com/Forums/en-US/exchange2010/thread/551d57f6-fcd6-4bc4-940c-704e2c94
beb7

"The solution is on a per-user basis to use Set-CASMailbox user 
 -ImapUseProtocolDefaults:$false -ImapEnableExactRFC822Size:$true

 or on a server basis use Set-ImapSettings -EnableExactRFC822Size:$true

 Note that it will require additional overhead so I'd suggest only 
 enabling the option for people using clients that exhibit the issue. 
 Pine/Alpine is one and I've heard it reported with Thunderbird also."

Will look into fetchmail also.

Ole

Ole J. Jacobsen
Editor and Publisher,  The Internet Protocol Journal
Cisco Systems
Tel: +1 408-527-8972   Mobile: +1 415-370-4628
E-mail: ole@...  URL: http://www.cisco.com/ipj
Skype: organdemo

On Sun, 17 Jun 2012, Joshua Miller wrote:

> Sorry this is probably not the solution you are looking for, but fetchmail
> works.
> 
> See "man fetchmail" and look at the "-r" option. For example:
> 
> fetchmail -r "Sent Items"
> 
> I know what you mean though... I'm not sure what's going on there.
> 
> See also:
> https://premier.microsoft.com/viewincidents.aspx?&incno=111022459547948
> 
> That's an MS incident opened regarding a similar issue related to this.
> Basically, it was started because S/MIME signing of messages broke when
> viewing the message over IMAP on an exchange server. This was confirmed by
> setting up outlook, which did see the signature as valid using exchange
> protocol, to use IMAP to connect to the same account. When using IMAP, even
> outlook showed the signature was invalid, meaning the message contents
> changed in transit. Since it saw it as fine using exchange protocol, and
> through other tests (ex. CC'ing an account on a normal IMAP server and
> comparing the results), we know that Exchange is mucking about with the
> message contents when you get them over IMAP.
> 
> One "work around" I found was to add a newline after my signature.
> 
> When looking at the messages, it appeared that Exchange was stuffing an
> extra newline in between message parts when  you fetched it over IMAP. It
> wants to have a newline between the last piece of text and the message
> separator (I think).
> 
> FWIW, it's very unlikely you'll get alpine to "fix" this issue. The issue
> also exists with any mail client talking to Exchange over IMAP. Alpine just
> happens to note the issue. Adding S/MIME signing of messages just added a
> way to pinpoint the issue... it worked before, and the CC signature worked
> to a different server, and exchange protocol worked, but outlook talking to
> exchange over IMAP caused signature validation to fail due to the issue
> you're reporting.
> 
> I'd recommend referencing the MS incident above and contacting MS. Their
> IMAP protocol support is, IMO, broken.
> Best of luck,
> --
> Josh I.
> 
> On Sat, Jun 16, 2012 at 8:33 PM, Ole Jacobsen <ole@...> wrote:
> 
> >
> > It seems that this new Exchange 2010 server has some IMAP issues.
> > Some message notifications when Alpine is running come in the
> > form of:
> >
> > "[{mail.cisco.com:143/imap/tls/novalidate-cert/user="ole"}inbox :
> > Unknown message data: 2 RECENT]"
> >
> > Instead of the familiar new header.
> >
> > Alpine gets confused about the size of the message, I guess it
> > does not agree with what the server says and when I try to save
> > the message it warns that there may be 'data corruption' and
> > that the message has shrunk.
> >
> > I understand that this is a known problem, but I haven't seen
> > a real solution, Eduardo are you listening?
> >
> > I am running Alpine 2.01(1266), with Eduardo's auto-indentation
> > fix.
> >
> > Ole
> >
> >
> > Ole J. Jacobsen
> > Editor and Publisher,  The Internet Protocol Journal
> > Cisco Systems
> > Tel: +1 408-527-8972   Mobile: +1 415-370-4628
> > E-mail: ole@...  URL: http://www.cisco.com/ipj
> > Skype: organdemo
> >
> > _______________________________________________
> > Alpine-info mailing list
> > Alpine-info <at> u.washington.edu
> > http://mailman2.u.washington.edu/mailman/listinfo/alpine-info
> >
> 

Gmane