On 9/6/2012 11:39 AM, Chris Ramsden wrote:
> I quote myself, earlier in this thread.
>
> "This site:
>
>
http://kb.mozillazine.org/Limits_%28Thunderbird%29
>
> ...says:
>
> "E-mail addresses
>
> There appears to be a limit of approximately 60 addresses when
> sending messages if you enter each address separately"
If true, it's a pathetically low limit, because many a message
can arrive from more liberal ISPs with between 100 and 500 recipients,
and all of those can appear in one incoming "To:" header
(such headers are typically multi-line, however,
containing multiple addresses per line).
Now, all you have to do is "reply all,"
and you'll then have a list of exactly that same size,
which would overwhelm any measly 60-address capacity
of TB, should that really be as many as it can handle.
If you save your message being composed as a draft
and then "view source," you will see that all the addresses
are in fact combined into one saved "To:" header,
while if you resume editing, TB now splits it up again
into its "one address per line with a button" arrangement
at the top, which might be the misfortune that could
set such a low ceiling on the size of even a "reply all" list.
Even as I check this out before posting, I see another TB bug
staring me in the face -- even if I carefully delete my
"Always BCC" addresses before I save a draft,
merely opening the saved draft to resume editing
re-inserts all my "Always BCC" addresses all over again,
despite that I already removed them during previous editing.
Returning back to composing a "To:" address list,
is it not possible to copy a large "To:" list
from any other message viewed in true "source" form,
with comma-separated addresses, and paste that into
any TB address line? IIRC, TB again immediately splits that
into the "one address per line with a button" format
that persists while you are actively composing,
and if that has a limit of merely 60 addresses in total,
it's vastly too small a limit to even match what's accepted
by many ISPs, in which case just doing "reply all"
to an incoming message from a high-limit source
would overwhelm poor underpowered TB.
As to someone's remark that a single "bad address"
could completely stop the mailing of a message having
many recipients, this does happen if the account's
outgoing server finds fault at once with any address,
while TB is still connected during the initial sending.
Improper syntax of even one address, for example, will always
"kill" an outgoing "send" attempt, as will the detection
of a non-existent local addressee *if* the outgoing server
checks that situation even while receiving recipient addresses
during the interactive connection between TB and that server
upon your pressing "Send." Once a list of recipients which
your outgoing "message submission" server can not check
for other than syntax has been initially accepted, however,
any problems detected only as that server forwards mail
to destination domains will simply be reported via email,
as "non-delivery reports" mailed back to the address in the
original "From:" header, and will have no impact
upon delivery to any other original addressees.
As to ISP limits, there can be combinations of per-message limits
with per-hour or per-day limits at more sophisticated ISPs,
in which case breaking up mailings might help overcome
any underpowered TB per-message limit,
but like your bank, which keeps debiting every separate charge
against your running account balance, you can still be "throttled"
by ISPs that count your overall sending over periods of time,
thus catching even those who use more professional mailing systems
that send a separate message for every single recipient.
--