Messaging Gateway

Dear sir

I have the below queries please help.......

very often we are unable to connect to SMS GW through Putty  where as the GUI Console connectivity is fine, need to reboot the appliance for restoring the connectivity. Error Snapshot below.

Also we have one requirement on attachment size limits:  Normally all users are having 6mb as the attachment size limit  across the organization, where as few users have exception with 15mb, so can we configure such a way on the GW to allow only 15mb attachment to these specified users and drop for other users with more than 6mb attachment

 Please share the configuration for the above

Regards

Sraj

I am very curious about the SSH connection issue, but unfortunately the snapshot did not get attached correctly (it doesn't look like it was uploaded to the forum servers). Typically, an issue like the one you are describing is environmental in nature, meaning it often has something to do with the network or access controls; though, it is odd that rebooting the appliance corrects the situation.

As to the second question, you can accomplish this with Content Filters. You would add a condition for the attachment size: Content > Add > Select (blank template) > Add (condition)

You can then add an action to handle the message or attachment, and use these filters in different Policy Groups for the different groups of users. Be sure you are allowing large enough messages by default: Administration > Hosts : Configuration > Edit (scanner) > SMTP > Advanced Settings > Maximum message size in bytes (inbound / outbound)

Dear 

Thanks for the solution provided , Find the missed attachment for the first question , meanwhile i will test the second solution you have provided to me 

Regards

Sraj

Attachment(s)

Doc1_4.docx   30 KB 1 version

Well, that's a pretty generic connection termination error. I am still inclined to believe this is an environmental issue (network issue, firewall, other security), particularly since other network connections are working fine. However, you can do a simple test to find out a little more.

When the issue is occuring and putty does not connect, if you can log into the console command line itself (that is, directly at the appliance keyboard), using the admin account, you can try the following command:

telnet localhost 22

SSH should respond with some versioning information. If it does not respond with versioning information, then make sure there are no SSH access rules involved:

sshd-config --list

If there are any access rules listed, it may be part of the issue. You can modify the access rules by using the sshd-config add/delete commands. For more information, use:

sshd-config --help

If there are no access rules listed, and you cannot connect locally, you may be running into system resource issues. I would recommend opening a case with support at that time.

Hello there 

Thanks for the support 

Regards

Sraj

Have your questions been answered? If so, please mark this thread as solved so thatthis we can focus on unresolved questions.

Thank you.