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?