>>I would say a). Why? Then you end up with 3 copies of the email.
Remember this: You have sender's server, which we can call ServerA. If recipient is yourn...@example.org and list is mailingl...@examplelist.org ServerA (sender's server) will now send the email to yourn...@example.org AND mailingl...@examplelist.org List server, should now ONLY send to list members of mailingl...@examplelist.org If List server now sends to the To: recipient aswell, you will end up with 3 copies: 1: The email that ServerA sent to you personally 2: The email that List server sent to you personally 3: The email that List server sent to you by the mailing list Thus list server should never send to any specified To: recipients, only to list recipients. *UNLESS* The list server have received the mail directly from a MUA via an authenticated session (either a session which is authenticated via a IP ACL, or username/password auth) In this case, the list server is the initial server, or ServerA in this case. OR The list server have received the mail via external means (for example, from a webscript via a pipe) Same here, then the list server is the initial server, or ServerA in this case. OR The list server is responsible (configured to receive mail for) for the To: recipient domain (in this case, example.org ). In this case, the list server will only receive 1 copy of the email from ServerA as ServerA will find out it’s the same server responsible for both recipient, and it will deliver the whole email once for both recipients. List server should now deliver 2 emails to recipient, both To: recipient and mailing list recipient. _______________________________________________ mailop mailing list mailop@mailop.org https://list.mailop.org/listinfo/mailop
