From David Harris:

It's stored as part of the encoded string in MercuryD.dat. There's
basically no way of getting at it outside the program's UI at this point.

 

Hello,

 I have an webapplication to configure my Mailuser and so on.

There I also have a posibility to add pop3 client requests, in the file mercuryd.dat

; Example entry
; styx.pmail.gen.nz,username,password,-,david

Now I like to add optional header information. How can I do that?

I had the idee to add this with mercury and then look in the file.. but I've

seen that the new mercury version (4.52) will encrypt the content.

Will mercury the non ecrypted version support in the future? Or is there

a posibility to encrypt this content in php?

Thanks
 

I'm working from memory here since I've not done this for some time.  You can create a mercuryd.dat with unencrypted data and it will be used but I'm not sure it does not require a "reload users" to get the system to look at the file.  Also, IIRC, the first time you manage the file in Mercury/32 and save it it will encrypt the data.

Yes, it works without a "reaload user" command, I've implemented it succesfull..

But today I added only the retrieve information like userlogin, password, host and default user.

I'd like to add also more optional headers (<tt>X-Destination-ID,x-envelope-to...)</tt>, but I don't know how

I have to add this information to the mercuryd.dat

You can't, all that goes into this file is the data required to get the mail from the host and setup the local and default users.

That said, even if you could you would have nothing to work with since the mail is being received from a POP3 mailbox you do not have access to the original SMTP headers.  Now if the owner of the POP3 mailbox is using one of the systems to add the RCPT TO: and MAIL FROM: addresses as a header in the RFC 2822 message body this would be possible, however redundant.  You can't even do this with a daemon since there is nothing to work with.

You can add headers via filtering to a mail message though.  The problem is how do you know what to put in the X-Destination-ID if it's not in the message?

ok, sorry.. I didn't mean add more header information to the downloaded message. :)

In the GUI MercuryD->add-> exists a section ("optional special header processing") to add non-standard headers, which mercury should also check

to delivering the message in the correct mailbox.

now my questions: How can I add this non-standard headers manually to the mercuryd.dat (without GUI)?

thanks :) 

Not sure, it's not in the mercuryD.dat nor in the mercury.ini that I can see.  I think this one needs to go to David.

;
; Sample MERCURYD.DAT file
; Mercury Mail Transport System,
; Copyright (c) 1993-99, David Harris, All Rights Reserved.
;
; MERCURYD.DAT is parsed by the MercuryD Distributing POP3 client to
; determine the sources from which it should obtain mail using the
; POP3 client protocol for distribution to local users.
;
; Each non-comment line in this file represents a single host/account
; combination MercuryD should contact to retrieve mail, using the
; following format:
;
;   host<,>username<,>password<,>local_user<,>default
;
;      "host"       - the domain name of the machine running the POP3
;                     server MercuryD should contact.
;      "username"   - the name MercuryD should use to login to the server
;      "password"   - the password matching "username" in plain text
;      "local_user" - The local user to whom mail downloaded from the
;                     specified account should be delivered.
;      "default"    - The user to whom mail should be delivered if no
;                     local recipients are found in a message.
;
;   Empty or blank parameters must be set to a single dash character, '-'.
;   Spaces are significant - only the ',' character is a valid delimiter.
;
;   If "local_user" is set to a single dash, MercuryD will attempt to
;   distribute the mail based on the "to:", "cc:" and "bcc:" fields in
;   each message. This is useful for sites running so-called "domain
;   mailboxes" - the first example entry below demonstrates this option.
;
;   "default" is only meaningful for domain mailbox entries, and is
;   intended to deal with problems like mailing list subscriptions,
;   where the local addressee often will not appear anywhere in the
;   message headers.
;
; Example entry
; styx.pmail.gen.nz,username,password,-,david