Leona

On doing some tests with the "split" at the end, or any position, I've noticed a bug when the client process the second message. Looks like the ClientAccountSelector is not used when connecting to the remote server if the content's "To" field has more than one recipient. Even if the envelope is all correct. Am I missing something?

You nailed it! The problem is well described. Actually, the "split" is running before the ClientAccountSelector. You say it's better to be after it? I had to set the "forward-to" because it is required by the "forward" parameter. Otherwise I get an error on starting the service. As for your question, I guess would be better if a failed MX lookup result in connecting through AAAA address. And I prefer simplify the management, avoiding using local DNS. Adding a client filter to set the two fields in...

Hi Graeme, I am struggling to make it work. Previously my single bat/service configuration was: start emailrelay --server-auth=@app/EmailRelay.auth --port=25 --remote-clients --client-auth=@app/EmailRelay.auth --client-tls --forward --forward-on-disconnect --forward-to-some --forward-to=smtp.office365.com:25 --close-stderr --spool-dir=@app/spool --log --log-address --log-file=@app/EmailRelay-log-%%d.txt --log-time --pid-file=@app/EmailRelay.pid --client-filter=msgid: --verbose --X-remote-clients...

You nailed it! The problem is well described. Actually, the "split" is running before the ClientAccountSelector. You say it's better to be after it? I had to set the "forward-to" because it is required by the "forward" parameter. Otherwise I get an error on starting the service. As for your question, I guess would be better if a failed MX lookup result in connecting through AAAA address. And I prefer simplify the management, avoiding using local DNS. Adding a client filter to set the two fields in...

Hi Graeme, I am struggling to make it work. Previously my single bat/service configuration was: start emailrelay --server-auth=@app/EmailRelay.auth --port=25 --remote-clients --client-auth=@app/EmailRelay.auth --client-tls --forward --forward-on-disconnect --forward-to-some --forward-to=smtp.office365.com:25 --close-stderr --spool-dir=@app/spool --log --log-address --log-file=@app/EmailRelay-log-%%d.txt --log-time --pid-file=@app/EmailRelay.pid --filter=@app/emailrelay-impersonation.js --client-filter=msgid:...

Change request on Multiple Processes

Hi Walker Increasing the verbosity of the logging was the key to finding the solution. I have a problem with the local name server and because of that, I was pointing the mx filter to a public dns without specifying the port, which causes a failover to the local dns. As the issue described before happens also using only the split and mx filters, I was mislead to believe that it was something caused by the split/mx processing, also because I could see the resolved IP of the destination domain in the...

Hi Walker Increasing the verbosity of the logging was the key to finding the solution. I have a problem with the local name server and because of that, I was pointing the mx filter to a public dns without specifying the port, which causes a failover to the local dns. As the issue described before happens also using only the split and mx filters, I was mislead to believe that it was something caused by the split/mx processing, also because I could see the resolved IP of the destination domain in the...