From: "Steven Stallion" <sstallion@gmail.com>
To: 9fans@9fans.net
Subject: Re: [9fans] /mail/lib/rewrite and net!$smtp
Date: Sat, 7 Dec 2019 20:25:29 -0600 [thread overview]
Message-ID: <0f981bb579b8e2f6b7622ddd3da01153@philo.quuxotic.net> (raw)
> Thanks! Unfortunately my MX host only exposes port 587 for relaying
> mail outside of the domain. I suppose I could update cs to permit
> specifying a port number in ndb for $smtp, but I'm not sure that's any
> better than just specifying the relay host directly in rewrite.
I did some more poking around this evening and I think I've found a
slightly better approach. Rather than try to embed the service string
in the smtp= entry in ndb, I appended it to the upas/smtp call in
/mail/lib/remotemail. It's not as clean as I would like, but hey, at
least I'm a member of the net!$smtp club now.
Cheers,
Steve
next reply other threads:[~2019-12-08 2:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-08 2:25 Steven Stallion [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-12-07 0:54 Alex Musolino
2019-12-07 1:13 ` kvik
2019-12-07 0:13 Steven Stallion
2019-12-07 21:10 ` [9fans] " Richard Miller
2019-12-07 21:46 ` Steven Stallion
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=0f981bb579b8e2f6b7622ddd3da01153@philo.quuxotic.net \
--to=sstallion@gmail.com \
--cc=9fans@9fans.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).