> I haven't seen this particular redraw artifact, but I've seen other
> smaller ones. Is there anything in particular that you can do to
> reproduce it?
It turns out that there is:
1 acme -f $font /acme/mail/guide; guide opens at top of right column
2 left-click on Mail; mbox list opens in right
> On the tangential subject of acme mail, I have a very infrequent bug
> where the header of a newly arrived message pops up in the position
> where the /mail/fs/mbox window used to be, some time after the mbox
> window has been adjusted by another window opening. Does anyone else
> see this? Is
o...@eigenstate.org once said:
> Unrelatedly, would there be interest in adding the `$split{cmd} syntax
> from 9atom to 9legacy? I think it's currently the only reason that
> git9 doesn't work out of the box there, and it's very nice syntax.
I'm not a fan of the `word{...} syntax. It's odd to
On the tangential subject of acme mail, I have a very infrequent bug
where the header of a newly arrived message pops up in the position
where the /mail/fs/mbox window used to be, some time after the mbox
window has been adjusted by another window opening. Does anyone else
see this? Is there a
> Looks like that was it - thanks a lot David! IMAP is syncing as we
> speak. It looks like I have my work cut out for me to get things
> updated to 9legacy's latest and greatest.
>
> Cheers,
> Steve
I've put some patches together that made acme Mail a bunch more usable
for me. Mostly around
Looks like that was it - thanks a lot David! IMAP is syncing as we
speak. It looks like I have my work cut out for me to get things
updated to 9legacy's latest and greatest.
Cheers,
Steve
On Thu, Nov 28, 2019 at 1:00 PM David du Colombier <0in...@gmail.com> wrote:
>
> If the server uses a X.509
If the server uses a X.509 certificate with a SHA256 signature,
you need SHA2 signature support in libsec.
http://9legacy.org/9legacy/patch/libsec-x509-sha2.diff
http://9legacy.org/9legacy/patch/libsec-x509-sig.diff
--
David du Colombier
--
9fans: 9fans
> unfortunately it doesn't look like anything is being logged
Turns out I misremembered where upas/fs logs the failure:
; upas/fs -f /imaps/imap.gmail.com/$gmail
upas/fs: opening /imaps/imap.gmail.com/$gmail: imap.gmail.com/imaps:cert for
imap.gmail.com not recognized:
Thanks - unfortunately it doesn't look like anything is being logged.
Interestingly enough, it looks like mail has been broken for quite a
while, this was the last log message recorded (the fileserver went
into storage in mid 2018):
gunge Aug 26 05:25:04 delivered stallion From stallion Wed Aug
Check /sys/log/mail for a fingerprint.
--
9fans: 9fans
Permalink:
https://9fans.topicbox.com/groups/9fans/Te20476748ab5e4ba-M519efe14ca0b3cb7c3836dee
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription
Adding the fingerprint will work if you are lucky, once,
or maybe twice.
In my experience almost every new connection required
redoing the above -- which wasn't very fun so I ended
up forwarding gmail into a sub-mailbox under my control
and haven't looked back.
Working with their SMTP has the
Thanks guys. I suspect I'm about to regret my lack of time mucking
about with tls on plan9:
% upas/fs -f /imaps/imap.gmail.com/sstall...@gmail.com
upas/fs: opening /imaps/imap.gmail.com/sstall...@gmail.com:
imap.gmail.com/imaps:tlsClient: tls: local invalid x509/rsa
certificate
% cat
The TLS implementation on Plan 9 doesn't verify X.509 certificate chain,
so the certificate bundle isn't useful. It's only used by Go programs.
However, you need to add the server certificate fingerprint to
/sys/lib/tls/mail,
as Steve Simon said.
--
David du Colombier
hi,
i receive mail on plan9 so i dont use gmail.
you sure you didn't forget to install a new x509 thumbprint in
/sys/lib/tls/mail?
-Steve
On 28 Nov 2019, at 3:40 pm, Steven Stallion wrote:
>
> All,
>
> Is anyone still fetching Gmail these days? After bringing my old
> fileserver back
14 matches
Mail list logo
