Drifting
Have followed both your instructions to the letter, and it seems that the email is still being routed out of the SME mailserver to the ISP smarthost.
Your requirement is a standard function of SME server so it should not be difficult to get it working.
I note you have NOT been forthcoming with answers to various questions so you make this procedure more difficult for us & yourself.
eg where is the mail server hosting archive.dc.local located, locally on a LAN or remotely ?
If local, is this IP actually accessible on the network from the SME server ie in the same IP range ?
Can you successfully ping archive.dc.local & the piler server LAN IP from the SME server command line ?
Please advise what this IP is 212.*.*.* so we can test it, is it local or remote, is it publicly accessible if remote ?
What underlying operating system software is this piler server running ?
I note also that your error response refers to dc.local rather than archive.dc.local
ie
"Hi. This is the qmail-send program at dc.local."
Can you explain why that is so ?
Is the piler server domain name dc.local or archive.dc.local ?
Before going further, you probably should undo or remove or delete previous changes made to your system trying to get this to work.
You are following 2 peoples advices so it can get confusing & things can clash.
Now my apologies, there is an error in my earlier advice.
Rather than adding archive.dc.local to the Hostnames & Addresses panel it should be added to the Domains panel in server manager
Please remove it from the Hostnames panel before proceeding
ie then
Open Server manager, Domains panel
Create archive.dc.local
Select Primary site for the i-bay setting (this does not matter much as the archive.dc.local domain site (on SME server) is only accessible locally from your SME server)
Select Resolve locally for the Domain DNS servers field, rather than Internet DNS servers
This will make SME server receptive to email sent to archive.dc.local
Note you will need to add a user named archive to the Server manager User panel
At this point you should be able to send an email message to archive@archive.dc.local using the SME server webmail system,
or using a LAN workstation connected to SME server using an email client that uses SME server as the smtp server.
It should arrive in the archive users mail box on SME server.
If the above test is OK,
Then run the command
db domains setprop archive.dc.local MailServer 212.*.*.*
signal-event email-update
Where 212.*.*.* is the LAN IP or remote IP of the mail server hosting archive.dc.local
If the archive.dc.local mail server is remotely located then this IP must be publicly accessible & resolvable
Please advise what this IP is 212.*.*.* so we can test it ?
Please provide answers.