Hi,
in reference to the following git thread:
opened 09:30AM - 23 Apr 19 UTC
closed 09:52AM - 23 Apr 19 UTC
can't reproduce
<!--
Hi there - thanks for filing an issue. Please ensure the following things … before creating an issue - thank you! 🤓
Since november 15th we handle all requests, except real bugs, at our community board.
Full explanation: https://community.zammad.org/t/major-change-regarding-github-issues-community-board/21
Please post:
- Feature requests
- Development questions
- Technical questions
on the board -> https://community.zammad.org !
If you think you hit a bug, please continue:
- Search existing issues and the CHANGELOG.md for your issue - there might be a solution already
- Make sure to use the latest version of Zammad if possible
- Add the `log/production.log` file from your system. Attention: Make sure no confidential data is in it!
- Please write the issue in english
- Don't remove the template - otherwise we will close the issue without further comments
- Ask questions about Zammad configuration and usage at our mailinglist. See: https://zammad.org/participate
Note: We always do our best. Unfortunately, sometimes there are too many requests and we can't handle everything at once. If you want to prioritize/escalate your issue, you can do so by means of a support contract (see https://zammad.com/pricing#selfhosted).
* The upper textblock will be removed automatically when you submit your issue *
-->
### Infos:
* Used Zammad version: 2.9
* Installation method (source, package, ..): package
* Operating system: Debian 9
* Database + version: -
* Elasticsearch version: -
* Browser + version: Firefox latest
### Expected behavior:
* When answering via reply button and adding an invalid e-mail address to "TO" or "CC" Zammad throws an error and notifies the user that the e-mail address is invalid and where without trying to actually send to the invalid e-mail.
### Actual behavior:
* Initially no error message, email sending for that particular group is completely stuck and has to be killed manually. After killing the mail sending process error message is shown identifying the issue with the typed email address:
> Delivery failed: "Unable to send email to 'testmail@example.com”': Can't use Channel::Driver::Smtp: #<Net::SMTPSyntaxError: 501 <testmail@example.com”>: malformed address: ”> may not follow <testmail@example.com >"
It would be great if the mail sending process would not be initiated before the validity of the e-mail address is checked.
### Steps to reproduce the behavior:
* Create new ticket
* Answer via mail
* Add receiver e-mail address to "TO" that has a trailing " symbol after the domain name.
* Try sending mail via smtp
Yes I'm sure this is a bug and no feature request or a general question.
It would be great if a email address validity check could be added when creating users or when sending emails via zammad and writing addresses into the TO/CC fields.
The issue is that oftentimes when moving customers manually to zammad after a phone call or similar e-mail addresses are quickly typed or copy pasted from other e-mails etc. which can lead to invalid mail addresses due to typos or unsupported characters.
Currently Zammad only checks if the string has a top level domain after the @ and that is it.
This leads to the situation that a user can be created with email address: examplename@exampledomain.com1312151
Adding an actual email validity check like e.g. the web form has would avoid unwanted follow up issues.
BR,
Nino
3 Likes
system
Closed
June 13, 2020, 4:20am
2
This topic was automatically closed after 416 days. New replies are no longer allowed.