Where is fine tool-, program can be also used to recover information from Microsoft Exchange ost files and/or convert them into Microsoft Outlook pst files,will be recovered and saved together with messages and objects from the corrupted *.pst file,program recover Outlook files and data from corrupted pst files of all Microsoft Outlook mail clients, from Microsoft Outlook 97 to Microsoft Outlook 2003. To save the recovered information as files with the *.pst extension, you should have the Microsoft Outlook 98 mail client or higher installed on your computer.

So, you're running MercuryD and MercuryE. Try to intercept the message via a global policy or filter rule, so you save a copy of each message before they get processed. Then you can later toss them into the queue (hold MercuryE first !!!!) to see if it's the list engine that causes this. I doubt that though. I'd much sooner suspect that something is causing packet/socket problems in your setup, and somehow MercuryE or MercuryD, or the loopback logic is messing things up.

If all else fails, I'd move Mercury to another machine, and use MercuryD and MercuryC, using hMailServer as the "smart host".

Nevertheless I'll see if I can't speed up my web-admin development a bit. Much of the foundation is already in place but I'm noway near a release.

Thanks for your reply FJR.

Using Outlook (2013) with multiple e-mail accounts only one account I can manage to have hierarchical folders. The other accounts, even creating a new account I cannot manage to create hierarchical folders.

How can I fix this?

 Mat 

One work around for this, if your ISP permits it, is to forward, at the ISP server, every arriving message to a second account while leaving the original message in place.  Not all ISPs offer this facility, but I seem to recall that GMail does.  You could then extract the mail through the Mercury POP process from one ISP account, while leaving the other one untouched.  I would have to check further about this but, in the GMail case, it might be better to use IMAP for your incoming connection.  I can't remember what all of the GMail options are.

If your ISP doesn't provide this type of forwarding facility, it may be possible to forward all messages from Mercury to a second account at your ISP.

 GordonM

Hi Peter,

[quote user="Peter Strömblad"]Hmm, never heard of their platform. Couldn't see If 9.2 is their latest build (the reference only to 2008 on their homepage). If 9.2 is their latest build I'd file a support case with them.[/quote]

 yes, its the latest client-version. I contacted them aready. They will give me some information next week.

Greetings

Asgard

ehh what? M/32 doesn't allow local usernames like user@domain.com

Sure is does in aliasing. Core then will deliver the mail using this full email address.  

If you use a local username like USER in an alias the X-Envelope-To: address will contain the local username USER.  If this account is auto forwarded then the local username USER shows up as the MAIL FROM: address and since it's not a full SMTP email address it is bounced.  I've asked David to change this to add the mail server domain if none exists but so far nothing has changed.

Thank you very much, I´m such a blind i****

I´ve searched Allow the use of "+" forms in addresses to carry user-specified data  for two days and couldn´t find it[*-)]

Again Thank you !!!

Ok,

 thanks to everyone who helped me.

i think i got the point.

Mark

Thanks so much Rolf. The fanout distribution is working fine.  I'll keep the VERP option in the back of my mind to try some other time.  For now, though everything is clicking away like it is supposed to!  Thanks again.

That looks like the MercuryE (end-to-end SMTP) console output, though. Your Internet provider is most likely blocking outgoing traffic on port 25. So unless you can convince them that you should be allowed to use port 25 you will need to switch to MercuryC and relay the mail through your Internet provider's mail server.

/Rolf 

NothingI've seen will cause this to happen and I've used some really lightweight WinXP workstations to process the mail.  For a number of years I user a 64K P90 XP Home to service the mail using POPFileD without any problems at all.

Well, I installed ClamWall instead of F-Prot. It's working smoothely so far - promising!

Cheers!

I change the pop3 client config for our users :

Now in local account field I enter the external email address (user1@company.com)

 Everything seems to be OK

Thank you for the ideas,

The main reason for the server side filter would be the PDA and SmartPhone users that only want to check their spam-folders when they are in office.

I think using reg-ex for building the mail adresses would be a little complicated (because of the firstname.lastname combinations)

Claudius

This is probably due to one of the odd anti-spam technique used by the receiving domain that requires a rDNS for your static IP address, though ineffective, it is still implemented by mail admins in many places.

You will need to ensure that your ip resolves to a valid DNS name  eg. mail.yourdomain.com or at least someserver.yourisp.com and not Non-existent domain when you do a nslookup.

The other possibility is that your range of IPs are within dynamic ip address pool known to ISPs and they may ban mails coming from it. In such instance, you can only send it through your ISP or contact the domain's hostmaster directly.

Thanks for your reply, David.

I confess I am not sure it happened the way I describe, but it was the only thing that made sense to me at the time.  I will investigate the whitelisted senders and see if I can figure out where it all went wrong.

[quote user="MartinB"]

Any way to block emails that are dated incorrectly ?? 

eg:

if date is earlier that 1st Jan 2008 the drop ??
I get lots of spam with dates going back years...
 [/quote]

Not at the SMTP level. You can use the Content Control and some rule like:

IF NOT HEADER "Date" MATCHES "* 2008 *" WEIGHT 100 TAG "Probably faked Date header"

but actually I wouldn't recommend it. It will probably also hit on mails without a date header, which is a RFC violation but unfortunately often the case with commercial newsletters and such. Besides, you have to remind the rule if all of a sudden at the beginning of 2009 all incoming mail is treated as spam.

Best regards,

Nico

I've not been able to recreate this.

As soon as it happens, I'll post details.

David - any plans with IMAP filtering ?? 

I still haven't solved my problem, but I've managed a workaround.

 I used a M/32 Policy to run NAV from the commandline without using VirProt (which doesn't appear to work).

 Regards.

Stephen.

I figured it out.  My wife's inbox is "wife". I created an alias "wife@mydomain.com", which is associated with a filter file, "wife.rul".

The filter file puts all the email in the "wife" inbox, and then selectively forwards emails to the BlackBerry:

# First save all email in the Pegasus inbox
Always Copy "wife"
# Now select which email get dropped
If header "S" contains "Daily Comics" Exit ""
If header "FE" contains "newsletters@news.com" Exit ""
# Anything else is forwarded to the BB
Always Forward "wife@blackberry.net"

When delivering email to "wife@mydomain.com", Mercury always uses the alias, so all email, including BCC goes through the alias. 

As Thomas suggested, I did use a list type filter for the list of senders that should not be forwarded.