9front - general discussion about 9front
 help / color / mirror / Atom feed
From: william@thinktankworkspaces.com
To: 9front@9front.org
Subject: Re: [9front] Mail server setup
Date: Tue, 09 Aug 2022 01:21:51 -0700	[thread overview]
Message-ID: <F0F10F72A4F86A43EDF3B4EBE06DF0EF@thinktankworkspaces.com> (raw)
In-Reply-To: <E4DB5286B726F6CF22A2C40991F8A1E7@chrisfroeschl.de>

yea I don't know. Here is my ndb 

ipnet=thinktankworkspaces.com ip=45.79.94.0 ipmask=255.255.255.0
	ipgw=45.79.94.1
	dns=173.230.145.5
	authdom=maat
	auth=maat
	dnsdom=think
	cpu=maat
	fs=maat
	smtp=thinktankworkspaces.com
	mail=thinktankworkspaces.com
	#smtp=45.79.94.76
	#mail=45.79.94.76

before I moved the domain I did everything with IP address. But relay issues DKIM issues popped up from
time to time. But final version is with fully qualified domain

I did do some other mangling but abandoned it because I'm letting gandi handle dns. Its just easier

but I had this earlier on before I commented it all out. 

#dom=thinktankworkspaces.com
#	ns=ns1.thinktankworkspaces.com
#	ns=ns2.thinktankworkspaces.com
#	mx=maat.thinktankworkspaces.com pref=1
#	mail=maat.thinktankworkspaces.com

do you have a new line after the command exec tlssrv in /rc/bin/service/tcp993
Some of these scripts break because you must have a blank line at the very end. I forget the rules.


Quoth chris@chrisfroeschl.de:
> 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-09  8:23 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
2022-08-09  8:21     ` william [this message]
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=F0F10F72A4F86A43EDF3B4EBE06DF0EF@thinktankworkspaces.com \
    --to=william@thinktankworkspaces.com \
    --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).