[quote user="Brian Fluet"]You say that your MercuryD retrieves two messages from each mailbox which is different from mine which only retrieves one message from each mailbox.  It then delivers to the To: AND to the CC: of the message.  This is the problem that the MSGIDS.MER fixed. Perhaps this is just a matter of semantics.  I am looking at messages retrieved from each mailbox (one) whereas you are looking at messages delivered from each mailbox (two, possibly more if the To and/or CC contain multiple local recipients). [/quote]

I think you are right. Mercury-D retrieves only one mail but because there is no direct local user designated, Mercury checks which local user or users mostly match. Therefore it checks the synonym.mer, too. The mail contains a To: and a Cc: section where both recipients are available as local users. And that's why it delivers to both local mailboxes.

And the same game when connecting to the second ISP mailbox.

On the other hand, when designating a local user for each ISP mailbox in Mercury-D, Mercury knows the local user where the mail has to be delivered to and does not check for any other possible users. That could be the reason for that behaviour.

Thanks for the hint, Brian 

Hi guys,

We are experiencing following Mercury behaviour when handling mails coming from the internet which are addressed to a local user and in cc to an alias PUBLIC. Mercury-D is always retrieving two mails (one for the local user and another for the Alias PUBLIC:) when connecting to one ISP user mailbox.

Firstly our configuration:

- Different local users, where Mercury-D is retrieving their mails from single ISP mailboxes and delivering them to the local Pmail boxes

- MSGIDS.MER in place for each user for suppressing duplicated mails (works fine so far)

- Mercury-D is additionally retrieving mails from an ISP mailbox where no local user is set for. Instead of a local user we have established a public alias in form:

  public@domain.com    PUBLIC:d:\path_to_folder\public.MAI      (This works fine, too. Mercury is delivering those mails to public folder)

In case a mail is addressed to user1@damain.com, it will be delivered to that local user1. In case a mail is addressed to public@domain.com, it will be delivered to our public folder only.

But now we are talking about a mail addressed to user1@domain.com and in cc to public@domain.com. Mercury-D is firstly connecting to the ISP mailbox user1@domain.com and is retrieving two (!) mails, one addressed to user1@domain.com and another for public@domain.com. Next, Mercury-D is connecting to the ISP mailbox of public@domain.com and is again retrieving two (!) mails, one addressed to user1@domain.com and another for public@domain.com.

Now two mails are being delivered to local user1 mailbox where one mail is being suppressed (MSGIDS.MER in place) and again two mails are being delivered to the public folder defined in the PUBLIC: alias. But the public alias has no local Pmail user account where I could place another MSGIDS.MER. Finally user1 obtains only one mail but in the public folder two identical mails are being dropped.

The message suppression of duplicated mails for public folders is one aspect of the issue. But because public folders are quite difficult and have another general behaviour than standard local mail accounts, I'm not wondering about.

But why Mercury-D is retrieving mails twice for one ISP user account although this mail is addressed in cc to another recipient?

Cheers

Joerg

Hi Jorge,

I think the behaviour you are seeing is as expected if I understand it correctly.  If a message is addressed to user1@domain.com and cc'd to public@domain.com then your mail host is delivering the message to each mailbox.  Mercury then retrieves each message from those mailboxes and delivers them locally following the To: and CC: content.  The duplicate gets deleted from the user1 mailbox as expected but no such capability for the public folder so you end up with a duplicate.

The part I am a little confused by is this statement:

Mercury-D is firstly connecting to the ISP
mailbox user1@domain.com and is retrieving two (!) mails, one addressed to
user1@domain.com and another for public@domain.com. Next, Mercury-D is
connecting to the ISP mailbox of public@domain.com and is again retrieving
two (!) mails, one addressed to user1@domain.com and another for
public@domain.com.

Can you somehow see two messages being retrieved by MercuryD from each mailbox or could it be one downloaded message from each mailbox; each being delivered to the two local mailboxes?

This is a nice brain exercise but unfortunately nothing comes to mind that would help you suppress the duplicate hitting the public folder.

[quote user="Brian Fluet"]

Can you somehow see two messages being retrieved by MercuryD from each mailbox or could it be one downloaded message from each mailbox; each being delivered to the two local mailboxes?

[/quote]

Exactly this is the crazy thing. When observing the state window of Mercury-D during the connection process to each single ISP mailbox, I see that two messages are being retrieved from both mailboxes. When connecting to user1 it retrieves a mail for user1@domain.com AND for public@domain.com. And when connecting to the mailbox of public it retrieves again two mails, addressed to user1@domain.com AND public@domain.com.

BTW, this behaviour is shown only in case one of the recipients is public@domain.com. For other users added in cc (without an recipient "public@domain.com") Mercury-D is retrieving only one mail for each user Mercury-D is connected to.

It seems Mercury-D knows in advance that mails addressed to public@domain.com (with local alias PUBLIC:) has to be handled different from other ordinary user mails. And when connecting to user1 mailbox it recognizes an additional cc entry to a local PUBLIC:-alias and takes it also immediately although not destined for user1.

We have also other aliases (non PUBLIC:) in place where ISP mailboxes (without a directly connected local user) are being forwarded to certain local user mailboxes. An it works without those behaviour when using different cc recipients.

[quote user="Joerg"]Exactly this is the crazy thing. When observing the state window of Mercury-D during the connection process to each single ISP mailbox, I see that two messages are being retrieved from both mailboxes. When connecting to user1 it retrieves a mail for user1@domain.com AND for public@domain.com. And when connecting to the mailbox of public it retrieves again two mails, addressed to user1@domain.com AND public@domain.com.

BTW, this behaviour is shown only in case one of the recipients is public@domain.com. For other users added in cc (without an recipient "public@domain.com") Mercury-D is retrieving only one mail for each user Mercury-D is connected to.[/quote]

Hi Brian,

In the meantime I have experienced that odd behaviour also for all other users (irrespective of PUBLIC or not), means when an email has both a "To" and a "CC" address, Mercury-D is retrieving always two mails for the user1 and two mails for user2 (cc user). I see this in the Mercury-D state window when connecting to the single ISP mailboxes. Of course, after retrieving those 4 mails, Mercury immediately deletes the duplicated mails due to the MSGIDS.MER so that each user is getting only one mail in the end. But I would like to understand why Mercury-D is retrieving always two mails for each user.

Presently I have set up Mercury as follows:

- different single local user accounts where the local account names based on the user's initials only (only two characters)

- synonym.mer in place where the user's official internet e-mail address is assigned to a local account

- the "Local User" box in Mercury-D itself left blank

- Mercury-D is connecting to the single ISP email accounts, is retrieving the mails and is delivering them to the local user account

- additional aliases only for one special address and for our special PUBLIC Alias in place

I know, that you have nearly the same configuration. Could you kindly check the behaviour of your Mercury-D when retrieving mails with a cc to another local user inside?

Greetings

Joerg

Hi Joerg,

You are correct in that we have almost identical setups so for my test I sent a message from a gmail account to user1@mydomain.com with a cc of user2@mydomain.com.  The MercuryD window showed the following as it retrieved from each mailbox:

1 message successfully retrieved
1 message successfully delivered to 'user1@mydomain.com'
1 message successfully delivered to 'user2@mydomain.com'

Obviously I don't see the 2 messages you describe, just MercuryD unnecessarily acting on the cc.  Like you, I have MSGIDS.MER in place to delete the duplicates.

Hi Brian,

You wrote that Mercury-D is retrieving 2 messages for each user, means when connecting to mailbox of user1 it retrieves two mails (for user1 and user2) and when connecting to mailbox of user2 it retrieves again 2 messages (for user1 and user2).

After that state messages in Mercury-D the Mercury Core Process State Window is showing:

Date/Time Job1: from: sender@domain.com (non-local)

to: user1 (local)

to: user2(local)

Date/Time Job2: from sender@domain.com

to: user1 (duplicate of previously-deliverd message, suppressed)

to: user2 (duplicate of previously-deliverd message, suppressed)

Is this the normal behaviour of Mercury? In past I took for granted that Mercury-D is retrieving only that (one) mail which is intended for the just connected user's mailbox. Dont understand why Mercury is retrieving the cc message simultaneously and not later when connecting to user2 mailbox.

edit:

Now I found the mistake. When a local user name is added in Mercury-D settings "Local User" box, Mercury-D is retrieving only that one mail which is directly intended for the user just connected to. After that, when connecting to user2 mailbox Mercury-D is retrieving only the "cc mail". And finally Mercury Core Process is making one job for mail of user1 and another single job for mail delivering to user2. That's the right behaviour which I remember to.

I remember we have removed the Local User from Mercury-D settings to avoid the wrong sender's address for autoreplies of Peg. Before removing the local user name, senders email address read localuser@domain.com instead of firstname.lastname@domain.com - do you remember?

Now you could choose the lesser of the two evils.  :-)

Cheers

Joerg

[quote user="Joerg"]I remember we have removed the Local User from Mercury-D settings to avoid the wrong sender's address for autoreplies of Peg. Before removing the local user name, senders email address read localuser@domain.com instead of firstname.lastname@domain.com - do you remember?.[/quote]

I was trying to remember that part when posting earlier.  You have just refreshed my memory.

Edit:   The memory has become clearer... With a local user name specified, Mercury does nothing but deliver to that mailbox but by removing the local user name we allowed Mercury to determine local delivery which is why it delivers to all local recipients of the message.  

You say that your MercuryD retrieves two messages from each mailbox which is different from mine which only retrieves one message from each mailbox.  It then delivers to the To: AND to the CC: of the message.  This is the problem that the MSGIDS.MER fixed. Perhaps this is just a matter of semantics.  I am looking at messages retrieved from each mailbox (one) whereas you are looking at messages delivered from each mailbox (two, possibly more if the To and/or CC contain multiple local recipients).

[quote user="Joerg"]Now you could choose the lesser of the two evils.  :-)[/quote]

I don't see what we are doing now as an evil.  The wrong senders address in autoreplies definitely was.  I'm happy with how things are working but I don't want to ever have to try to figure out how we got here.