Anonymous | Login | 03-07-2021 08:55 UTC |
Main | My View | View Issues | Change Log | Docs |
Viewing Issue Simple Details [ Jump to Notes ] | [ View Advanced ] [ Issue History ] [ Print ] | |||||||||||
ID | Category | Severity | Reproducibility | Date Submitted | Last Update | |||||||
0000151 | [Squeak] Network | minor | always | 09-17-04 00:14 | 12-10-05 21:12 | |||||||
Reporter | KenCausey | View Status | public | |||||||||
Assigned To | gokr | |||||||||||
Priority | normal | Resolution | open | |||||||||
Status | assigned | Product Version | ||||||||||
Summary | 0000151: MailMessage cannot send to more than one email address | |||||||||||
Description |
In the MailComposition (MailMessage) window which comes up when doing 'mail to list' from the changesorter, or 'mail out bug report' from the debugger, or 'email package maintainers' from SqueakMap, etc., it doesn't seem possible to send the email to more than one address. (Yes, this means that 'email package maintainers' in SM doesn't work after all if there is more than one maintainer :-( ... ) I'm not sure now if the problem is in MailMessage or in SMTPClient>>recipient:. (I guess the DecentReviewerNotePad in BFAV sends to multiple To: address somewhat successfully, but it uses multiple To: fields which has the side-effect of confusing some email clients, and is not RFC822 approved.) I tested this three different ways, by editing the contents of the To: portion of the MailComposition window, with the results below.... - Doug Test 1: ------------------------ "From: dway@mailcan.com To: dway@mailcan.com, dew_dropper@hotmail.com Subject: Regarding Whisker Browser testing" -> 553 5.1.3 <dway@mailcan.com, dew_dropper@hotmail.com>... Invalid route address Test 2: ------------------------ From: dway@mailcan.com To: <dway@mailcan.com>, <dew_dropper@hotmail.com> Subject: Regarding Whisker Browser testing" -> no error, but email only gets sent to the last address. (SMTPClient adds brackets around the whole To list, like this: "<<dway@mailcan.com>, <dew_dropper@hotmail.com>>" Test 3: ------------------------ "From: dway@mailcan.com To: dway@mailcan.com To: dew_dropper@hotmail.com Subject: Regarding Whisker Browser testing" -> 553 5.1.3 <dway@mailcan.com, dew_dropper@hotmail.com>... Invalid route address |
|||||||||||
Additional Information | Transferred from BFAV2 ID 23377 reported by Doug Way <dway@mailcan.com> | |||||||||||
Attached Files |
![]() ![]() |
|||||||||||
|
![]() |
|||||||||||||
|
![]() |
|
(0002110 - 521 - 621 - 621 - 621 - 621 - 621) KenCausey 08-04-05 00:01 |
frank.shearar@rnid.org.uk: "Change Set: MailMessageTo-fbs Date: 29 June 2004 Author: Frank Shearar Currently MailMessage allows all sorts of undesirable occurences, like allowing multiple To lines. RFC 2822 forbids this. This changeset supplies a protocol that, if used, guarantees that you can add as many recipients as you like to a MailMessage while maintaining a single To header. Too, this changeset moves MailMessage to the Network-RFC822-Tests category." (attaching MailMessageTo-fbs.cs.gz) |
(0002111 - 141 - 169 - 169 - 169 - 169 - 169) KenCausey 08-04-05 00:03 |
dway@mailcan.com: "Definition for MailMessageTest seems to be missing from this changeset. Would like to approve this soon if possible!" |
(0002112 - 447 - 537 - 575 - 575 - 575 - 575) KenCausey 08-04-05 00:06 |
Doug Way <dway@mailcan.com>: "MailMessage is definitely in need of some help. Most annoying is that there are getters/accessors for "to", "cc" and other commonly used fields, but no setters... you have to call setField:/setFields: with a hardcoded 'to' string, etc. Maybe this should just be cleaned up in 3.8. Although this changeset is a reasonable first step. (Except it's missing the test class definition for some reason.)" |
(0002113 - 190 - 246 - 288 - 288 - 288 - 288) KenCausey 08-04-05 00:09 |
"Frank Shearar" <frank@angband.za.org>: "This contains the class definition (which my image had from Ken Causey's HeaderFolding-klc changeset)." (attaching MailMessageTo-fbs.1.cs.gz) |
(0002114 - 197 - 231 - 231 - 231 - 231 - 231) KenCausey 08-04-05 00:13 |
frank@angband.za.org: "Hm, I just noticed the reorganization thingy in the end of my v2 changeset references a nonexistent method - I hope this doesn't cause trouble, but it can just be axed." |
(0002115 - 505 - 587 - 668 - 668 - 668 - 668) KenCausey 08-04-05 00:15 |
dway@mailcan.com: "This is not really the fault of Frank's changeset, but it seems that MailMessage still needs more work. If I create a MailMessage and use addRecipient:, I can add a few To: addresses, which show up successfully as separated by commas in the To: field of the MailMessage editor. But MailMessage still tries to wrap angle brackets around everything in the To: field when it gets sent. Like this: <address1@company.com, address2@myco.com> ...which my SMTP server rejects." |
(0002116 - 217 - 217 - 217 - 217 - 217 - 217) KenCausey 08-04-05 00:17 |
The first message cannot be filed in because it attempts to add methods to a class not defined in 3.8-6665-basic. The second files in without errors and the included tests pass. I did not test or examine it further. |
Mantis 1.0.8[^]
Copyright © 2000 - 2007 Mantis Group
71 total queries executed. 45 unique queries executed. |