Aha - thanks for that.

I have to confess that I am completely in the dark about this.

I have 4 'Move' rules set up. They move messages with specific email addresses to designated accounts. I have looked at all the accounts and none of them contain the eBay message.

I'm happy to leave this as I'm not getting anywhere with it and I simply printed the message that was required and gave it to the person who requested it. However, I don't know what I'll do if someone outside our orgainisation requests a message which is also killed.

The good thing is learning about the Log to concole option - that may come in handy the future.

Thank you for all your help.

Hello

I have just seen a strange thing happen. I needed to find a message from eBay that had been received by one of our members of staff. When the message was originally received Mercury delivered it as it should. However, when I tried to forward it to another internal account Mercury did not deliver it. The console showed    * Job killed by filtering rule.

Anyone know why Mercury will happily deliver the message but not forward it?

Thanks

You should know.

You wrote the filtering rule that killed it :)

[quote user="dilberts_left_nut"]

You should know.

You wrote the filtering rule that killed it :)

[/quote]

Seriously? And how did I do that?

The first thing I did was check the filtering rules and there are no rules that 'kill' a delivery. Nothing is deleted. We do not use Spamhalter or any other module that inspects messages and processes them based on content.

Seriously, if you can help I'd appreciate it.

Thanks

I've just looked at TRANSFLT.MER under SMTP. This is the only thing I can think of that may affect it:

H, "*192.156.225.44*", R, "554 Get out of here, you worthless scumbag."
R, "*honeypot@aphrodite.pmail.gen.nz*", RS, "554 Fraudulent RCPT rejected."
S, "*viagra*", D, "'Viagra' encountered in subject line - connection dropped."
S, "*vicodin*", R, "554 'Vicodin' encountered in subject line - message refused."
H, "[EHeh][EHeh]LO +[0-9]+.[0-9]+.[0-9]+.[0-9]*", R, "554 Invalid HELO format"

S, "/c*CONGRATULATIONS*WON*", BS, "554 Possibly Nigerian 419 Variant - please change and re-send."
# S, "*for job*", BS, "554 Possibly employment spam - please change and re-send."

But nothing jumps out.

[quote user="Greenman"]The first thing I did was check the filtering rules and there are no rules that 'kill' a delivery. Nothing is deleted.[/quote]

This message will also be shown if your filter 'moves' a message or otherwise takes it out of the normal delivery stream.

[quote user="Greenman"]

I've just looked at TRANSFLT.MER under SMTP. 

[/quote]

That's the filter rules for the SMTP transaction, which would show up in the MercuryS log. Check global filtering rules for things that appear in the core log!

/Rolf 

Folks

Thanks, but as I said I have checked the filtering rules. The only rules that are set up copy, forward or move messages to specific accounts, either local or extrernal. The triggers for the copy/forward actions are the email addresses of local users and the move actions are triggered by two tech support addresses, and they are moved to my email account.

I don't understand why the message was originally delivered to the destination account without any problems when it was received from eBay, but that when I tried to forward it, Mercury 'killed' it.

When I tried to replicate it just now, forwarding it to my email account nothing appeared in Mercury's console, and the message was not delivered.

Thanks again for your help.

You can put entries in your filter rules that output the reason to the System Messages - makes the bug hunt a bit easier in these types of situations.

It WILL be one of your rules that did it, so the only way to resolve it is to very carefully examine each rule that MOVES a message, along with the source of the forwarded message.

There is obviously an unintended match to one of them.

Thanks

I have had a look at the filters and cannot see how to add an entry so that a reason is displayed in System Messages. Under the Core Module config dialog, system message reporting level is set to 5 and the number of messages to store is 100. As I am unable to find an entry for the * Job killed... this morning should I increase the number of messages to keep? (What are these mesages?)

Our usage is fairly low in the grand scheme of things, and Mercury processes about 500 messages per day. If I set the number of messages to keep to 600 will this over-burden Mercury? The only messages displayed in the System Messages Window at present are IMAP connection notifications which all consist of *Date, time FOLDER: User 'mailboxname', mailbox closed and unlocked*.

You just set a test with an action of Log to Console (or such - I haven't got it in front of me) with a relevant message.

My rules are mostly set that each test 'calls a Label', performs some Always actions then either returns or exits, so it is easy to add an Always trigger with a Log action to say which Label has been called, and hence which trigger has been hit.

It's always bugged me a bit that System Messages are only in memory and not logged to disk.

I have mine set to 1000 and don't notice any issues with that at all.