Reply All Error

When I used the 'reply all' button I received an error warning about one address being malformed. Is it normal that this causes all other addresses to be dropped as well? I tested it by sending a mail to both my yahoo and hotmail accounts malforming the latter and indeed the yahoo seems gone as well.
Also, in the first example, when I manually delete the culprit my Sent folder shows just one entry, I have to open it to see that it does contain all other mail addresses.

Originally posted by bartgzn:

When I used the 'reply all' button I received an error warning about one address being malformed. Is it normal that this causes all other addresses to be dropped as well?

Don't know if it's normal or not. Never received that error. Did it look like an Opera dialog that popped up? If so, were you able to dismiss it and still send the message or did you have to remove the address in the compose field first? Or, was it Opera's error console reporting to you the error that the smtp server gave Opera? (You said you manually deleted it, but I'm not sure if you meant in the compose field or if you edited the copy in "All Messages/Sent" and resent it without the malformed address.)

If Opera allowed you to send the message with the malformed address, then it was probably the smtp server that reported the error and whether other addresses are dropped too would depend on how the smtp server handled it ("To" header parse error where it couldn't figure out the rest of the addresses to send to for example).

Tough to say without lots more info. Do you have an example malformed address?

I do know that if I send to multiple addresses and one of them no longer exists *my* smtp server will still send to the others. But, in that case, all the addresses are well formed.

Looks like it's Opera popping up a warning from the smtp server:

SMTP service unavailable [421 edge01.upcmail.net edge ESMTP server temporary not available]

plus a button to open an error console -that is empty. To me that's cryptic, as if the server were down. By the way I malformed it replacing @ with #.
The message then lands in my out box from where Opera tries to resend it at my specified intervals and now the popup is:

Recipient error [550 5.5.0 <malformedaddress#hotmail.com> domain name required]

The only way to get rid of this is to delete it from the out box, and either drop or correct the malformed address in the original message before resending.
Apparently Opera treats reply all as one message, and my smtp server blocks it. If this were standard behavior I wouldn't have received that e-mail at all.

Originally posted by bartgzn:

Looks like it's Opera popping up a warning from the smtp server:

O.K.

Originally posted by bartgzn:

plus a button to open an error console -that is empty.

When you open the console, make sure you switch the drop-down to "errors". The messages are hidden by default for some reason.

Originally posted by bartgzn:

The only way to get rid of this is to delete it from the out box, and either drop or correct the malformed address in the original message before resending.

Yeh, that makes sense.

Originally posted by bartgzn:

Apparently Opera treats reply all as one message, and my smtp server blocks it.

Yes. Opera sends a single message and the smtp server looks at the To, Cc and Bcc heads and takes care of who the message goes to. Opera doesn't send a single message for each recipient. But, that's not just Opera, other clients do that too.

Originally posted by bartgzn:

By the way I malformed it replacing @ with #.

I tested with # and get the same result as you. Since there's an error sending, it's considered fatal and the message doesn't get sent at all. There's really nothing you can do about it, except for making a wish for something (like how exactly you want the malformed address to be handled) in the wish-list forum.

Thanks for clearing that all up, guess I'll have to contact my ISP if the server's behavior can be changed; Again if all servers would react the same I wouldn't have received that mail at all.
Don't know if it is worthwhile to put this on the wish list, an error like this should be rare -the person sending me that message has already corrected the wrong address.