-
Notifications
You must be signed in to change notification settings - Fork 580
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
If file for Embed() is missing, the error is returned but email is still sent #65
Comments
Same problem exists on attachments as well |
yep @leventogut I was suspecting it may affect regular attachments as well. |
haven't checked the code either , I am handling this on upper level not to cause any problems. have been quite busy so couldn't spend time on it . |
Any thoughs on that @alexcesaro ? In theory there's this |
I implemented a fix for this issue. Check my pull request. #97 |
Looks cool. Will integrate it soon with my client code. |
Hi!
This library is very helpful.
However, I encountered an inconsistent behaviour which I believe is a bug.
When a file given as an argument to
Message.Embed(...)
is missing on the filesystem,there's no error returned (this method returns nothing).
Later, when calling
Send(sender, message)
,error is returned, but the email is sent (without embedded data of course).
This is confusing - I'd rather expect that when there's an error, an email would not be sent. When it works this way, I cannot really differentiate between such error and other error stopping message from being sent.
The text was updated successfully, but these errors were encountered: