Hi,

I've just noticed that manually restored mails are not routed correctly to my mailserver. It happens for mails originating from an external domain, which I do fetch per pop-fetcher of Xeams.

Mails marked-as-good are routed perfectly though1

Xeams logs this while restoration:

2018-03-07 13:12:46,697 WARN  helper.c - Wanted to restore message but X_SMRecipient field was null. Will figure out the recipients from To and CC. File name = 00001_210_20180307_146868.eml

What then happens it tries to send the mail back to the originating mail-service (obviously parsed the recipients from "To"), which of course is nonsense. I can see no "X_SMRecipient"-fields in (possible) junk-mails eml-files.

This worked in earlier version of Xeams! Any ideas?

Thanks,

Nico

Nico,

Did you specify a local domain under SMTP Configuration? Make sure your local domain is present on that screen. This configuration makes Xeams not to do an MX lookup on the domain, but just forward the message to the desired IP.

Yes everything locally is specified.

Xeams is installed as a smtp-proxy for an exchange. Xeams does route mails from pop-fetcher perfectly fine to configured native exchange accounts, as long as they're "marked as good".

Once somebody does login, and tries to restore a quarantined (pop-fetched)-item, the link to the forwarded native-domain-user gets lost, and xeams will try to forward it back to the external smtp-host, which is of course undesired and will fail. I think Xeams misses in "restore"-function, the option to send it to the correlated local-user (configured in user-associations). And only in restore-function, it works otherwise on "marked as good" pop-fetched-items. I think it misses to change the recipient in the email-header, once it is quarantined.

Is there no logic, to change email-header of pop3-fetched items to the configured recipient in the fetcher, once it is quarantined?

Nicolas,

Could you please contact our support department via email. We are not sure if we fully understand the problem you're running into. Email/phone will help.