smaller reset larger        English         

Main Menu

All times are in GMT -8 (DST) :: The time is now 2:56 pm.

Sub Menu

Category Details
Category Name
SMTP
Category Created
Fri, 9th Mar 2007
Last Article Update
Tue, 11th Aug 2015
Category Actions
 
(Lost?)

   SMTP

DKIM in CommuniGate Pro 

Not natively, though there is support through a third party plug-in available here:

http://www.niversoft.com/products/cgscripts/domkeys

Please Note: This plug-in was not created nor is support directly by CommuniGate Systems.
View Full Article Add Comment

Error: Error Code=TLS alert record received 

We would suggest increasing the log level for TLS Sessions to 'All Info' on the 'Settings | General | Other' page of the CommuniGate Pro web administration interface. If there is another failure of this type, you will see more information related to TLS session itself and will be able to better understand what occurred.
 
Having said that, the most likely cause is that the server to which CGP is connecting requires a cipher that is not currently enabled. If you again take a look at the 'Settings | General | Other' page of the web administration interface, under the TLS Sessions section, you'll see the following two options (http://www.communigate.com/cgatepro/PKI.html#TLS):
 
1) CBC Ciphers for old TLS
2) Weak Ciphers
 
You could try enabling both (be sure to click update) and see if the problem continues. 
 
We would still suggest, at least temporarily, increasing the TLS Sessions log level. Even if the connections to these hosts start to work after enabling the above options, it's probably best to know for sure which cipher is being used.
View Full Article Add Comment

Failed to receive message body. Error Code=message line is too long 

This means that the message being submitted to CGP via SMTP has a single line that is in excess of the maximum value CGP will accept, i.e. the message is poorly formatted. The RFC standard recommends that the maximum length of a line be between 80 and 998 characters plus CR/LF (carriage return line feed). CGP even goes beyond this and will accept longer lines (up to 10,000 bytes), but the message being submitted to your server has a line that exceeds even CGP's maximum value.

View Full Article Add Comment

Inbound mail connections failing due to TLS after upgrading to 5.4 

CGP implemented the newly updates SSL/TLS protocols and these are incompatible with older systems. In order to avoid the problem you can include the --TLSServerHelloExtensions NO in the startup parameters.

 

See related article.

View Full Article Add Comment

Message Line is Too Long Error 

This error means that the message being submitted to CGP has a single line that is in excess of the maximum value CGP will accept, i.e. the message is poorly formatted. The RFC standard recommends that the maximum length of a line be between 80 and 998 characters plus CR/LF (carriage return line feed). CGP even goes beyond this and will accept longer lines (up to 10,000 bytes), but the message being submitted to your server when you see this error means that it has a line that exceeds even CGP's maximum value.
View Full Article Add Comment

SSL/TLS Version for Outbound SMTP 

One of the following CommuniGate Pro startup parameters (https://support.communigate.com/tickets/kb_article.php?ref=2558-RPGZ-2772) should be used to adjust the SSL/TLS version for outbound SMTP connections:
 
--SMTPOutgoingTLSVersion 0 (for SSLv3)
--SMTPOutgoingTLSVersion 1 (for TLSv1.0)
--SMTPOutgoingTLSVersion 2 (for TLSv1.1)
--SMTPOutgoingTLSVersion 3 (for TLSv1.2)
 
In short you'll create a 'Startup.sh' file in the '/var/CommuniGate' directory (or C:\CommuniGate Files if you're running on Windows) with contents similar to this:
 
-----
#### Startup.sh
SUPPLPARAMS="--SMTPOutgoingTLSVersion 2"
#### end Startup.sh
-----
 
Then you restart the CommuniGate Pro service. 
 
If '--SMTPOutgoingTLSVersion 2' is used, this is an example of what will appear in the CGP logs for an outbound SMTP connection:
 
07:42:30.967 2 TLS-000001 created(TLSv1.1,AES128_SHA256) -> [10.0.1.84]:25 for SMTP-000001
View Full Article Add Comment