I think the full config minus pki stuff would be useful. Till then look at tags. It may be useful.
listen on 587 auth ... tag authed accept tagged authed ... On Nov 28, 2018 5:32 PM, Thomas Smith <[email protected]> wrote: > > Hi, > > I’m running OpenSMTPd on OpenBSD 6.3. > > The server is used primarily as a mail filtering relay, filtering with spamd; > however, it’s also used, on a more limited bases, to send outbound emails. > > If I’m only relaying email for domain.com, relaying works fine. In this > context, an external user would send an email to [email protected], that email > would pass through this server first, then it would be delivered upstream. > > It’s this second context that causes issues… > > If user1 attempts to send an outbound email through this server—that is, > user1 is authenticating to this server for the sole purpose of sending an > email—and sends that email to [email protected], I end up with a mail loop > since the server itself is listed as the MX for domain.com. > > My question is this… > > It is possible to configure OpenSMTPd to detect this scenario and to know > that it should relay that email to domain.com rather than trying to deliver > it to its MX server, which happens to be the server itself? > > Here’s a very abridged version of my config, showing the relay and > authentication configurations: > > accept from any for domain <domain> relay via <server> # relay config > listen on egress port 587 tls-require auth <smtpout_auth> hostname > $smtp_domain pki $smtp_domain # outbound smtp auth config > > If the answer to my question is that this isn’t possible, can someone > recommend an alternative way of configuring OpenSMTPd to make it work? The > objective would be to provide both of these services on the same server, > instead of separate servers. > > Thank you, > > ~ Tom > > -- > You received this mail because you are subscribed to [email protected] > To unsubscribe, send a mail to: [email protected] >
