hMailServer IssueTracker

Display defect

ID
215
Short summary Mail not delivered to MIME recipients
Created 2009-05-16 21:43:59
Created by mhomden
Status Resolved
Priority 2 - High
Quick link

Applies to
Found in 5.1.1 build 341
Resolved in 5.2 build 349

Problem
I have just upgraded from a 4.4.3 version as the domain signatures were not being appended, but upon installing the latest 5.1.1. version I have found that all mail is being delivered into the catch-all account and not to the MIME recipients. I have restored back to the 4.4.3 version and all is OK.

Please advise.

Thanks

Marc

Issue steps

By martin, 2009-05-17 12:22:52

I just tetsted this in 5.1.1 but it worked just fine for me.

I'm guessing there is something else wrong which triggers the error in your installation, but since you didn't mention anything about your set up it's hard to say what that may be.

For example, are the MIME recipients in a local domain?


By mhomden, 2009-05-17 12:37:59

OK so the config it exactly the same in the 4.4.3 version as I ran an upgrade, basically we have a .btconnect.com address and everything to *.owndomain.com forwards to this address, I then use the external account settings, in the catch-all account to pick up via POP3 and have set the deliver to MIME recipients option, but all I see in the logs is the 'APPLICATION' entry stating that it has been delivered to this catch-all account, as said this exact same setup works in the 4.4.3 version as I have now downgraded and restored a backup and all is fine.


By martin, 2009-05-17 12:42:33

You forgot to answer my question.

Are the MIME recipients in a local domain?
Is btconnect.com a domain you have added to your hMailServer installation?


By mhomden, 2009-05-17 12:46:26

The MIME recipients are in the .owndomain.com
No I have only added our .owndomain.com


By martin, 2009-05-17 12:57:23

So do you have a route with the name btconnect.com?



By mhomden, 2009-05-17 13:00:02

No as everything is 'seen' as .owndomain.com so this is the only route I have


By martin, 2009-05-17 13:06:43

So you have a domain named owndomain.com and a route with the same name?


By mhomden, 2009-05-17 13:40:42

yes that's correct


By martin, 2009-05-17 14:23:48

Then it seems like you relied on a bug error in hMailServer 4.x.

When hMailServer has downloaded messages from external accounts, it does not deliver these to external recipients. This behavior is as-designed, since doing this could cause message looping.

I will add an option to v5.2 which allows you to tell hMailServer that if the recipient is found in a route, it should deliver to it.


By mhomden, 2009-05-17 14:45:43

That would be great as the 5.x versions have other bug fixes to the one I'm running and also more functionality, and I would not want to move away from hMailServer as it's one of the best apps. I have downloaded and certainly over performs. In addition I have not found a better solution to achieving what I want from my setup without using hMailServer, I now have an enterprise looking solution for the end users at a fraction of the cost!

When do you think the amended v5.2 will be available and ready to test?

Thanks for the quick response and the fix.

Marc


By martin, 2009-05-17 14:55:37

Probably an alpha in a few days.


By mhomden, 2009-05-17 14:58:39

OK Great, can you keep me posted via this issue?


By martin, 2009-05-18 21:23:46

Yes, you'll receive a notice when it's fixed.


By Wisi, 2009-05-28 09:15:17

hello, please notice me, too. I will test if this fix also solves my problem posted in http://www.hmailserver.com/devnet/?page=issuetracker_display&issueid=217.


By martin, 2009-06-12 14:20:55

This issue is fixed in 5.2. It's available as alpha on the download page. A beta will probably soon be available. The alpha isn't recommended for production usage.


You must be logged on to add a step. Log on now.