9front - general discussion about 9front
 help / color / mirror / Atom feed
From: chris@chrisfroeschl.de
To: 9front@9front.org
Subject: Re: [9front] Mail server setup
Date: Mon, 08 Aug 2022 12:26:42 +0200	[thread overview]
Message-ID: <E4DB5286B726F6CF22A2C40991F8A1E7@chrisfroeschl.de> (raw)
In-Reply-To: <5DB133F4076ADA8FFA563E41DA7707C1@thinktankworkspaces.com>

Got a subdomain for testing now, but the error remains:

; upas/fs -f /imaps/test.chrisfroeschl.de/chris

!Adding key: proto=cram server=test.chrisfroeschl.de user=chris
password: 
!
upas/fs: imap: unexpected line: y2hyaxmgndq4ntu2mze4zthhmznlmtjhmjhiymu4nmu3mwqxmdu= bad no command: bad syntax

> chmod 600 for the key sorry

I created a new TLS cert several times to avoid an error there.

These were my last creation steps: (from the FQA)

; ramfs -p
; cd /tmp
; auth/rsagen -t 'service=tls role=client owner=*' >key
; chmod 600 key
; cp key /sys/lib/tls/key
; auth/rsa2x509 'C=DE CN=test.chrisfroeschl.de' /sys/lib/tls/key | auth/pemencode CERTIFICATE >/sys/lib/tls/cert

Permission should suffice therefore.

I really can't see what I'm doing wrong by now.  Perhaps some ndb
stuff that is required but not mentioned?  Some special user settings?
etc.

Will investigate further while testing smtp as soon as I get the chance.

chris

  reply	other threads:[~2022-08-08 10:28 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-06 13:17 chris
2022-08-06 19:46 ` william
2022-08-06 19:47 ` william
2022-08-08 10:26   ` chris [this message]
2022-08-09  8:21     ` william
2022-08-09 18:09       ` chris
2022-08-11 12:37         ` chris
2022-08-11 14:29           ` Stanley Lieber
2022-08-11 21:17             ` chris
2022-08-12  6:23               ` william
2022-08-12 13:47                 ` Stanley Lieber
2022-08-12  6:33               ` sirjofri
2022-08-12  7:10                 ` sirjofri
2022-08-12 15:27                   ` chris
2022-08-12 18:49                     ` sirjofri
2022-08-12 20:53                       ` chris
2022-08-12 22:25                     ` ori
2022-08-13  9:56                       ` Steve Simon
2022-08-07  0:56 ` sl

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=E4DB5286B726F6CF22A2C40991F8A1E7@chrisfroeschl.de \
    --to=chris@chrisfroeschl.de \
    --cc=9front@9front.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).