1 |
On 2018-01-19, Grant Taylor <gtaylor@××××××××××××××.net> wrote: |
2 |
|
3 |
> I haven't done enough with the above (alternate) MTAs to be able to |
4 |
> speak to them. But my understanding is that they come with a |
5 |
> /path/to/sendmail wrapper script (or binary) that emulates part of |
6 |
> what the sendmail binary did. At least the portions there of that |
7 |
> clients use to submit email the way that you're talking. |
8 |
|
9 |
I have a /usr/bin/sendmail emulator that transfers mail to an MTA that |
10 |
will then worry about delivery. I need an SMTP server that will relay |
11 |
incoming mail by using that existing command-line utility. |
12 |
|
13 |
>> I'm currently using something I wrote in Python, but the SSL |
14 |
>> support in the 3rd party SMTP module is broken and I don't relish |
15 |
>> trying to fix it. |
16 |
> |
17 |
> Do you actually need a local MTA (daemon)? Or do you just need |
18 |
> something smart enough to accept messages from standard in and pass |
19 |
> them out via a smart host? |
20 |
|
21 |
I need something that accepts mail via SMTP (with SSL and AUTH |
22 |
support), and then relays each received message by invoking a command |
23 |
line utilty that has the same API as /usr/bin/sendmail. |
24 |
|
25 |
There is no local delivery and no acceptance of mail other than via |
26 |
SMTP. |
27 |
|
28 |
I would very much prefer that there is no queueing: the smtp server |
29 |
should not acknowlege acceptance of the message until the smtp server |
30 |
has invoked /usr/bin/sendmail and it has returned success. |
31 |
|
32 |
-- |
33 |
Grant Edwards grant.b.edwards Yow! I've read SEVEN |
34 |
at MILLION books!! |
35 |
gmail.com |