Allow non-strict email address validation #83
Comments
This would be very useful. I'm using Zend-Mail to parse emails that arrive in an inbox and therefore have no control over their header values. When calling
A quick and dirty solution would be to add some static method like |
I completely agree with @steffenweber. We use Zend Mail along with Zend Mime to parse bounce reports. And those often contain something like |
+1 |
Similar issue here. When iterating over an inbox (where you don't have control over the messages in there), I am e.g. running into In my case the Is there a good way to work around this? I'd guess that almost every "real life" inbox contains mails with such unexpected headers, which makes it almost impossible to iterate over an inbox. |
Hello, I did solve it with Validator quick fix for Moon Box. Cf : Monwoo/MoonBox@0636a95#diff-1a8dca4bf22bff2976d4f1eac7e2f50f Use composer Autoload feature to quick fix vendors files : Then, allow validation on failing case ('<>' for my case) :
=> Monwoo/MoonBox@0636a95#diff-54278b9d8fed58a67d9f6b35ad65321dR525 |
This repository has been closed and moved to laminas/laminas-mail; a new issue has been opened at laminas/laminas-mail#64. |
Add ability to specify whether EmailAddressValidator used by AddressList should validate the email with the
strict
flag set or not.The text was updated successfully, but these errors were encountered: