> Running the most recent amd64 snapshot on ESXi.
>
> OpenBSD r1.mwlucas.org 6.0 GENERIC#162 amd64
>
> I'm trying to use relayd's check send/expect support to verify a
> daemon's banner comes up. After problems I've stripped this down to
> the simplest possible config, a single known good mail server. The server
> keeps showing up as down, with a TCP timeout. Packet sniffer shows
> that the connection opens and that the SMTP banner is returned in less
> than a second.
>
> Am I doing something obviously stupid here?
>
> Here's the config and the debugging output.
>
> relayd.conf:
> ---
> ext_ip="203.0.113.213"
>
> log updates
> timeout 9000
>
>
> table <smtp> { 104.236.197.233 }
>
> redirect smtp {
> listen on $ext_ip port 587 interface em0
> forward to <smtp> check send nothing expect "200 *"
> }
>
> --
>
> Why have the "timeout 9000"? Well, because of the error I get:
>
> relayd -dvvvv
> pfe: filter init done
> startup
> socket_rlimit: max open files 1024
> socket_rlimit: max open files 1024
> socket_rlimit: max open files 1024
> socket_rlimit: max open files 1024
> relayd_tls_ticket_rekey: rekeying tickets
> init_tables: created 1 tables
> hce_notify_done: 104.236.197.233 (tcp read timeout)
> host 104.236.197.233, check send expect (9020ms,tcp read timeout), state
> unknown -> down, availability 0.00%
> pfe_dispatch_hce: state -1 for host 1 104.236.197.233
> ^Chce exiting, pid 12145
> kill_tables: deleted 1 tables
> flush_rulesets: flushed rules
> pfe exiting, pid 67580
> relay exiting, pid 72564
> ca exiting, pid 19097
> relay exiting, pid 72558
> relay exiting, pid 72790
> ca exiting, pid 1431
> ca exiting, pid 889
> parent terminating, pid 81783
>
> Any suggestions, folks?
Does the daemon actually return "200"? --
$ nc -vv localhost 25
Connection to localhost 25 port [tcp/smtp] succeeded!
220 elanoir.my.domain ESMTP OpenSMTPD
^C
-- Dale
