1 |
On 2018-01-19, Alan McKinnon <alan.mckinnon@×××××.com> wrote: |
2 |
> On 19/01/2018 21:54, Grant Edwards wrote: |
3 |
>> On 2018-01-19, Ian Zimmerman <itz@××××××××××××.org> wrote: |
4 |
>>> On 2018-01-19 18:49, Grant Edwards wrote: |
5 |
>>> |
6 |
>>>>> Just like the others writing in this thread, I am wondering why you |
7 |
>>>>> need 2 pieces here. Why won't e.g. exim do both sides of this for |
8 |
>>>>> you? It certainly has all the functionality. |
9 |
>>>> |
10 |
>>>> I don't see how you can say that when you don't know the method that |
11 |
>>>> my command-line MTA uses to transfer mail on down the path towards |
12 |
>>>> delivery. |
13 |
>>> |
14 |
>>> I can say it because I have some experience with exim, and I know it can |
15 |
>>> do pretty much anything. If its configuration language isn't Turing |
16 |
>>> complete, it is quite damn close to it. And the same can be said of |
17 |
>>> sendmail, though I know much less about it know. |
18 |
>> |
19 |
>> Can exim transfer mail to an Exchange server that doesn't expose an |
20 |
>> SMTP server? |
21 |
> |
22 |
> Errr, no. exim does SMTP. |
23 |
> |
24 |
> If the above is what you need, any orthodox mail server would need to |
25 |
> hand the mail over to something that *can* deliver to Exchange. |
26 |
|
27 |
Yes, and that something is my existing command-line MTA utility that |
28 |
has the same usage as /usr/bin/sendmail. |
29 |
|
30 |
-- |
31 |
Grant Edwards grant.b.edwards Yow! HELLO KITTY gang |
32 |
at terrorizes town, family |
33 |
gmail.com STICKERED to death! |