Thomas,

Amazing, thanks, it's up and running .... and working already [:D] Thanks for all your help,

Kindest regards

MrPix (Paul )

Hi,

I have spent the past 4 hours reading various reponses on this topic and yet still can't actually find an answer that works.

I have Mercury32 4.52 and have multiple domains running for my household/family and another for a support group that I run voluntarily (not for profit). I will use sanititised addresses for simplicity

The system announces itself as smtp.dom_x.com and I don't want to change this.

I have a mailing list working for dom_y, but I cannot seem to get the from address working, it always comes from postmaster@dom_x.com

I have used a full address for the Title and checked the box 'is a full address' next to it as follows: Update <update@dom_y.com>

I have created an alias for update@dom_y.com to user@dom_y.com

Please can you assist me in getting the welcome, confirmation and the actual update file when a moderator posts, to reflect the From address to be update@dom_y.com rather than the default it is picking up from the mercury.ini.

Thanks a lot, this product rocks and I would not be without it :)

MrPix (Paul) 

Not sure what to tell you, I think I am missing something in your list setup.  Mail will be coming from maiser@<Internet name for this system> in all cases since that this the name of the mailing list server.  The From: address in my mailing lists is the sender of the mail, the To: address is what I've entered in the lists.mer as the list address.  For example, here is one of my lists on the server tstephenson.com which also supports the domain account novell-tstephenson.com.  .  If I send mail to NovellTest@novell-tstephenson.com it finds an alias NovellTest@tstephenson.com so it gets sent to maiser for action instead of the domain account.  The mail is then processed by maiser and goes out with the original senders address in the From: field, and the "Title" in the To: field.  Now this server does show up in the sender field as maiser@tstephenson,com since that is the address of the server sending the mail.

NovellTest
   File:             c:\mercury\mercury\novell.mlf
   Title:            NovellTest@novell-tstephenson.com
   Title_is_address: Y
   Welcome:          Standard
   Farewell:         Standard
   Restricted:       Y
   Enumerate:        N
   Reply_to_list:    N
   Public:           N
   Confirm_subs:     N
   Mod_redirect:     N
   Password_Posting: N
   P_Password_File:  N
   Prefixing:        0
   S_Password_File:  N
   VERP_mode:        0
   VERP_maxerrs:     0
   VERP_flags:       0
   VERP_filename:    
   List_ID:          112
   Def_Password:     
   Auto_Password:    N

Here's the headers of the message I got from the list.

    From:    "Thomas Stephenson Ubuntu" <ubuntu@ubunto-tstephenson.com>
    To:    NovellTest@novell-tstephenson.com
    Subject:    Testing
    Reply to:    ubuntu@ubunto-tstephenson.com
    Date:    Sun, 08 Jun 2008 10:36:36 -0700
    X-Mailer:    Pegasus Mail for Windows (4.50 VC15) (via Mercury/32 v4.61)
    Comments:    Originally To: novelltest@novell-tstephenson.com
    Message-id    <1536560593.3002.1212921408@tstephenson.com>
    Sender:    Maiser@tstephenson.com
    X-Text-Class:    good
    X-POPFile-Link:    http://192.168.1.2:8080/jump_to_message?view=4947

FWIW, I can send these email addresses and domains to the list without causing any further problems since the spammers get these faster than i can create them.  ;-(  Thank goodness for Spamhalter and POPFileD.

Hi, Thanks for your reply, I can see differences, but not sure if they would impact anything at all.

Here is my lists.mer

update
   File:             m:\mercury\lists\update.mlf
   Title:            update@dom_y.com
   Title_is_address: Y
   Welcome:          m:\mercury\dom_y\welcome.mer
   Farewell:         Standard
   Moderator:       admin@dom_y.com
   Moderated:        Y
   Enumerate:        N
   Reply_to_list:    Y
   Anonymous:        T
   Public:           Y
   List_Headers:     1
   List_Signature:   m:\mercury\dom_y\ttsig.mer
   Concealed:        Y
   Confirm_subs:     N
   CS_Template:      m:\mercury\dom_y\update.mer
   Mod_redirect:     Y
   Password_Posting: N
   P_Password_File:  N
   Prefixing:        1
   Prefix_string:    Update Mailing List -
   No_stripping:     Y
   S_Password_File:  N
   VERP_mode:        0
   VERP_maxerrs:     0
   VERP_flags:       0
   VERP_filename:   
   List_ID:          100
   Def_Password:  

Header information of  a subscription welcome message:

Received: from spooler by smtp.dom_x.com (Mercury/32 v4.52); 9 Jun 2008 08:47:27 +0100
X-Envelope-To: paul@dom_x.com
From: postmaster@smtp.dom_x.com
To: paul@dom_x.com
Subject: Subscription information
Date: Mon, 9 Jun 2008 08:47:16 +0100
MIME-Version: 1.0
Content-type: Text/plain; charset=US-ASCII

I subscibed using a local account to subscribe, but get the same if I use a free internet provided accounts too (like Hotmail, yuk)

If you can shed any light ony it I would appreciate it greatly.

Kindest regards

MrPix (Paul) 

Looks like you are running an anonymous list and so you are sending from the server. Also all subscription are going to be coming from the domain name of the server. 

Since the server can only have a single server name you get the name you have assigned when you named the system.  The only way to handle something like this it to run the other domain on a different Mercury/32 installation.  The primary installation would put all mail for the second domain into a domain account.  The secondary server would pull this mail via MercuryD and deliver it to the users and maiser.  The mailing list would be running on the second system and so maiser would handle it and then send the mail out with the domain name assigned to the second system. 

Both of these Mercury/32 installations can be running on the same computer.

Hi Thomas,

 It looks like the second option with the dual install is the way to go.... I'll have a go at implementing it [:)]... if you have any quick pointers on hot to do this, that would be really cool.

 Thanks for all your time so far and keep up the good work with these amazing products.

Kindest regards
MrPix (Paul)

1.  Install Mercury/32 to c:\Mercury.  The Internet name for this system will be Domain1.com.  When creating the domains create a domain account for the domain2.  This setup will use all the protocols that you need to use for domain1. The domain account will point to a local user name like domain2.  dm=domain2  :  domain2.com

2.  Install Mercury/32 to Mercdom2.  The "Internet name for this system" will be domain2.com.  When creating the protocols you need MercuryC and MercuryD and if you are going to have a separate userbase then you'll probably need MercuryI and/or MercuryP.  MercuryC will point at MercuryS of the primary installation which will handle all outbound mail.  MercuryD will download mail via POP3 from the DOMAIN2 user on the primary system.  You will use the X-Envelope-To: header exclusively to deliver the mail and so the username is blank and the default user is the postmaster account username on the second system.

Now mail sent to user@domain2.com is received via MercuryS  on the primary system.  Core sees the domain of the email address and puts the mail into the DOMAIN2 user account with the original RCPT TO: address in the X-Envelope-To: header. 

Mail is downloaded by MercuryD, sees the X-Envelope-To: email address and passes this to the queue as a MG*.QCF/QDF file pair. 

Core processes the queue files and any email message containing a address matching the local domain is then processed by core by first checking if there is an alias.  If not it checks is to see if it is to postmaster or maiser, then it checks to see if it's a mailing list address and finally it checks to see if there is a local user by that name. 

If the mail it to a mailing list then it's transferred to maiser for processing.

This is pretty much what I do with the domains tstephenson.com, novell-tstephenson.com and ubunto-tstephenson.com that are all pointed to the same IP address.  Each of these domains have their own userbase and mailing lists.  In this case though each of these are running on a separate system running Netware and Linux.