Not sure but I would guess that MX records for the recipient domain still points to a mailserver (presumably at the hosting company) where that domain now has been removed.

The other way to accept all messages for the domain is to check "Accept mail for invalid local addresses" in MercuryS configuration. If the recipient doesn't exist the message will then be forwarded to the postmaster account, and a notification will be sent to the sender.

The problem with accepting all mail is of course that one is likely to receive a ton of spam addressed to non-existent accounts. Unless that can be contained it's best to stop nondelivery notifications (by removing or renaming the template file failure.mer).

Only having a domain mailbox in the local domains list is somewhat less orthodox but works as well as long as there is no conflicting definition for the domain.

The client is an iPhone.  I'll have this user dig into his configuration settings to see if he can identify where it is coming from.

In Mercury 4.7x  a "Sender" field was added to every E-Mail, that was sent from  the Mercury listserver.
This meant that always "Maiser in order of ..." has been displayed in each email, but allowed a clear identification to avoid multiple processing.

In Mercury 4.8, this field is not set and we need for our policies (scripts) another option now.
Could we use the field "X-listname" and delete them after processing? How does it affect if we delete this field during the processing of e-mail?

Operation:
We use the Mercury listserver as our project server. Each list corresponds to a construction project.
Just our part of the communication is done via the server, which is why our users have to know who the email originally get even.
We use the Policy CMD scripts with Find and especially Sed to modify the e-mails and allow this. 

Thanks, Torsten

[quote user="J_Aarni"]You can also use special names in Mercury log files to re-create them regularly.[/quote]

Jyrki has a very useful point and is what I do. This way its easy to delete or archive old logs. I usually zip up my logs from the previous month. Having 10's of GB of old log files is not really an issue when pretty much your minimum hard drive is 500GB, although I haven't found a need to look back over stuff.

accept mail for invalid local addresses was already unticked. so far everything looks good now, lots of connection refusals from the same IPs :) genuine register requests are working properly and mail is being sent perfectly. the mail server is under far less stress now. CPU usage is next to nothing and memory usage is very low too. I will keep an eye on it over the next couple of days. I really need to understand more about how this mercury mail server works.

thanks for your support guys, I am very grateful for your help. thanks

Brian

Thank you for your comment - I think you may have somewhat 'inadvertantly' opened my eyes to this! 

I have been using a single primary mailbox  into which all the email arrives. Mercury D polls this single mailbox and then dsitributes to local users based on the domain name prefix.

I have now created separate mailboxes - one for each user on the name hosting server and updated Mercury D to download from each mailbox - the duplicate message problem now appears to be solved! I love simple solutions. 

Thanks for the  light-bulb moment.

lol i had the same Problem probing 2 hours to fix this Problem :D

i had no delivery file tamplate in the config so it always crashed but now we are happy :) 

FYI With Mercury 4.8 & Win7 I just set my server to large fonts (125% scaling) and the dialogs have auto-scaled and are fine.

[quote user="Brian Fluet"]Have since discovered that the recipient address the original message was incorrect.  Subsequent messages have been delivered.  What an annoyance to have the delivery failure notice reference greylisting when the problem is an invalid address.
[/quote]

Haha - at least it was easily sorted out :)

Rolf,

Thanks very much, that fixed the problem!

Hi Andre,

We are using Mercury in connection with Pmail. But when accessing remotely from home we are using Roundcube as well. I have tried to create a subfolder in an already available folder - and it works. Also after closing RoundCube and re-opening my account with Pmail, the new subfolder appears.

Cheers

Joerg

edit: of course, also via RoundCube you are able to create new subfolders only within an empty parent folder. As long as any mails are already stored in the parent folder, RoundCube will return an error message when trying to create a new subfolder.

the website i have was just a basic website written in php and html from the web with no registration functionality at all. i downloaded from github a registration script that contained several files and a mysql db. it all works fine and it used to work ok with mandrill which was a free mail relay service but they started charging for the service so i thought maybe it was better to use the inbuilyt mercury mail since that was what it was there for.

i wanted one account for example (a private email for myself) and i wanted another email account to handle sending confirmation/register emails when someone registers on the site or if they forget a login password it can send them an email with their details. It is really not going to be used for anything complex at all just mostly handling registration stuff only. 

It's working now.  Thanks Jim!

Edit: To clarify, the expression filter Subject: [[]Spam]* works.  

Rolf, sorry - my question was not precise enough ;-(

what I want to know is, if these in 0.91 and 0.92 included functions (look down) are still included in your latest version 1.1.2.74 and if they are "ever on" because in 0.91 and 0.92 you have to activate it with a "SmtpEvent = smtpevt.dll; 1" in the DAEMON.INI but NOW with your latest version 1.1.2.74 there are already a lot of numbers after the smtpevt.dll; " SmtpEvent = smtpevt.dll; 0111121"

look (part of your readme-file included in 1.1.2.74): 

"Version 0.9.1 added a check for missing Date header and bulk mail. Date is a required header according to the SMTP RFCs. If there is no Date header and the recipient is an invalid local address the connection will be terminated. If the message has a Precedence: Bulk header and bad recipient the message is received but immediately discarded. Authenticated connections will always be allowed, though.
In version 0.9.2 the ability to block messages with a bad local sender address was added. If a MAIL FROM command with an address that belongs to a local domain is issued the daemon will check if there actually is such a mailbox in Mercury. If not, the connection will be terminated and log entries created. Note that this check will not be performed for domain mailboxes.

To activate this function the line in DAEMON.INI will need an extra parameter, and should look like this:
SmtpEvent = smtpevt.dll; 1 "

I hope you understand what I mean :-)

Also I have running an old Mercury/32 3.32 for testing around, what is the latest SMTPEVT.dll or RCPTEVT.dll which I can use for 3.32 and do you have a download link for this latest version, please? 

Thank's a lot in advance.

Regards, Michael. 

This should be possible to suppress using "outgoing rules" - define one that matches <> as sender and a part of the message text and then deletes such messages.

I had been having the following problems with Mercury:

1. All the problems with IMAP on Android and Apple clients not disconnecting as described in detail by Gusg, above.
2. Problem with Thunderbird IMAP client: when opening an email with attachments Thunderbird fetches and displays only the body of the email and waits for the user to open an attachment before fetching it from the server. Intermittently, when fetching an attachment Thunderbird would report that "the server has reported the attachment is empty". Closing and restarting Thunderbird would allow the user to fetch the attachment from the same email. The problem was that either Mercury or Thunderbird had "lost its place". I tried running Mercury with logging enabled to diagnose the problem, but, because it was so intermittent, I would end up with gigabytes of useless log files. Pegasus does not have this problem because it fetches the whole message including the attachments, whether you want to open the attachments or not.
   
3. These problems may be solved by Mercury V5 with a new file

   system that allows one file per message so locking of whole "folders"

   will no longer be necessary. However, on March 31, 2011 David Harris

   announced that "We hope to release V5 sometime in 2011", and this

   was already mid 2015. It had become clear to me that the "one man band"

   development model of Mercury and Pegasus was no longer sustainable.
   

4. My server was running Windows XP and upgrading the OS required buying new hardware.

I solved all of these problems: I bought a Raspberry Pi, installed Postfix as the mail server and PopFile for mail filtering (I even copied its database from the PC the the Raspberry), ported the PopFile daemon I wrote many years ago for Mercury, copied all my users email folder structure to the new server, copied all their emails and then shut down Mercury. My Raspberry Pi server has not needed rebooting in 9 months.

Mercury was a great program. It deserves better support than David Harris all by himself has been able to provide and, in my opinion, he needs to find a development model that allows him to involve other programmers and still feel comfortable keeping control of his "children". Perhaps something similar to what Linus Torvalds does with the Linux kernel might satisfy David too?

I encountered this exact issue several years ago but was unable to solve it.

One of our staff was using an iPhone to connect via IMAP to Mercury and the lck file was not being removed even when the IMAP connection was closed by exiting the mail program on the phone.

I posted on Apple's forums about this but never received a reply. It's really poor that they continue to exercise so little control over their mail program :(

Hello Rolf,

Thank you for the suggestion, it was related to the TCP/IP timeout. I started at 90 seconds and changed to 120 which has resolved this issue. I have been dealing with it for a long time and decided to ask, glad I did. Thank you.

Stephen 

Thank you, Rolf