-
Notifications
You must be signed in to change notification settings - Fork 16
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
OutOfMemoryError has been occurred #158
Comments
According to the code, it seems that the response from the email server is not verified. protected int readServerResponse() throws MessagingException {
|
@hehexiansheng123 could you attach the stacktrace of the OutOfMemoryError, please?. I know that could happen in an unrelated area, but just in case it happens in the place we need to take a look... |
@jbescos my colleagues had upload the stack information, take a look please, thanks bro |
Thank you both, @hehexiansheng123 and @baoxinggit @jmehrens , I am thinking to provide a new property with a default value in Do you have any suggestion?. |
it seems a good idea, I think it's best to add a read length limit to the response body in the readLine method. |
I need to do some more work to provide better informed feedback. That said, I wonder if there is something documented in the RFCs about max length of a server response. If so we might be able to enforce a hard limit without a new property. Adding a new property seems fine if no other alternative. Choosing right default might get tricky. We should spend time thinking about adding enough namespace to the property to allow parent/child control of buffer sizes. E.G. all of Angus Mail, smtp, imap, pop3, and classname. Then decide if that provides value. |
This thread talks a bit on limits: |
My product tester is connected to a self-built email server. When verifying the email account or sending emails, a large packet is returned, causing memory overflow. Does this software verify the packet length in these two scenarios? If it is not verified, it is vulnerable to attacks.
Thanks
The text was updated successfully, but these errors were encountered: