:mailbox_with_mail: YAM (short for 'Yet Another Mailer') is a MIME-compliant open-source Internet email client written for Amiga-based computer systems (AmigaOS4, AmigaOS3, MorphOS, AROS). It supports POP3, SMTP, TLSv1/SSLv3 connection security, multiple users, multiple identities, PGPv2/v5 encryption, unlimited hierarchical folders, an ARexx interface, etc...
Originally by @raziel- on 2015-11-01 18:08:20 +0100
Summary
If i write (by accident, of course ;-) ) a broken address into the CC field and open that eMail after trying to send (it's not being sent, of course) in YAM's editor with "Edit", YAM or the Editor's parser is changing the broken address to soemthing else by cutting a part off and adding something on it's own, which is wrong.
It's probably replacing the broken part from the 1st users eMail address or something like that.
Steps to reproduce
Click on New eMail
Use any eMail address in the TO field
Use i.e. "A Stupid User <stupid@ stupid.net" as CC address (mind the missing closing >!!!)
(Also don't put the space in there, YAM's bug tracker will cut the address off, which is good :-) )
Now try to send the mail...it will get caught by the server...it throws a 501 for me, but YAM will also put the eMail into OUTGOING
Mark and EDIT that eMail...the CC field is filled with "A@ web.de" for me...which is more than wrong :-)
But it shows that the parser is trying to fix the problem by taking the address from my address (i think) which happens to be @web.de.
Expected results
Not really sure, maybe an error requester on sending that the format of the address is wrong or broken, just like it happens with when i miss the subject?
Actual results
Described above, plus a shortly puzzled user who asks himself wtf is wrong again with the server ;-)
Regression
No idea, never happened before though, as long as i can remember
Notes
1) It's interesting that if i write a valid address in the TO field it's still not being sent.
2) If i doubleclick the broken eMail to simply show it, the broken address is still there (so i guess it's a problem in the Editor?)
3) If i only use two words with a space, i.e. "Stupid User" the whole CC field will be erased when i open it in the Editor, three or more words and it will show up broken.
YAM_UT.c: treat address/name combinations like "name abc@de.fg" and "abc@de.fg (name)" in the same fashion when separating them into address and realname parts. This refs #609.
mui/RecipientString.c: when resolving recipients the address is checked to be really valid, i.e. no spaces in the the address part, correctly paired angle brackets, etc. Invalid recipients will be kept now instead of being removed silently and an error message will be popped up instead. Effectively this makes it impossible to send off mails with invalid recipients. This finally closes #609.
Originally by @raziel- on 2015-11-01 18:08:20 +0100
Summary
If i write (by accident, of course ;-) ) a broken address into the CC field and open that eMail after trying to send (it's not being sent, of course) in YAM's editor with "Edit", YAM or the Editor's parser is changing the broken address to soemthing else by cutting a part off and adding something on it's own, which is wrong. It's probably replacing the broken part from the 1st users eMail address or something like that.
Steps to reproduce
Expected results
Not really sure, maybe an error requester on sending that the format of the address is wrong or broken, just like it happens with when i miss the subject?
Actual results
Described above, plus a shortly puzzled user who asks himself wtf is wrong again with the server ;-)
Regression
No idea, never happened before though, as long as i can remember
Notes
1) It's interesting that if i write a valid address in the TO field it's still not being sent. 2) If i doubleclick the broken eMail to simply show it, the broken address is still there (so i guess it's a problem in the Editor?) 3) If i only use two words with a space, i.e. "Stupid User" the whole CC field will be erased when i open it in the Editor, three or more words and it will show up broken.