Re: [Nmh-workers] mts.conf that works with fastmail?

[Thomas Levine]

I have now gotten inc working with FastMail POP. Here is a simplified
version of the command.

  inc -user address@hidden -host pops-proxy.fastmail.com \
    -proxy 'openssl s_client -quiet -connect pops-proxy.fastmail.com:443' \
    -nosasl

And here is the one that I really am using.

  inc -user address@hidden -host pops-proxy.fastmail.com \
    -proxy 'openssl s_client -quiet -connect pops-proxy.fastmail.com:443' \
    -nochangecur -nosasl +pop

I wrote a Seive rule in FastMail to copy all mail to the INBOX.Download
folder, and then I inc from that folder. This way, a copy of each
message stays on the server after I delete it.

Thomas Levine writes:
> I know next to nothing about SSL and TLS, so this discussion is
> interesting.
> 
> Ken Hornstein writes:
> > It would be nice to know why inc didn't work, if it was a lack of capability
> > or some other problem.  If the issue is that they use IMAP and not POP,
> > then that's something we don't support yet.  But if your server supports
> > POP, hopefully we should be able to make use of it.
> 
> I think my issue was in configuring the encrypted connection.
> I configured the sending after I configured the receiving, and
> I no longer cared to touch the receiving part by the time
> I figured out how to use the encrypted connection for sending.
> 
> My host supports POP, but I used IMAP for the move_on_delete
> capability. If I were using POP, I would use a different approach
> to accomplish the same thing.