Just set up a brand new ASUS desktop with 6.8, so as to replace my old mail
server,
which died after 15 years or so (but well backed up and have 20 odd years of
emails
saved on it). I have a few local users on it, and we are used to using good
old alpine.
The basic "Mail" client works fine, both sending and receiving, however, having
installed
the Alpine client, which seems to work fine for handling incoming mail, I was
surprised to find
that newly composed outgoing email, or replies to ones received cause Alpine to
hand endlessly,
I actually have to close the X-window to get out of it -- even so it is still
running so I
have to issue a kill -9 to stop it.
Feels to me that somehow there is a lock on some file that Alpine wants to use,
but I can't see
anything like mbox.lock or whatever. Whoops, above paragraph: s/hand/hang
Here's my /etc/main/smtp.conf
# This is the smtpd server system-wide configuration file.
# See smtpd.conf(5) for more information.
table aliases file:/etc/mail/aliases
listen on socket
# To accept external mail, replace with: listen on all
#
# listen on lo0
listen on all
action "local_mail" mbox alias <aliases>
action "outbound" relay
# Uncomment the following to accept external mail for domain "example.org"
#
# match from any for domain "example.org" action "local_mail"
match from any for domain "computershop.ca" action "local_mail"
match from any for domain "hook.org" action "local_mail"
match from any for domain "mrdoctors.ca" action "local_mail"
match from local for local action "local_mail"
match from local for any action "outbound"
------------------------------------------------------------------
Here's text from the hanging outgoing test message:
To : aus...@hook.org
Cc :
Attchmnt:
Subject : Re: test message from gmail to cs...@computershop.ca
----- Message Text -----
replying to test message below from cshop
On Thu, 21 Jan 2021, Austin Hook wrote:
> test message from gmail to cs...@computershop.ca
>
[Sending mail | <= This line incomplete says something like 0%
-------------------------------------------------------------------
Am behind our firewall so here's an extract of the rules:
emailports = "{ smtp, pop3, imap, imap3, imaps, pop3s }"
...
### Externally originated mail traffic redirected to our internal mailserver
match in on $ext_if proto tcp to $ext_if port $emailports rdr-to $emailserver
### Stop mail from Local net from IPs where no mail should come from
block in quick on $int_if proto tcp from { $hp $wlrouter $dynamic $accounting }
port $emailports
...
### Local net will need help accessing the mailserver ###
match in on $int_if inet proto tcp from $int_if:network to $ext_if \
port $emailports rdr-to $emailserver
match out on $int_if proto tcp from $int_if:network to $emailserver \
port $emailports nat-to $int_if
pass out on $ext_if from $localnet to any nat-to $ext_if
--------------------------------------------------------------
Getting pretty rusty here... set it up 10 years ago and it's taken me a week
of being down ,so far,
to deal with dozens of gotchas, like forgetting our last nameserver was down as
well, and the ns2 location
went away a year ago, and I should have covered that problem at the time.
Still have to set up our
web pages again. etc. etc.
I wonder if alpine used new mail ports I never heard of back then and probably
gave too much info here,
Except what really is needed. Here's a few basic questions perhaps some can
answer top of their head:
1) Anyone still running Alpine in this era of 6.8?
2) Any reason why the new pseudo-Sendmail wouldn't handle Apline as well as
the old one did?
In general, kudos, to the OpenBSD folks who bring so much basic functionality
into OpenBSD itself. I'll
be delighted if I can just use this simplified framework successfully.
3) Any further comments?
Austin
