Tickets :: [#7070] Sending email message: validation failed imp 4.2

6.0.0-RC7

6/18/26

History
Attachments
Comment
Watch
Download

Summary	Sending email message: validation failed imp 4.2
Queue	IMP
Queue Version	4.2
Type	Bug
State	Duplicate
Priority	1. Low
Owners
Requester	bug.horde (at) nowsales (dot) nl
Created	7/15/08 (6547 days ago)
Due
Updated	9/9/08 (6491 days ago)
Assigned	7/16/08 (6546 days ago)
Resolved	9/9/08 (6491 days ago)
Github Issue Link
Github Pull Request
Milestone
Patch	No

41	Michael Slusarz	State ⇒ Duplicate

361	jkau (at) jasper (dot) k12 (dot) ga (dot) us	Comment #10	Reply to this comment
And thus it's just a variation on ~~Bug #6899~~ which has been fixed in the CVS

4411	jkau (at) jasper (dot) k12 (dot) ga (dot) us	Comment #9 New Attachment: imp-validation-error.jpg	Reply to this comment
It has nothing to do with the identity full name being a domain. The bug is triggered when you have a "." in your identity full name with no spaces. So: J. Kau works but J.Kau does not and returns the validation failed.

2810	Jan Schneider	Comment #8 State ⇒ Not A Bug	Reply to this comment
Unless someone can track this down, or a developer can reproduce it, we can't do anything about it.

3511	Jan Schneider	Comment #7	Reply to this comment
I don't see this with Mail 1.1.4 either.

4711	a-dinc (at) hotmail (dot) de	Comment #6	Reply to this comment
I can't reproduce this. I'm facing the same problem here.

251	info (at) nowsales (dot) nl	Comment #5	Reply to this comment
I have installed the mail-beta but I still get the same message. I can't reproduce either - I am sending a message as follows: example.com <test@example.com> and it works. Also, are you using PEAR's Mail package v. 1.2.0b1? There has been several fixes to validation in that library since 1.1.4.

459	Michael Slusarz	Comment #4	Reply to this comment
I can't reproduce either - I am sending a message as follows: example.com <test@example.com> and it works. Also, are you using PEAR's Mail package v. 1.2.0b1? There has been several fixes to validation in that library since 1.1.4.

574	miks (at) skynet (dot) lv	Comment #3	Reply to this comment
I can't reproduce this. I also get this error. Solution with Identity Name works, but it's only temporary solution.

1910	Jan Schneider	Comment #2 State ⇒ Feedback	Reply to this comment
I can't reproduce this.

469	bug (dot) horde (at) nowsales (dot) nl	Comment #1 State ⇒ Unconfirmed Patch ⇒ No Milestone ⇒ Queue ⇒ IMP Summary ⇒ Sending email message: validation failed imp 4.2 Type ⇒ Bug Priority ⇒ 1. Low	Reply to this comment
Last night we upgraded to IMP 4.2 on Horde 3.2.1, everything was fine except for one user who got the following error when sending an email through the webinterface: Validation failed for: IdentityName <i...@domainname.com>. The identity and compose message options and those are correct/filled out (correct identity / emailaddress are shown in the errormessage). Our logs show: HORDE [error] [imp] Validation failed for: IdentityName <i...@domainname.com> [pid xxxxx on line 720 of "/var/www/html/horde/ imp/lib/Compose.php"] [debug] [imp] There was an error sending your message: Validation failed for: IdentityName <i...@domainname.com> [pid xxxxx on line 176 of "/var/www/html/horde/lib/Horde/Notification.php"] SOLUTION VIA SETTINGS Apparently you get this error if your Identity Name is the same as you domain name i.e. Identity Name = yourdomain.com... change it and everything works again :S