fetchmail-users — User questions and discussion

Re: [fetchmail-users] IMAP IDLE doesn't work right with davmail server

[Rob M. <rob...@gm...>]

On Fri, May 2, 2014 at 8:15 PM, Grant Edwards <gra...@gm...> wrote:
>
> I'm trying to use fetchmail with the davmail IMAP server, and it
> doesn't seem to be working.  When new mail is received while the
> connection is in an IDLE command, the server sends EXITS and RECENT
> resonses, but fetchmail doesn't recognize them and never tries to
> fetch the messages.  If I kill fetchmail and restart it, it will then
> fetch the messages.
>
> Here's what happens after an initial fetch has completed and the IDLE
> command is sent:
>
> fetchmail: IMAP< A0012 OK FETCH completed
>  flushed
> fetchmail: IMAP> A0013 STORE 1 +FLAGS (\Seen \Deleted)
> fetchmail: IMAP< * 1 FETCH (UID 18266 FLAGS (\Seen \Deleted))
> fetchmail: IMAP< A0013 OK STORE completed
> fetchmail: IMAP> A0014 EXPUNGE
> fetchmail: IMAP< * 1 EXPUNGE
> fetchmail: IMAP< A0014 OK EXPUNGE completed
> fetchmail: selecting or re-polling default folder
> fetchmail: IMAP> A0015 IDLE
> fetchmail: IMAP< + idling
> fetchmail: IMAP< * 2 EXISTS
> fetchmail: IMAP> DONE
> fetchmail: IMAP< * 2 RECENT
> fetchmail: IMAP< * 5 EXISTS
> fetchmail: IMAP< * 5 RECENT
> fetchmail: IMAP< * 7 EXISTS
> fetchmail: IMAP< * 7 RECENT
> fetchmail: IMAP< * 8 EXISTS
> fetchmail: IMAP< * 8 RECENT
>
> That will continue as more e-mails are received...
>
> Any ideas?

What version number of Fetchmail are you using? If it isn't 6.3.26 try
upgrading and then repeat your test. Do you know what version number
of DavMail you are connecting to?

You'll also want to check section G3 of the FAQ
(http://fetchmail.berlios.de/fetchmail-FAQ.html#G3) for the
information the developer will want.

-- 
                 Please keep list traffic on the list.

Rob MacGregor
      Whoever fights monsters should see to it that in the process he
        doesn't become a monster.                  Friedrich Nietzsche

[fetchmail-users] IMAP IDLE doesn't work right with davmail server

[Grant E. <gra...@gm...>]

I'm trying to use fetchmail with the davmail IMAP server, and it
doesn't seem to be working.  When new mail is received while the
connection is in an IDLE command, the server sends EXITS and RECENT
resonses, but fetchmail doesn't recognize them and never tries to
fetch the messages.  If I kill fetchmail and restart it, it will then
fetch the messages.

Here's what happens after an initial fetch has completed and the IDLE
command is sent:

fetchmail: IMAP< A0012 OK FETCH completed
 flushed
fetchmail: IMAP> A0013 STORE 1 +FLAGS (\Seen \Deleted)
fetchmail: IMAP< * 1 FETCH (UID 18266 FLAGS (\Seen \Deleted))
fetchmail: IMAP< A0013 OK STORE completed
fetchmail: IMAP> A0014 EXPUNGE
fetchmail: IMAP< * 1 EXPUNGE
fetchmail: IMAP< A0014 OK EXPUNGE completed
fetchmail: selecting or re-polling default folder
fetchmail: IMAP> A0015 IDLE
fetchmail: IMAP< + idling 
fetchmail: IMAP< * 2 EXISTS
fetchmail: IMAP> DONE
fetchmail: IMAP< * 2 RECENT
fetchmail: IMAP< * 5 EXISTS
fetchmail: IMAP< * 5 RECENT
fetchmail: IMAP< * 7 EXISTS
fetchmail: IMAP< * 7 RECENT
fetchmail: IMAP< * 8 EXISTS
fetchmail: IMAP< * 8 RECENT

That will continue as more e-mails are received...

Any ideas?

-- 
Grant

Re: [fetchmail-users] Fetchmail

[jader f. <jad...@gm...>]

Openssl has support to Tlsv1.1 and Tlsv1.2 in the version 1.0.1g


2014-05-02 12:12 GMT-03:00 Rob MacGregor <rob...@gm...>:

> On Fri, May 2, 2014 at 2:36 PM, jader fabiano <jad...@gm...> wrote:
> > Hello!
> > I am developing a solution that it use fetchmail, and I have a doubt.
> > How can I specify to fetchmail uses tls1.1 or tls1.2?
> >
> > I did not find how i can do this.
>
> Quoting the man page online on the SSL mode:
>
> > Selects an SSL/TLS protocol version. Possible values are 'AUTO', 'SSL3',
> > and 'TLS1'. AUTO lets fetchmail autonegotiate any supported version
> > except SSLv2 (Fetchmail, since v7.0.0, prohibits negotiation of SSLv2 --
> > it has been deprecated for 15 years and is insecure). 'SSL3' and 'TLS1'
> > explicitly select SSL v3 or TLS v1.0, respectively. Note that OpenSSL, as
> > of version 1.0.X, only supports TLS v1.0, but not v1.1 or newer.
>
> Also - be warned that this list will be going away any day now due to
> changes at Berlios.
>
> --
>                  Please keep list traffic on the list.
>
> Rob MacGregor
>       Whoever fights monsters should see to it that in the process he
>         doesn't become a monster.                  Friedrich Nietzsche
>

Re: [fetchmail-users] Fetchmail

[Rob M. <rob...@gm...>]

On Fri, May 2, 2014 at 2:36 PM, jader fabiano <jad...@gm...> wrote:
> Hello!
> I am developing a solution that it use fetchmail, and I have a doubt.
> How can I specify to fetchmail uses tls1.1 or tls1.2?
>
> I did not find how i can do this.

Quoting the man page online on the SSL mode:

> Selects an SSL/TLS protocol version. Possible values are ’AUTO’, ’SSL3’,
> and ’TLS1’. AUTO lets fetchmail autonegotiate any supported version
> except SSLv2 (Fetchmail, since v7.0.0, prohibits negotiation of SSLv2 --
> it has been deprecated for 15 years and is insecure). ’SSL3’ and ’TLS1’
> explicitly select SSL v3 or TLS v1.0, respectively. Note that OpenSSL, as
> of version 1.0.X, only supports TLS v1.0, but not v1.1 or newer.

Also - be warned that this list will be going away any day now due to
changes at Berlios.

-- 
                 Please keep list traffic on the list.

Rob MacGregor
      Whoever fights monsters should see to it that in the process he
        doesn't become a monster.                  Friedrich Nietzsche

Re: [fetchmail-users] Fetchmail

[Heinz D. <ht...@fa...>]

On 02.05.2014, jader fabiano wrote: 

> I am developing a solution that it use fetchmail, and I have a doubt.
> How can I specify to fetchmail uses tls1.1 or tls1.2?

Interesting question. In my case, specifying "--sslproto TLSv1"
results in tlsv1 being used, as expected, although the server offers
tlsv1.2. With "SSL3", however, wireshark shows med that I have a
tlsv1.2 connection..



  

[fetchmail-users] Fetchmail

[jader f. <jad...@gm...>]

Hello!
I am developing a solution that it use fetchmail, and I have a doubt.
How can I specify to fetchmail uses tls1.1 or tls1.2?

I did not find how i can do this.

Thanks.

[fetchmail-users] Mailing list service for fetchmail project.

[Matthias A. <mat...@gm...>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Dear fetchmail mailing list subscribers,

BerliOS is shutting down end of this month, and their mailing list
export is broken, so I may not be able to obtain subscriber rosters in a
timely manner.

I will move downloads to sourceforge.net, but I have not yet decided if
I want to move the mailing lists there because their list archive
interface is awkward to use and inconcise.

If the move of the list goes well, I will follow up with a new
announcement message in a few days.

If such an action does not happen, please check the fetchmail website at
http://www.fetchmail.info/ or http://fetchmail.sourceforge.net/ for
updated mailing list instructions in May 2014.  You may have to
resubscribe in the future.

Sorry for the inconvenience - if any.

Best regards
Matthias
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)

iEYEARECAAYFAlNgLlcACgkQvmGDOQUufZUgUgCeLTz8ey8Opjx0pLQzxiWhJ/4l
EuUAn0mEcjkcwno4uvTtoR8vMatB/MEN
=FWME
-----END PGP SIGNATURE-----

Re: [fetchmail-users] Secure SMTP support?

[Grant E. <gra...@gm...>]

On 2014-04-09, grarpamp <gra...@gm...> wrote:
> On Wed, Apr 9, 2014 at 4:48 PM, Grant Edwards <gra...@gm...> wrote:
>
>> I wrote my own IMAP/ssl -> SMTP/ssl fetch-and-forward program.
>>
>> It doesn't have all the options and features that fetchmail does, but
>> it does everything I need it to do.  If, for some reason, it doesn't
>> work out and I decide I need fetchmail again, I'll be back...  ;)
>
> I think what is being desired could also be done by dumping messages
> into msmtp.

Yup, msmtp works great -- and I already had it installed and
configured, since that's what I use with mutt.  I don't know why I
didn't think of using it instead of fixating on SSL support for SMTP.
I think I'll retire my home-made program (I hadn't fully "daemonized"
it yet).

Of course it took 10-15 tries to figure out the config file syntax. :)

fetchmail kept complaining about "no mail servers have been
specified", but I think in the end the main problem was I was running
it as root.

Thanks for the suggestions.

-- 
Grant

Re: [fetchmail-users] Secure SMTP support?

[Peter P. <ro...@ri...>]

On Wed, Apr 09, 2014 at 06:04:25PM -0400, grarpamp wrote:
> On Wed, Apr 9, 2014 at 4:48 PM, Grant Edwards <gra...@gm...> wrote:
> > I wrote my own IMAP/ssl -> SMTP/ssl fetch-and-forward program.
> >
> > It doesn't have all the options and features that fetchmail does, but
> > it does everything I need it to do.  If, for some reason, it doesn't
> > work out and I decide I need fetchmail again, I'll be back...  ;)
> 
> I think what is being desired could also be done by dumping
> messages into msmtp.
> Of esmtp vs msmtp, msmtp has the best TLS support, IPv6, etc.
> Similar to fdm/getmail vs fetchmail in both those regards.
> Thought there was a third comparable smtp tool like msmtp out
> there but I have forgot it.

Well, in theory there is nullmailer, but in practice there's dma
(the DragonFly Mail Agent).

G'luck,
Peter

-- 
Peter Pentchev	ro...@ri... ro...@Fr... p.p...@st...
PGP key:	http://people.FreeBSD.org/~roam/roam.key.asc
Key fingerprint 2EE7 A7A5 17FC 124C F115  C354 651E EFB0 2527 DF13
Hey, out there - is it *you* reading me, or is it someone else?

Re: [fetchmail-users] Secure SMTP support?

[grarpamp <gra...@gm...>]

On Wed, Apr 9, 2014 at 4:48 PM, Grant Edwards <gra...@gm...> wrote:
> I wrote my own IMAP/ssl -> SMTP/ssl fetch-and-forward program.
>
> It doesn't have all the options and features that fetchmail does, but
> it does everything I need it to do.  If, for some reason, it doesn't
> work out and I decide I need fetchmail again, I'll be back...  ;)

I think what is being desired could also be done by dumping
messages into msmtp.
Of esmtp vs msmtp, msmtp has the best TLS support, IPv6, etc.
Similar to fdm/getmail vs fetchmail in both those regards.
Thought there was a third comparable smtp tool like msmtp out
there but I have forgot it.

Re: [fetchmail-users] Secure SMTP support?

[Grant E. <gra...@gm...>]

On Wed, Apr 09, 2014 at 10:36:52AM -0500, Grant Edwards wrote:
> On 2014-04-09, Matthias Andree <mat...@gm...> wrote:

> > If you were to provide a clean patch for wrapped SSL or STARTTLS for
> > (E)SMTP, against the Git master branch, I would definitely look at
> > it.
> 
> Thanks, I would be interested in working on that.

Never mind.

I wrote my own IMAP/ssl -> SMTP/ssl fetch-and-forward program.

It doesn't have all the options and features that fetchmail does, but
it does everything I need it to do.  If, for some reason, it doesn't
work out and I decide I need fetchmail again, I'll be back...  ;)

-- 
Grant

Re: [fetchmail-users] Secure SMTP support?

[Grant E. <gra...@gm...>]

On 2014-04-09, Matthias Andree <mat...@gm...> wrote:
> Am 04.04.2014 18:53, schrieb Grant Edwards:
>
>> In my googling, I didn't find anybody who wanted STARTTLS support,
>> just standard pop3s.  If one were to submit a patch adding support
>> for pop3s, would it be accepted?  [I've learned the hard way to ask
>> before starting work on new features for open-source projects.]
>
> Grant,
>
> For POP3, StartTLS (STLS) is already in place, albeit with an awkward
> unintuitive configuration, because fetchmail 6.x lumps SSL protocol
> selection together with wrapped vs. STARTTLS mode.

Sorry, I started out talking about SMTP and switched to POP3 without
explanation.  I found people asking about POP3 (which as you point out
is already handled) and wrapped SMTP but not STARTTLS.  I somehow
managed to mangle my posting and started typing pop instead of smtp.

> If you were to provide a clean patch for wrapped SSL or STARTTLS for
> (E)SMTP, against the Git master branch, I would definitely look at
> it.

Thanks, I would be interested in working on that.

> We would need to discuss how to select modes and protocols, though.

I have no opinion or preference, so if you would like to suggest
something, that would be great.

> I would rather not add to the proliferation of command line/rcfile
> options if it can be helped.

:)

I've always found fetchmail's configuration syntax confusing, and
every time I set up fetchmail I do it mostly by trail-and-error.  At
first I thought it was just me, then when ESR decided he needed to
write a GUI config file editor I realized it wasn't just me...

> I will not add features to the legacy_63 branch.

No problem.

--
Grant

Re: [fetchmail-users] Secure SMTP support?

[Matthias A. <mat...@gm...>]

Am 04.04.2014 18:53, schrieb Grant Edwards:

> In my googling, I didn't find anybody who wanted STARTTLS support,
> just standard pop3s.  If one were to submit a patch adding support for
> pop3s, would it be accepted?  [I've learned the hard way to ask before
> starting work on new features for open-source projects.]

Grant,

For POP3, StartTLS (STLS) is already in place, albeit with an awkward
unintuitive configuration, because fetchmail 6.x lumps SSL protocol
selection together with wrapped vs. STARTTLS mode.

If you were to provide a clean patch for wrapped SSL or STARTTLS for
(E)SMTP, against the Git master branch, I would definitely look at it.
We would need to discuss how to select modes and protocols, though.  I
would rather not add to the proliferation of command line/rcfile options
if it can be helped.

I will not add features to the legacy_63 branch.

Cheers,
Matthias

Re: [fetchmail-users] Secure SMTP support?

[Grant E. <gra...@gm...>]

On 2014-04-04, Matthias Andree <mat...@gm...> wrote:
> Am 03.04.2014 23:29, schrieb Grant Edwards:
>>
>> The last time I tried to set up fetchmail, it seemed to support
>> SSL-wrapped IMAP and POP3 but not SMTP.
>>
>> Is that still the case?
>>
>> Why support SSL-wrapped IMAP and POP but not SMTP?
>>
>> I would think the infrastructure required to support IMAP/POP over
>> SSL would work just as well for supporting SMTP over SSL.  In all
>> cases you're just connecting to a server using SSL and then running
>> the exact same protocol on top of the SSL connection -- right?
>
> This would require some more code, especially for STARTTLS support,
> that have not been written yet.  But you're right, the infrastructure
> is there.

In my googling, I didn't find anybody who wanted STARTTLS support,
just standard pop3s.  If one were to submit a patch adding support for
pop3s, would it be accepted?  [I've learned the hard way to ask before
starting work on new features for open-source projects.]

> The code has not yet been written because the assumption was that
> fetchmail would predominantly be used on the same computer as your
> SMTP server software, through "localhost" (which is the default), and
> it has been consequently assumed that that connection is trusted.

I'm currently using stunnel as a work-around, but it's rather tedious
having to set up a second service and make sure the two services start
up in the correct order.

-- 
Grant

Re: [fetchmail-users] Secure SMTP support?

[Grant E. <gra...@gm...>]

On 2014-04-03, J. Echter <j.e...@ec...> wrote:
> Am 03.04.2014 23:29, schrieb Grant Edwards:
>> The last time I tried to set up fetchmail, it seemed to support
>> SSL-wrapped IMAP and POP3 but not SMTP.
>>
>> Is that still the case?
>>
>> Why support SSL-wrapped IMAP and POP but not SMTP?
>>
>> I would think the infrastructure required to support IMAP/POP over
SSL
>> would work just as well for supporting SMTP over SSL.  In all cases
>> you're just connecting to a server using SSL and then running the
>> exact same protocol on top of the SSL connection -- right?
>>
> Hi Grant,
>
> why didn't you try it at first?

I did try it.  I couldn't figure out the correct options and after
some googling discovered it wasn't supported (I found a number of
other people trying to do the same thing).  Now that there's an
upcoming major release, I thought perhaps that issue had been
addressed.

-- 
Grant

Re: [fetchmail-users] Secure SMTP support?

[Matthias A. <mat...@gm...>]

Am 03.04.2014 23:29, schrieb Grant Edwards:
> 
> The last time I tried to set up fetchmail, it seemed to support
> SSL-wrapped IMAP and POP3 but not SMTP.
> 
> Is that still the case?
> 
> Why support SSL-wrapped IMAP and POP but not SMTP?
> 
> I would think the infrastructure required to support IMAP/POP over SSL
> would work just as well for supporting SMTP over SSL.  In all cases
> you're just connecting to a server using SSL and then running the
> exact same protocol on top of the SSL connection -- right?

This would require some more code, especially for STARTTLS support, that
have not been written yet.  But you're right, the infrastructure is there.

The code has not yet been written because the assumption was that
fetchmail would predominantly be used on the same computer as your SMTP
server software, through "localhost" (which is the default), and it has
been consequently assumed that that connection is trusted.

Re: [fetchmail-users] Secure SMTP support?

[J. E. <j.e...@ec...>]

Am 03.04.2014 23:29, schrieb Grant Edwards:
> The last time I tried to set up fetchmail, it seemed to support
> SSL-wrapped IMAP and POP3 but not SMTP.
>
> Is that still the case?
>
> Why support SSL-wrapped IMAP and POP but not SMTP?
>
> I would think the infrastructure required to support IMAP/POP over SSL
> would work just as well for supporting SMTP over SSL.  In all cases
> you're just connecting to a server using SSL and then running the
> exact same protocol on top of the SSL connection -- right?
>
Hi Grant,

why didn't you try it at first?

Cheers

Juergen

[fetchmail-users] Secure SMTP support?

[Grant E. <gra...@gm...>]

The last time I tried to set up fetchmail, it seemed to support
SSL-wrapped IMAP and POP3 but not SMTP.

Is that still the case?

Why support SSL-wrapped IMAP and POP but not SMTP?

I would think the infrastructure required to support IMAP/POP over SSL
would work just as well for supporting SMTP over SSL.  In all cases
you're just connecting to a server using SSL and then running the
exact same protocol on top of the SSL connection -- right?

-- 
Grant

Re: [fetchmail-users] Mail received via IMAP4: Subject line is mangled if not in ASCII

[grarpamp <gra...@gm...>]

> And I am now wondering if I should kill the mimedecode option in the
> next (future) fetchmail major release.  It requires tons of code for a
> half-baked non-solution that used to work around MIME unawareness in
> mail clients some dozen years ago.

The default is off which nicely follows the principle of just passing
mail through unaltered towards the final destination/processor.
I don't use it or pass8bits. Others would be better suited to speak
on removal.

>> This is working for spam, at least. Have to wait for some non-spam to
>> see if it still works.

I sent a test note out...

Subject: =?ISO-8859-1?B?SWYgeW91IGNhbiByZWFkIHRoaXMgeW8=?=
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: base64
ZXhjdXNlIHRoZSB0ZXN0DQrQv9GA0LjQstGW0YINCg==

[fetchmail-users] If you can read this yo

[grarpamp <gra...@gm...>]

excuse the test
привіт

Re: [fetchmail-users] Mail received via IMAP4: Subject line is mangled if not in ASCII

[Matthias A. <mat...@gm...>]

Am 17.03.2014 19:21, schrieb jdebert:
> On Mon, 17 Mar 2014 10:07:49 +0200
> ro...@ri... wrote:
>>
>> To the original poster: I don't really have a straight-up solution to
>> your problem, but you might try playing with the "mimedecode" and
>> "pass8bits" options in your fetchmail configuration file.  Both of
>> them should be unset by default, and this should be fine for most
>> cases; if you have explicitly set any of them, try unsetting it, see
>> if that helps.  Otherwise, try setting them in some combination to
>> see what happens.
>>
> 
> I had pass8bits and mimedecode set because they solved this problem
> before. Now having unset them has once again seems to have solved the
> problem.

Manually decoding the header you showed in your first post renders as

| Re: [opensuse-ja] Libreoffice write 描画問題

here, which Babelfish translates to "Libreoffice write drawing problem".


> Go figure. (^_^)

Depends on where you're sending to and what your clients make of what
they get from your spool or mail server.

Quoting the fetchmail manual:

|        [...]                  The mimedecode option is off by default,
because
|        doing RFC2047 conversion on headers throws away character-set
informa‐
|        tion and can lead to bad results if the encoding of the headers
differs
|        from the body encoding.

There should be a way to declare the destination character set, but isn't.

And I am now wondering if I should kill the mimedecode option in the
next (future) fetchmail major release.  It requires tons of code for a
half-baked non-solution that used to work around MIME unawareness in
mail clients some dozen years ago.

> This is working for spam, at least. Have to wait for some non-spam to
> see if it still works.

Re: [fetchmail-users] Mail received via IMAP4: Subject line is mangled if not in ASCII

[jdebert <jd...@ga...>]

On Mon, 17 Mar 2014 10:07:49 +0200
ro...@ri... wrote:
> 
> To the original poster: I don't really have a straight-up solution to
> your problem, but you might try playing with the "mimedecode" and
> "pass8bits" options in your fetchmail configuration file.  Both of
> them should be unset by default, and this should be fine for most
> cases; if you have explicitly set any of them, try unsetting it, see
> if that helps.  Otherwise, try setting them in some combination to
> see what happens.
> 

I had pass8bits and mimedecode set because they solved this problem
before. Now having unset them has once again seems to have solved the
problem.

Go figure. (^_^)

This is working for spam, at least. Have to wait for some non-spam to
see if it still works.

Thanks!

jd

Re: [fetchmail-users] Mail received via IMAP4: Subject line is mangled if not in ASCII

[grarpamp <gra...@gm...>]

> Er, no, it wasn't garbage, it was a MIME-encoded Subject field; this is

I meant their appearance as pasted into the body of the op's msg,
and should have known the context you mentioned.

Re: [fetchmail-users] Mail received via IMAP4: Subject line is mangled if not in ASCII

[<ro...@ri...>]

On Mon, Mar 17, 2014 at 01:49:47AM -0400, grarpamp wrote:
> > I'm trying to track down what's causing mail received via IMAP4 using
> > fetchmail have mangled Subject lines when the Subject is not ASCII.
> 
> You may have switched the above description around as
> 
> > This appears in the ISP mailbox:
> > ISO-2022-JP
> 
> this was garbage to me and

Er, no, it wasn't garbage, it was a MIME-encoded Subject field; this is
the way it should be transferred, this is the way it should be received
in the end-user's mailbox.  It is the job of the end-user's MUA to
decode it before *displaying* it to the user.

To the original poster: I don't really have a straight-up solution to
your problem, but you might try playing with the "mimedecode" and
"pass8bits" options in your fetchmail configuration file.  Both of them
should be unset by default, and this should be fine for most cases; if
you have explicitly set any of them, try unsetting it, see if that
helps.  Otherwise, try setting them in some combination to see what
happens.

G'luck,
Peter

-- 
Peter Pentchev	ro...@ri... ro...@Fr... p.p...@st...
PGP key:	http://people.FreeBSD.org/~roam/roam.key.asc
Key fingerprint 2EE7 A7A5 17FC 124C F115  C354 651E EFB0 2527 DF13
Do you think anybody has ever had *precisely this thought* before?

Re: [fetchmail-users] Mail received via IMAP4: Subject line is mangled if not in ASCII

[grarpamp <gra...@gm...>]

> I'm trying to track down what's causing mail received via IMAP4 using
> fetchmail have mangled Subject lines when the Subject is not ASCII.

You may have switched the above description around as

> This appears in the ISP mailbox:
> ISO-2022-JP

this was garbage to me and

> and it is received locally like this:

this was rendered ok.

> Is it the IMAP protocol doing the mangling?

The protocol spec is binary and not involved.
If your locale is US and you prefer to see rendered chars
instead of various codings and escapes, you might try setting
your viewing environment to LANG=en_us.UTF-8 .
Also, update and recompile old systems/libraries/apps
because some are still evolving language support.