EDIT - I just checked and couldn't find it, maybe I read it elsewhere, but it has been documented somewhere [:)] - END EDIT
You can specify an action for each CC definition, but if you use X-CC & X-UC headers for triggers in filtering rules you will only get the result of the last CC definition.
Since it appears that you have isolated the issue to a queue phenomenon, try running each module manually (note that you may have to press the poll button twice sometimes for it to complete its rounds). Before taking the turn from MercuryD to the Mercury-core, copy the queue files to another location. If the server crashes on every occasion when you poll the core with the queue in place, initiate Thomas or someone else on the beta team here for duplication of your error.
But I did discover that the queue's QDF file is not locked at daemon call-time and can simply be edited by the daemon. Now I have a working daemon in place getting rid of the "Sender: Maiser" header.
[/quote]
You MUST NOT DO THIS! This is so much of a problem that if I find that a Daemon is doing it, I will be forced to add code to Mercury to detect and suppress loading of that daemon. Mercury DOES provide a daemon-level method of modifying the raw data files of a job, but it's not shown in the current version of the daemon toolkit. Even so, that is the only approved way of modifying the actual data fork of a job, and you must not attempt to do it "behind Mercury's back" in this way.
The real problem here is the mail program that's trying to reply to Maiser. The RFC822/2822 definition of the Sender: field is quite unambiguous - it must be used whenever the entity sending the message is not the same entity as the one shown in the "From" field - the most usual example is a secretary sending a message on behalf of her boss. It makes no sense for the reply to go to the secretary - the mail program should be sending the reply to the actual author.
I'll consider adding an option to suppress or restructure the "Sender" field in an upcoming version of Mercury, but initially, I'd be trying to find out why the mail client is doing such a bizarre thing.
Here one can find a real exploit code (not just crashing the server!). As far as I can tell, it executes shell code, but to the real malware exploitation, it's "a small step in programming, but a giant leap to hijacking the machine...".
If you want to send the mail off the mercury hosting server, the xxxxxxx.com domain cannot be in your local domains list - found under configurations/core tab localdomains
I am trying to identify attachments in incoming mail. For instance, if an incoming mail has an attachment "SAMPLE.PDF", I would like to simply add a header. So, I have the following statement in RULES.MER:
If attachment ExtnPart contains "pdf" AddHeader "SpamCheck: !PDF!"
The message is not moved / copied in filtering process. But this does not add any header as I want.
Also, the following command
if body contains ".pdf" weight 31
in content control file SPAMBUS.DAT does not generate the weightage.
[quote]Mercury will presumably blacklist the IP of the local proxy, causing itself to not receive any mail anymore for the time of the short-term blacklisting (30 minutes AFAIK).[/quote]
Good point. I'll watch out for that.
Of course, I would rather have the patch out now than wait for all the bells and whistles.
[quote user="Tons0fun"]Ok, I am indeed running a dynamic IP system using dydns to redirect all traffic to my server. Unfortunately the email relay service is a little rich for my blood, any suggestions? [/quote]
1. Set both a PTR and MX host record for this host name and try again.
Yeah, might be my avast doing that. It does pop up when I launch IE and shows Script blocker... but the software is good :).
10 minutes later: Thanks :)! I disabled scan outgoing mail, and now I can send mail :). Thank you :)!
20 minutes later: I can send, but I can't telnet into port 25 :D lol, I sent a test mail successfully, but I can't telnet... Could not open connection to the host, on port 25...
But thanks anyways, I have gotten it working now :)!
Confirmed that mx ip and not hostname that has A-records.
You can easily use: to check on any domain you have problems with. Their report is mostly accurate and very informative. DNS report in this case says: "MX is host name, not IP" which is somewhat misleading.
From what I understand the client issued a FETCH FLAGS command to get a listing of all messages in the Inbox, and this is part of the reply. There appears to be no request to download message headers or body in this log extract, though.
Do you get the same result with another email client than Outlook Express?
Yes the decision is that we do want to use our company logo in our signature. We can do it in the client but if we did it in the server it would be easier to enforce.