blank

The following list provides only a small selection of apps able to display PDF Mails correctly.

Windows:

  • Adobe Acrobat Reader (Desktop version, free version available)

Android:

  • Foxit (free version available)
  • xodo PDF (free version available)

iOS:

  • Foxit (free version available)
  • xodo PDF (free version available)
blank

The following is an excerpt from the Cisco Knowledge Base:

Note

If you use Transport Layer Security (TLS) encryption for e-mail communication then the ESMTP inspection feature (enabled by default) in the PIX drops the packets. In order to allow the e-mails with TLS enabled, disable the ESMTP inspection feature as this output shows.

CiscoASA# config t
CiscoASA(config)# policy-map global_policy
CiscoASA(config-pmap)# class inspection_default
CiscoASA(config-pmap-c)# no inspect esmtp
CiscoASA(config-pmap-c)# exit
CiscoASA(config-pmap)# exit
CiscoASA(config)# exit
CiscoASA# wr me

Note

In ASA version 8.0.3 and later, the allow-tls command is available to allow TLS email with inspect esmtp enabled as shown:

config t
policy-map type inspect esmtp tls-esmtp
parameters
allow-tls action log
exit

policy-map global_policy
class inspection_default
no inspect esmtp
inspect esmtp tls-esmtp
Exit

blank

The default settings are as follows:

  • The first attempt takes place after 5 minutes.
  • The second attempt takes place after 10 minutes.
  • The third attempt takes place after 15 minutes.
  • Each additional attempt is made every 30 minutes.
  • The first delivery delay notification is generated after 6 hours.
  • The delivery is stopped after 1 day.
  1. Stop the gateway role. The corresponding settings are saved in the file “Gateway Role.config” in the directory “C:\ProgramData\Net at Work Mail Gateway\Configuration\” on all your installed gateway roles. S
  2. Search for the following line in the file:
    <netatwork.nospamproxy.proxyconfiguration ... >
  3. Add the following entry directly below this line if it does not already exist in a similar form:
    <queueConfiguration firstRetryInterval="00:15:00" secondRetryInterval="00:30:00" thirdRetryInterval="01:00:00" subsequentRetryInterval="04:00:00" expirationTimeout="3.00:00:00" sendDelayNotificationAfter="12:00:00" />
  4. Adjust the values to the desired value and save the file.
  5. Restart the previously stopped gateway role(s).
blank

How to change the SMTP connection properties of the gateway role

This article describes how to change the SMTP connection properties of the Gateway Role. The corresponding settings are made in the file “Gateway Role.config” in the directory “C:\ProgramData\Net at Work Mail Gateway\Configuration\”.

  1. Search for the following line in the file:
    <netatwork.nospamproxy.proxyconfiguration ... >
  2. Add the following entry directly below this line:
    <smtpServicePointConfiguration maxActiveConnectionsPerEndPoint="25" maxConnectionIdleTime="00:01:00" isServicePointRecyclingEnabled="false" maximumMailsPerSession="2" />
  3. Now adjust the values to the desired value.

Please note

Before you save the “Gateway Role.config” file, you must stop the “NoSpamProxy – Gateway Role” service. Only then you can save the configuration file properly.

blank

Version 9.0 or higher

As of version 9.0, the license manager is located on the start page of the management console on the upper right side of the screen, as shown in the following screenshot:

Lizenz installieren

 

 

 

 

 

Click Manage License to open the License Manager Wizard.

Alternate installation method

In some cases, licenses cannot be imported via the interface, e.g. because their runtime is shorter than that of the current license, or you can’t reach the interface at the moment and still urgently need to replace the license. In these cases, please proceed as follows:

Gateway or/and Intranet Role

The license is always stored as “license.xml” in the directory C:\ProgramData\Net at Work Mail Gateway\Configuration\.

This is a hidden directory which is not displayed by default. Before you overwrite the existing license, you should save it and then copy the new license as “license.xml” into the directory.

Then restart the services “NoSpamProxy – Gateway Role” or/and “NoSpamProxy – Intranet Role” in the Windows services to use the new license.

Web Portal

The license is stored as “license.xml” in the subdirectory “App_Data” of the Web Portal installation. The default path is:

C:\Program Files\Net at Work Mail Gateway\enQsig Webportal\App_Data\

Before you overwrite the existing license, backup the license and then copy the new license to the directory as “license.xml”. Then, as administrator, execute the command

iisreset.

blank

Configuration of a web proxy for NoSpamProxy Version 9.2 and higher

This article describes how to configure a proxy server for NoSpamProxy version 9.x and higher. The Cyren filter and antivirus also works via port 80, but this is configured separately:

How to configure Cyren services

Queries via Windows components

In order to be able to use the proxy for queries that are made directly via Windows components, such as a possible CRL check, you must store the proxy in the system. To do this, execute the following command as an administrator. This command adopts the proxy settings from Internet Explorer for the system components:

netsh winhttp import proxy source=ie

This is necessary on the server with the Intranet and Gateway Role of NoSpamProxy.

Gateway Role

To enter the proxy, the file NetatworkMailGatewayGatewayRole.exe.config from the directory “..\Net at Work Mail Gateway\Gateway Role” must be edited. The following lines must be added.

Copy and Paste does not work because invisible control characters are also copied.

<system.net>
<defaultProxy>
<proxy
usesystemdefault="true"
proxyaddress="http://192.168.1.10:3128"
bypassonlocal="true"
/>
</defaultProxy>
</system.net>

Adjust the IP address of your proxy server accordingly. The file should look similar to the following. However, please edit a copy of the original file!
Copy and Paste does not work because invisible control characters are also copied.

<?XML version="1.0" encoding="utf-8"?>
<configuration>
<runtime>
<gcServer enabled="true" />
<generatePublisherEvidence enabled="false"/>
<assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
<dependentAssembly>
<assemblyIdentity name="Microsoft.Practices.Unity" publicKeyToken="31bf3856ad364e35" culture="neutral" />
<bindingRedirect oldVersion="0.0.0.0-2.1.505.0" newVersion="2.1.505.0" />
</dependentAssembly>
<dependentAssembly>
<assemblyIdentity name="EntityFramework" publicKeyToken="b77a5c561934e089" culture="neutral" />
<bindingRedirect oldVersion="0.0.0.0-4.3.1.0" newVersion="4.3.1.0" />
</dependentAssembly>
<dependentAssembly>
<assemblyIdentity name="Microsoft.Practices.ServiceLocation" publicKeyToken="31bf3856ad364e35" culture="neutral" />
<bindingRedirect oldVersion="0.0.0.0-1.0.0.0" newVersion="1.0.0.0" />
</dependentAssembly>
<dependentAssembly>
<assemblyIdentity name="Newtonsoft.Json" publicKeyToken="30ad4fe6b2a6aeed" culture="neutral" />
<bindingRedirect oldVersion="0.0.0.0-7.0.0.0" newVersion="7.0.0.0" />
</dependentAssembly>
<dependentAssembly>
<assemblyIdentity name="Microsoft.Owin" publicKeyToken="31bf3856ad364e35" culture="neutral" />
<bindingRedirect oldVersion="0.0.0.0-3.0.1.0" newVersion="3.0.1.0" />
</dependentAssembly>
<dependentAssembly>
<assemblyIdentity name="Microsoft.Data.Edm" publicKeyToken="31bf3856ad364e35" culture="neutral" />
<bindingRedirect oldVersion="0.0.0.0-5.6.4.0" newVersion="5.6.4.0" />
</dependentAssembly>
<dependentAssembly>
<assemblyIdentity name="Microsoft.Data.OData" publicKeyToken="31bf3856ad364e35" culture="neutral" />
<bindingRedirect oldVersion="0.0.0.0-5.6.4.0" newVersion="5.6.4.0" />
</dependentAssembly>
<dependentAssembly>
<assemblyIdentity name="System.Spatial" publicKeyToken="31bf3856ad364e35" culture="neutral" />
<bindingRedirect oldVersion="0.0.0.0-5.6.2.0" newVersion="5.6.2.0" />
</dependentAssembly>
<dependentAssembly>
<assemblyIdentity name="Microsoft.Data.Services.Client" publicKeyToken="31bf3856ad364e35" culture="neutral" />
<bindingRedirect oldVersion="0.0.0.0-5.6.4.0" newVersion="5.6.4.0" />
</dependentAssembly>
</assemblyBinding>
</runtime>
<system.net>
<defaultProxy>
<proxy
usesystemdefault="true"
proxyaddress="http://192.168.1.10:3128"
bypassonlocal="true"
/>
</defaultProxy>
</system.net>​​
</configuration>

If you want to define exceptions, add the following section directly above the line </defaultProxy>

<bypasslist>
<add address="[a-z]+\.contoso\.com$" />
<add address="192\.168\.\d{1,3}\.\d{1,3}" />
<add address="intranet.nospamproxy.de" />
</bypasslist>​

If it is absolutely necessary to say that NO web proxy is to be used, the following must be entered:

<system.net>
<defaultProxy enabled="false" />
</system.net>

After you have modified the file, restart the Gateway Role.

Please note that the file may be overwritten with each patch/upgrade and the changes must be made again.

Intranet Role

If you want to assign a proxy to the Intranet role, this can be done in the same way as described above using the NetatworkMailGatewayIntranetRole.exe.config from the directory “..\Net at Work Mail Gateway\Intranet Role”. Please note that the Intranet Role requires direct communication with the Gateway Role. You should therefore define proxy exceptions for the Gateway Role(s).

Outlook Add-in

If a Web Proxy with authentication is used on the client PC, it is possible that the NoSpamProxy Outlook add-in cannot upload files to the Web Portal from the client PC because the information from the system variables do not apply here. To make this information available to the add-in, however, you must perform the following steps:

    1. In the Microsoft Outlook installation directory, create a new file named “Outlook.exe.config” next to the “Outlook.exe” file.
    2. Enter the following information into this file and save it:
      <configuration>
      <system.net>
      <defaultProxy useDefaultCredentials="true" />
      </system.net>
      </configuration>
    3. Restart Outlook.

Find more information on the Microsoft Website.

blank

General information concerning NospamProxy updates

Whenever you install an update of NoSpamProxy, you need to consider the following points, regardless of whether it is an update within a version or a larger version jump.

Proxy settings

The proxy settings are done in a configuration file. In the How Tos category you will find the article How to configure a web proxy for NoSpamProxy Version 9.2 or higher with the exact procedure. Unfortunately these settings are overwritten with each update and must be carried out again afterwards. Therefore, copy the corresponding configuration files into a backup directory in advance in order to be able to use them again afterwards.

IMPORTANT: For updates within e.g. 10.1 or 10.0 the files can be used 1:1. For updates from 9.x to 10.x, the changes must be made on the basis of the new files. Please refer to the above mentioned article.

Template adaptations

If you update from NoSpamProxy 10.x or earlier to a newer version, you still have to save the template files of NoSpamProxy manually. The articles on customising the Web Portal theme and the notification theme describe how to customise each file. These are overwritten for version 10.x with each update and must be saved in advance. After the update, copy the files back to the original directory. With version 11.x a template designer is integrated in NoSpamProxy. From this point on, this step is no longer necessary, unless you have adapted the texts in the templates.

Please note: For updates within e.g. 10.1 or 10.0 the files can be used 1:1. For updates from 9.x to 10.x, the changes must be made on the basis of the new files. Please refer to the above mentioned articles.

Web Portal

If the Web Portal was installed on a server without the Gateway Role, the configuration link https://<server-url>/enqsig/admin/configurecyren must be called again after the update. The NoSpamProxy CYREN Service service must then be restarted on the Web Portal.