Why are some messages containing long lines not posted out?
When you check the POST logs (starting PT), you see that the remote server has dropped the connection to GMS. If you examine the message that caused the problem, you find that one of the lines has over 80 characters on it.
This problem has NOTHING to do with GMS and is a problem with the configuration of the receiving server. GMS is performing its function of delivering email as per RFC821.
We have had this problem reported by customers trying to send email to company running WatchGuard firewall. It is the firewall that is failing to cope with the email message and dropping the connection. This means that the owner of GMS can’t resolve the problem but must contact the owner of the firewall.
Gordano has contacted WatchGuard Technical Support about this problem and they have provided us with the following solution:
Here are the steps for the configuration edit for oversized lines.
To resolve the “client sent oversized line” issue, you will need to edit the config file AFTER you have upgraded to 4.6.1
Open the 4.6.1 config in policy manager and save the config file to the desktop as “edit.cfg”.
Leave policy manager open and open wordpad and do a file>open and change the file type listing to “All files” and open edit.cfg from the desktop.
Insert the line
IT WILL NOT BE THERE BY DEFAULT….So you must manually enter it before the line
So when you are complete, it will look like this…
services.SMTP.proxies.smtp.max.line_length: 5000 services.SMTP.proxies.smtp.max.size: 15000 services.SMTP.proxies.smtp.max.to: 200
The second two lines will already be there, but you have to manually add the first one.
<service name> will be SMTP unless the user has changed the name of their SMTP proxy service.
Keywords:POST, send, long lines, long, WatchGuard, outgoing. queue