I'm using mercuryC to send e-mail via our ISP. I use this method
because we were having problems with e-mails to ISP's like AOL being
rejected using direct SMTP. The problem is that our ISP is rejecting
some mailings with 452 #4.5.3 Too many recipients.
Another mail server I have used has an outgoing setting of 'slow
message posting' which will break an e-mail down and send it to
individual recipients as separate e-mail, thus getting around this
issue. Is there such a setting in Mercury or could someone suggest a
way around my problem?
Try a GMail server. Get a GMail account and then use the GMail server for sending. I do not know what specific limits they have but I do know that they are not using throttling.
FWIW. the VERP processing of Mercury/32 does allow for sending mailing list mail separately to each user and that may solve your problem with the server that limits the number of addresses per single message. Also the mailing list "Fanout" option under distribution allows you to use normal processing and send multiple messages each with fewer addresses. For example if you use a fanout of ten with a list of 200 members then you will send ten messages with 20 addresses in each message. Depending on the limits of this server that may be all you need.
<blockquote><p>I'm using mercuryC to send e-mail via our ISP. I use this method
because we were having problems with e-mails to ISP's like AOL being
rejected using direct SMTP. The problem is that our ISP is rejecting
some mailings with 452 #4.5.3 Too many recipients.</p>
<p>&nbsp;Another mail server I have used has an outgoing setting of 'slow
message posting' which will break an e-mail down and send it to
individual recipients as separate e-mail, thus getting around this
issue. Is there such a setting in Mercury or could someone suggest a
way around my problem?</p></blockquote><p>Try a GMail server.&nbsp; Get a GMail account and then use the GMail server for sending.&nbsp; I do not know what specific limits they have but I do know that they are not using throttling.&nbsp; </p><p>FWIW. the VERP processing of Mercury/32 does allow for sending mailing list mail separately to each user and that may solve your problem with the server that limits the number of addresses per single message.&nbsp; Also the mailing list "Fanout" option under distribution allows you to use normal processing and send multiple messages each with fewer addresses.&nbsp; For example if you use a fanout of ten with a list of 200 members then you will send ten messages with 20 addresses in each message.&nbsp; Depending on the limits of this server that may be all you need.
</p><p>&nbsp;</p><p>&nbsp;</p><p>&nbsp;</p>