Go Premium for a chance to win a PS4. Enter to Win

x
?
Solved

Wireshark SSL and SurgeMail

Posted on 2010-11-29
4
Medium Priority
?
665 Views
Last Modified: 2012-05-10
Hi,

I've enabled SSL in SurgeMail for a certain domain that i wan't to send to only using SSL.
When sniffing the packets i can read every packet both ways.  I'm guessing this means that my mail server is sending everything in clear-text (and my SSL setup is wrong)?  

The reason im asking is because there could be that possibility that Wireshark can read the packets unencrypted because im sniffing directly on the mail interface?



0
Comment
Question by:olemrefv
  • 3
4 Comments
 
LVL 40

Accepted Solution

by:
noci earned 500 total points
ID: 34235035

Do the packets resemble something from the below page (the top level being Secure Socket Layer)
http://wiki.wireshark.org/SSL

Did you configure certificates in Wireshark, if not then it can't decode.

0
 

Author Comment

by:olemrefv
ID: 34246273
Ok, so my packets are not being sent using SSL.  I've added 2 cluster domains, and the IP's to these clusters under: "Other machines we only send to using SSL ip or domain" (SurgeMail).

When using smtpdiag.exe i send an email to a recipient being handled by the clusters, and my packets are still unencrypted. Here is the process:
SOA serial number match: Passed
Both TCP and UP queries succeeded. Local DNS test passed.
Both TCP and UP queries succeeded. Remote DNS test passed.
Successfully connected to cluter.xx.xxxxxxx.com (8 times)
Error: Expected "250". Server Rejected the recipient address.
Failed to submit mail to cluster.xx.xxxxxx.com


The recipient require SSL, so is this the reason for the error?  I can't see any "evidence" of my mail server and the receiving end having some kind of negotiation of SSL.
My SSL certificate in SurgeMail is valid.
0
 
LVL 40

Expert Comment

by:noci
ID: 34248220
This is not an SSL issue per se..
250 is the status returned when an address is acceptable. So that value is expected.

The message received is: Server Rejected address, so the target host clearly doesn't like the receipient address.
0
 
LVL 40

Expert Comment

by:noci
ID: 34248258
It only is an SSL issue if you can tell the mail receiver that this account can only come from SSL protected links.
and the connection isn't SSL secured.

Also what port do you connect to, 25 is normaly not encrypted but can be encrypted using TLS if needed,
port 465 is the SSL encrypted port.
0

Featured Post

WatchGuard Case Study: NCR

With business operations for thousands of customers largely depending on the internal systems they support, NCR can’t afford to waste time or money on security products that are anything less than exceptional. That’s why they chose WatchGuard.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

If you thought ransomware was bad, think again! Doxware has the potential to be even more damaging.
In 2017, ransomware will become so virulent and widespread that if you aren’t a victim yourself, you will know someone who is.
With Secure Portal Encryption, the recipient is sent a link to their email address directing them to the email laundry delivery page. From there, the recipient will be required to enter a user name and password to enter the page. Once the recipient …
Monitoring a network: how to monitor network services and why? Michael Kulchisky, MCSE, MCSA, MCP, VTSP, VSP, CCSP outlines the philosophy behind service monitoring and why a handshake validation is critical in network monitoring. Software utilized …
Suggested Courses
Course of the Month9 days, 8 hours left to enroll

877 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question