Ok. It is related to name resolution, but it is over my head. :-D
It’s querying the mx record; then the a record for the mail server. But this is
where it gets odd (at least for someone ignorant like me). Then the query
prepends the mail server (mail.mailroute.net) to the hostname of the address
Ok. So apparently, I had not tested this specific case on either of my
machines. I spun up a fresh 9.2 virtual machine, and installed opensmtpd-devel.
This is with a different host, so odd routing issues should not be the root
cause. The MX lookup was wrong again. It pointed to the 209.141.37.64
Hi Gilles,
Thanks for the response. I figured that y’all more need more info, but I was
sick in bed and hoping there might have been a known issue. Once again, I’m bet
it’s something on my side, but I wanted to be sure. I’m testing this on a KVM
VM before I roll it on our production mail server
On Mon, Dec 23, 2013 at 03:36:37AM -0500, John Grasty wrote:
> Hi,
>
Hi,
> I love opensmtpd.
>
So do I ;-)
> I?m sure this error is my fault, but I can figure it out for the life of me.
> On a backup server, I have opensmtpd 5.4.1 with the sample config file
> listening on the localhost a
Sorry for the delay, been caught in stuff
On Sat, Dec 14, 2013 at 05:52:44PM +, John Cox wrote:
> I tried to use this:
>
> smarthost = "smarthost.example.net"
>
> from any relay via tls://$smarthost
>
We don't perform macro expansion within strings, I don't know if we
should, it would
Hi,
I love opensmtpd. I’m sure this error is my fault, but I can figure it out for
the life of me. On a backup server, I have opensmtpd 5.4.1 with the sample
config file listening on the localhost and relaying only local mail. This
server’s hostname is subdomain.example.com. When I try to send