Currently, the library supports a single separator (e.g., ,) for parsing email lists. However, in real-world use cases, email lists often include multiple separators such as ,, ;, or even newline characters (\n). Supporting multiple separators would enhance the library’s flexibility and make it more robust for diverse inputs.
This is fixed in this PR: #65