9front - general discussion about 9front
 help / color / mirror / Atom feed
From: thinktankworkspaces@gmail.com
To: 9front@9front.org
Subject: Re: [9front] upas email configuration
Date: Wed, 23 Feb 2022 21:09:40 -0800	[thread overview]
Message-ID: <EC936C53E05483A310FA78658D3E3F60@gmail.com> (raw)
In-Reply-To: <5037d738-823c-43fe-9f31-d43aa57588f4@sirjofri.de>

So I suspect mail was working fine. AWS was blocking 25 and 587. They kind of recommend 
paying for static address and to use SES. Which is wasteful and expensive over a long
period of time. SES only publishes to SNS or s3. I would have write extra stuff just to get
mail. 



Quoth sirjofri <sirjofri+ml-9front@sirjofri.de>:
> Hello you two,
> 
> I have a running mailserver on 9front using the 9front upas (which is 
> nupas). Most things are configured like mentioned in the FQA (section 7, 
> I guess?), but here are my notes. I hope it helps:
> 
> http://sirjofri.de/changeblog/1594881674/
> 
> I have another blog post about putting tagged mails into different 
> folders, which you can nicely see in action when you look at my mail 
> address: sirjofri+ml-9front, where the ml-9front part specifies the 
> folder for the mails sent to this address.
> 
> Mail server maintenance is horror and I wish you good luck. Also don't 
> forget you need a running cron for sending mail using runq.
> 
> sirjofri


  reply	other threads:[~2022-02-24  5:14 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-15  8:42 thinktankworkspaces
2022-02-15  9:55 ` qwx
2022-02-15 12:49   ` sirjofri
2022-02-24  5:09     ` thinktankworkspaces [this message]
2022-02-24 11:05       ` hiro
2022-02-26 20:43         ` thinktankworkspaces
2022-02-15 15:22 ` Stanley Lieber
2022-02-15 17:08   ` Steve Simon
2022-02-15 19:05   ` phil9
2022-02-15 23:50     ` thinktankworkspaces
2022-02-17  7:24     ` thinktankworkspaces
2022-02-17  7:27     ` thinktankworkspaces

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=EC936C53E05483A310FA78658D3E3F60@gmail.com \
    --to=thinktankworkspaces@gmail.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).