I don't have any concern about Pegasus Mail being capable of using an 1800 entry distribution list but I have a concern that Pair Networks may not respond kindly to it. Their Resource Usage policy says:
"User may not... Send out mail to more than 25 addresses in one batch, whether sequentially or in parallel. Such batches must “sleep” for at least three seconds between each delivery attempt. Please consider using our pairList service for such mailings."
https://policy.pair.com/hosting/usage-policies/resource-usage.html
An unknown to me is how "batch" is defined. When Pegasus Mail sends to a distribution list, the transaction log shows one message transmitted. It contains a To: address of the distribution list. Obviously the list of recipients is being passed to the SMTP server within what we see as one message so the question is whether Pair Networks will reject it if there are more than 25 recipients. This might be worth an inquiry to their customer service.
Thinking about this further, could you send to a distribution list that contained 75 other distributions lists, each with 24 entries? I don't know. I'm just thinking out loud.
It is a shame that they are deprecating their pairList service. It looks like it could have been a good way to go.
I don't have any concern about Pegasus Mail being capable of using an 1800 entry distribution list but I have a concern that Pair Networks may not respond kindly to it. Their Resource Usage policy says:
"User may not... Send out mail to more than 25 addresses in one batch, whether sequentially or in parallel. Such batches must “sleep” for at least three seconds between each delivery attempt. Please consider using our pairList service for such mailings."
https://policy.pair.com/hosting/usage-policies/resource-usage.html
An unknown to me is how "batch" is defined. When Pegasus Mail sends to a distribution list, the transaction log shows one message transmitted. It contains a To: address of the distribution list. Obviously the list of recipients is being passed to the SMTP server within what we see as one message so the question is whether Pair Networks will reject it if there are more than 25 recipients. This might be worth an inquiry to their customer service.
Thinking about this further, could you send to a distribution list that contained 75 other distributions lists, each with 24 entries? I don't know. I'm just thinking out loud.
It is a shame that they are deprecating their pairList service. It looks like it could have been a good way to go.