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