VSNext limitations

[Wolfgang]

some question regarding the limitations with VSNext

Mail Transfer Agent (MTA) support for Threat Emulation

No (PMTR-109026)

But Threat Extraction with MTA is fully supported ?

Object Sharing from on-premises Management Server to Infinity Portal

No (PMTR-109033)

Log Sharing from on-premises Management Server to Infinity Portal

No (PMTR-109034)

Infinity Playblocks service in Infinity Portal

No (PMTR-109035)

Any timeline known when this will be supported? Playblocks integration would be really great.

Anti-Spam and Email Security Blade

No (by design)

With normal VSX there is no box available to enable Antispam on the virtual gateway object. With VSNext it is, I can do all the configuration steps. Maybe it's working but not supported, any detailed information what's not working ?

[Silvan_Nyambu]

Hello @Wolfgang 

I recently enabled MTA on VSNext and it's working, though seems like its intermittent.

I realized is that the postfix within a VS runs in a separate directory unlike legacy setups where the Postfix configuration was shared across a single common directory layout and commands are controlled by the machine's primary runtime path.

When you check the queue from the primary path, below is the output: mail system is down

However, if you specify the explicit path where the postfix is running on VS1, you can see the queue, and the mail system is running as expected. This is the command: "/opt/postfix/CTX/CTX00001/usr/sbin/postqueue -c /opt/postfix/CTX/CTX00001/etc/postfix/ -p"

[Wolfgang]

@Silvan_Nyambu thanks for sharing. Yes, MTA is supported but not the Antispam-Feature, the Option the enable Antispam Blade is still not available and not supported.