| 1 |
On 19/01/2018 21:54, Grant Edwards wrote: |
| 2 |
> On 2018-01-19, Ian Zimmerman <itz@××××××××××××.org> wrote: |
| 3 |
>> On 2018-01-19 18:49, Grant Edwards wrote: |
| 4 |
>> |
| 5 |
>>>> Just like the others writing in this thread, I am wondering why you |
| 6 |
>>>> need 2 pieces here. Why won't e.g. exim do both sides of this for |
| 7 |
>>>> you? It certainly has all the functionality. |
| 8 |
>>> |
| 9 |
>>> I don't see how you can say that when you don't know the method that |
| 10 |
>>> my command-line MTA uses to transfer mail on down the path towards |
| 11 |
>>> delivery. |
| 12 |
>> |
| 13 |
>> I can say it because I have some experience with exim, and I know it can |
| 14 |
>> do pretty much anything. If its configuration language isn't Turing |
| 15 |
>> complete, it is quite damn close to it. And the same can be said of |
| 16 |
>> sendmail, though I know much less about it know. |
| 17 |
> |
| 18 |
> Can exim transfer mail to an Exchange server that doesn't expose an |
| 19 |
> SMTP server? |
| 20 |
> |
| 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 |
|
| 28 |
|
| 29 |
-- |
| 30 |
Alan McKinnon |
| 31 |
alan.mckinnon@×××××.com |
Archives