Also, you can turn on session logging in MercP and examine the entire conversation to see exactly what is being asked for by the client and what is provided by the server.

There are some standard template files included with Mercury, for instance failure.mer. So for example, try replacing "Content-type: Text/plain; charset=US-ASCII" with "Content-type: Text/plain; charset=utf-8".

I close this old case.

After ran Mercury couple of weeks without Spamhalter, no crashes at all. After manually compacted Spamhalter's database, few crashes per week with Spamhalter.

 Jyrki

Thanks I will try that next time he mentions it.

So apparently XAMPP has a release where they have broken the Mercury installation by failing to include the required QUEUE directory. Well, at least now we know what to tell other people that are trying to get it to work!

As usual with XAMPP it advisable to remove references to localhost if you at all plan to use the server on the Internet. 

You could create a new folder, copy over the mail and delete the old one, then rename it to the old name.

Thanks Rolf for refreshing my feeble brain.  The ~r in the UDG does indeed pick up the content of the user default reply-to address.  I now remember configuring it this way because I use MercD to POP hosted mailboxes and could not use ~8 because the local account names and hosted account names are different.

The small daemon that hides and shows various module windows in Mercury has now been updated. It hides module dialogs instead of permanently closing them. Settings can be saved so they will be applied again when Mercury is restarted.

It's available for download here:  

If there is more than one concurrent connection to a mailbox it may not be possible to delete messages. Otherwise it should be OK though.

The  main question is probably if your Internet provider allows you to use port 25 (SMTP) for external communication. Otherwise use MercuryC instead of MercuryE and relay outgoing mail though the ISP's server. Using non-default ports on a public server will not work, you will be the only one to know what port to use. 

If you don't use MercuryX for scheduling anything it's better to disable it.

Binding to 127.0.0.1 only allows traffic from the server itself, so don't do that if you want to communicate with other computers. The IP interface field should in most cases be blank. It should never contain a domain name.

Please read Mercury help (or the PDF manual) about local domains.

Well, that's a Base64 transfer encoded text (meaning: *** Dear Bhante an). There are various freeware decoders for Base64 around, try googling for it!

Sure, point the alias to a general filtering rule that copies messages to both mailboxes.

[quote user="MartinTruckenbrodt"]

Hello,

for some local e-mail addresses I have to send a auto reply.

I have done aglobal rule using the action Sending reply using a template.  Also I've done a txt file for a template.

The reply has added following lines automatically:

Message-ID:
Comment: Missing date header inserted by host server.
Date: Thu, 20 Jun 2013 10:08:05 +0200

[SOLVED]: How to prevent adding of these lines?

[SOLUTION]: I've added two blank lines on top of file.

Is it possible to use a HTM(L) file, too?[/quote]

I'm not sure exactly what you are asking.  Where do you want to use an html file?

Hello,

FYI: I closed and lost this idea.

Bye MArtin

Hello,

Bye Martin

To host your own mail server to send and receive messages you should have your own domain, and preferably a fixed public IP address. You should as well make sure that your Internet provider allows traffic on port 25 (SMTP).

Pegasus or Mercury do not by themselves provide any SMS feature. 

Hello,

I've decided to use local users insteat.

So there is no need for the filter rule now.

Bye Martin

I use the above process on my server; I have the main instance of M32 that filters all the outgoing mail.

If  the "From" header = a.com, message is processed by the main instance.

If the "From" header = b.com, message is moved to the mbox b-out, where wsmtpex gets it, and forward it to the "B" instance of M32.

If the "From" header = c.com, message is moved to the mbox c-out, where wsmtpex gets it, and forward it to the "C" instance of M32.

Unfortunately there is a couple of cons (at least, here)

1) when the msg is moved to the b-out or c-out, the "From" header is removed.

2) it seems that wsmtpex does not support multiple recipients; so, if I send an email to - say - myfriend1@gmail.com and myfriend2@gmail.com, only the last receives it, because all the other addresses are lost.

 It may be a misconfiguration, but I couldn't get rid of this.

Best regards

Filippo

[quote user="bmpan"]

Any new ideas regarding this issue? I found the following in the documentetion of another IMAP server:

[quote]

There are five pre-defined flags that may be set on each message in an IMAP folder: \Seen, \Answered, \Draft, \Deleted, and \Flagged.

An IMAP server may also optionally offer the ability to set arbitrary client-defined flags for any message.

[/quote]

Also, I heard about some email clients supporting user defined flags. I checked all the config and ini files of Mercury, but there seems no option to define custom flags. Would be useful to have that feature of message highlighting back, particular in a multi-user environment.[/quote]

As you have found, Mercury does not handle the writing of the highlighted/urgent indicator in IMAP connections.

This has been brought up before as an item on the wish list.

Also, when Mercury is restarted, the session log target filename index is reset and any existing files for the corresponding session index are appended to rather than being overwritten, hence the large files if this has been session logging continuously for some time.

I have a scheduled script that cleans out old session logs, so if I want to have the logging running for a while (or forget it is on) it doesn't fill the disk.