Adding new phlog about openSMTPD - gopherhole - My website source code.
 (DIR) Log
 (DIR) Files
 (DIR) Refs
       ---
 (DIR) commit 69749558318b3f12e6188c2386266529bac171cb
 (DIR) parent ed547ff3bcb7b4cda9a4b027373d8db20d818b2d
 (HTM) Author: Jay Scott <me@jay.scot>
       Date:   Sun,  5 Feb 2023 16:16:34 +0000
       
       Adding new phlog about openSMTPD
       
       Diffstat:
         M index.gph                           |       1 +
         M phlog/013.txt                       |       2 +-
         A phlog/014.txt                       |      44 +++++++++++++++++++++++++++++++
       
       3 files changed, 46 insertions(+), 1 deletion(-)
       ---
 (DIR) diff --git a/index.gph b/index.gph
       @@ -10,6 +10,7 @@
        
        PHLOG
        
       +[0|2023-02-05 ... Re-Evaluating my local mail setup with OpenSMTPD|phlog/014.txt|server|port]
        [0|2023-02-03 ... Finally, I switched over to OpenBSD|phlog/013.txt|server|port]
        [0|2023-01-29 ... Automating my infra deployment and configuration|phlog/012.txt|server|port]
        [0|2023-01-14 ... Reducing my footprint, using a mini-pc|phlog/011.txt|server|port]
 (DIR) diff --git a/phlog/013.txt b/phlog/013.txt
       @@ -34,7 +34,7 @@ shell, again, nothing really needed to change.
        I really like the package management, for Alpine Linux I had my own
        bootstrap script [2] to get me up and running. On OpenBSD I am nearly
        done right off the bat with just one command, a list of user packages
       -really to install. On Linux I feel that this would be including a heap
       +ready to install. On Linux I feel that this would be including a heap
        of system libraries and dependencies.
        
        
 (DIR) diff --git a/phlog/014.txt b/phlog/014.txt
       @@ -0,0 +1,44 @@
       +[jay.scot]
       +[014]
       +
       +
       +--[ Re-Evaluating my local mail setup with OpenSMTPD
       +
       +
       +This one is not limited to OpenBSD, but something I came across and
       +implemented after reading about daily(8) and security(8). These scripts
       +perform a variety of system tasks daily, weekly, and monthly. The report
       +produced by these tasks is sent to the local user, which prompted me to
       +re-evaluate my current email situation.
       +
       +
       +Previously, any mail I generated was sent via an external SMTP relay
       +configured directly in mutt. This also included my git configuration
       +file, which had an external SMTP relay set up for sending patches using
       +git-send-email. When sending mail via shell scripts, I would do this by
       +invoking mutt in the following manner.
       +
       +        echo "the body" | mutt -s 'the title' -- me@domain.com
       +
       +
       +Outside of the initial local user mail delivery issue, it worked, but
       +came with overhead. If there were connectivity issues with the SMTP
       +relay, things would hang or break. Mail would not be queued unless it
       +was handled by the application or script. I would get a 1-2 second delay
       +when mutt connected to the relay, which was annoying for some scripts.
       +All mail that was meant for me, such as scripting results or
       +notifications, would go through a public round trip.
       +
       +    Then:
       +      script -> external smtp relay -> external imap fetch -> mutt (maildir)
       +
       +    Now:
       +      script -> local openSMTPD -> mutt (maildir)
       +
       +
       +And finally, after setting up OpenSMTPD locally I now get all system
       +mail directly to my Maildir and a mail queue system. I should have fixed
       +it ages ago, it's a nice quality of service change.
       +
       +
       +.EOF