2022-04-29 22:13:04,237 INFO reports.E - Email summary report sent to user@domainnet.net in 547 ms.
2022-04-29 22:13:05,033 ERROR a.D -
java.lang.NullPointerException
at com.synametrics.commons.net.mail.Z.C(EmailHeader.java:138)
at com.synametrics.xeams.l.J.C(GatewayManager.java:54)
at com.synametrics.xeams.a.D.c(SmtpProxyWorker.java:1649)
at com.synametrics.xeams.a.D.C(SmtpProxyWorker.java:1196)
at com.synametrics.xeams.a.E.run(SmtpProxyWorker.java:1987)
at java.lang.Thread.run(Thread.java:748)
2022-04-29 22:13:05,035 ERROR connector.I - Unable to determine profile from header [javax.mail.internet.InternetHeaders@291c2a6]. Assuming default profile. Error: null

Anyone know? My system updated to 8.2 build 6227 last night. I am pretty sure I was at the latest before this release and have never had issues.

thanks

John

Following post fixed me issue, but this looks like a bug..

https://www.xeams.com/app?operation=forum&st=viewOneArticle&id=16620

This is not a bug. By default, you do not need an entry in hosts.txt file. This is because the MX record for your domain typically points to the same IP where Xeams runs. In your case, since port 25 is blocked, you need to explicitly add an entry in hosts.txt file so Xeams would send emails to a different port.

Hi,

I know for sure, this was not the case in previous versions, I never had to add the port in the loca host file.

Cheers,

Hemant

Hemant,

This logic hasn't changed for years. However, it is possible that your Xeams were configured differently causing it to work earlier. Here is what happens when you use the SMTP Proxy server for inbound email. (I assume you're using the Proxy. If not, let me know).

• When using Proxy, the destination port is specified in Proxy configuration rather than hosts.txt file
• Xeams adds a temporary header in every message containing the host name and port, eliminating the need for hosts.txt. This logic works fine for incoming emails.
• However, emails that are generated by Xeams, such as Quarantine Reports, do not contain this header. Therefore, they end up performing MX Lookups, which works fine if your DNS points to the IP address where Proxy is listening. In other words, such messages will go out and come back in.
• If your configuration is modified somehow in a way that prevents messages from going out and coming back in, that will make the quarantine reports sit in the queue. The only way to fix that is to specify the port and IP in hosts.txt, which eliminates the need for MX lookups.

I also have not had to touch the config in years and running in proxy mode (just using it for spam filtering) So was surpised when it also was not working. I am using cloudflare and a number of other devices and softwar items outside of xeams, so possible something changed up ahead of the proxy or on the smtp server (I've not changed anything outside of patching of devices firmwares, os patchs, etc)

Looks like I will need to change my setup anyways as I as told proxy will be deprecate in a later version. hope that holds off until I can get migrated my VMs to RHEL8 and containerize everything.