Using VestaCP/Exim as a Smart Host
-
adamskalicky
- Posts: 1
- Joined: Tue Nov 24, 2015 10:51 pm
Using VestaCP/Exim as a Smart Host
Hi All,
I have been struggling with using exim as a "Smarthost" for my office 365 mail. For those of you not familiar with the concept, a smart host will basically route all mail that cannot be routed internally for accepted domains to another mail server.
A few details about the setup:
Domain in question: scencdn.com
Human users are on O365 - ex. [email protected]
Non-Human accounts are on Vesta - ex. [email protected]
All mail is routed to O365, then if the account is not a human user (basically if it does not exist on O365) it is sent to Vesta.
This setup works fine if external emails send to non-human accounts - ex [email protected] sends to [email protected].
The issue comes when a human user send to a non-hum account within the Org. for example [email protected] (O365) sends to [email protected] (Vesta). The routing is fine but Exim kicks back the message with the following error:
[email protected]
ny1.scencdn.com
Remote Server returned '550-Verification failed for <[email protected]> 550-Unrouteable address 550 Sender verify failed'
Original message headers:
Received: from BN3PR1101MB1123.namprd11.prod.outlook.com (10.165.75.137) by
BN3PR1101MB1122.namprd11.prod.outlook.com (10.165.75.136) with Microsoft SMTP
Server (TLS) id 15.1.331.20; Tue, 24 Nov 2015 22:27:35 +0000
Received: from BN3PR1101MB1123.namprd11.prod.outlook.com ([10.165.75.137]) by
BN3PR1101MB1123.namprd11.prod.outlook.com ([10.165.75.137]) with mapi id
15.01.0331.019; Tue, 24 Nov 2015 22:27:34 +0000
I suspect this is because the email [email protected] is not a part of Vesta and it thinks it is spam.
I already tried adding *.prod.outlook.com to the white-blocks.conf but nothing changed.
Any ideas?
I have been struggling with using exim as a "Smarthost" for my office 365 mail. For those of you not familiar with the concept, a smart host will basically route all mail that cannot be routed internally for accepted domains to another mail server.
A few details about the setup:
Domain in question: scencdn.com
Human users are on O365 - ex. [email protected]
Non-Human accounts are on Vesta - ex. [email protected]
All mail is routed to O365, then if the account is not a human user (basically if it does not exist on O365) it is sent to Vesta.
This setup works fine if external emails send to non-human accounts - ex [email protected] sends to [email protected].
The issue comes when a human user send to a non-hum account within the Org. for example [email protected] (O365) sends to [email protected] (Vesta). The routing is fine but Exim kicks back the message with the following error:
[email protected]
ny1.scencdn.com
Remote Server returned '550-Verification failed for <[email protected]> 550-Unrouteable address 550 Sender verify failed'
Original message headers:
Received: from BN3PR1101MB1123.namprd11.prod.outlook.com (10.165.75.137) by
BN3PR1101MB1122.namprd11.prod.outlook.com (10.165.75.136) with Microsoft SMTP
Server (TLS) id 15.1.331.20; Tue, 24 Nov 2015 22:27:35 +0000
Received: from BN3PR1101MB1123.namprd11.prod.outlook.com ([10.165.75.137]) by
BN3PR1101MB1123.namprd11.prod.outlook.com ([10.165.75.137]) with mapi id
15.01.0331.019; Tue, 24 Nov 2015 22:27:34 +0000
I suspect this is because the email [email protected] is not a part of Vesta and it thinks it is spam.
I already tried adding *.prod.outlook.com to the white-blocks.conf but nothing changed.
Any ideas?