Is it possible to have multiple instances of Mercury running on different machines, all accessing the same outbound queue?
No it is not, you will send multiple messages if you try this. You can split and use two versions of Mercury/32 and have one doing the sending and the other doing the receiving. This second version would be looking at the same queue directory but would only be running MercuryC or MercuryE.
We have several really large e-mail lists and want to set up another
machine to handle outbound mail for these lists. Our concern is that
the core of the 'secondary' machine will pick up a message that was
meant for the list and not be able to process it since it doesn't have
access to the list.
You can setup the second server to only process the mail for the list by having the first server forward any list mail to the mailing list on the second server. You would create an alias pointing to the second sever via a user@[<IP address>] address form where the server name would be [<IP address>] so it would go to maiser. For example, you create a list called "large_list" on the second server running on IP address 192.168.1.2. You alias mail to large_list@mydomain.com to large_list@[192.168.1.2]. Now mercury core sees the mail come in for the list, creates and outbound task and ends it to the second server. The second server sees the match for the server name and so passes it off to maiser. The second server now sends out the mail.
This can also be done via a domain accont and MercuryD on the second server to pull the mail from the MercuryP server.
<blockquote>Is it possible to have multiple instances of Mercury running on different machines, all accessing the same outbound queue?</blockquote><p>No it is not, you will send multiple messages if you try this.&nbsp; You can split and use two versions of Mercury/32 and have one doing the sending and the other doing the receiving.&nbsp; This second version would be looking at the same queue directory but would only be running MercuryC or MercuryE.</p><blockquote><p>&nbsp;We have several really large e-mail lists and want to set up another
machine to handle outbound mail for these lists. Our concern is that
the core of the 'secondary' machine will pick up a message that was
meant for the list and not be able to process it since it doesn't have
access to the list.</p></blockquote><p>You can setup the second server to only process the mail for the list by having the first server forward any list mail to the mailing list on the second server.&nbsp; You would create an alias pointing to the second sever via a user@[&lt;IP address&gt;] address form where the server name would be [&lt;IP address&gt;] so it would go to maiser.&nbsp; For example, you create a list called "large_list" on the second server running on IP address 192.168.1.2.&nbsp; You alias mail to large_list@mydomain.com to large_list@[192.168.1.2].&nbsp; Now mercury core sees the mail come in for the list, creates and outbound task and ends it to the second server.&nbsp; The second server sees the match for the server name and so passes it off to maiser.&nbsp; The second server now sends out the mail.</p><p>This can also be done via a domain accont and MercuryD on the second server to pull the mail from the MercuryP server.
</p>
