The good news is that your ini file looks overall quite good. The bad news is that sending SMTP mail over the Internet requires port 25. If you can't convince your ISP to allow you to use port 25 you should switch from MercuryE to MercuryC and relay through their SMTP server.

In MercuryS configuration change server port to 25 (and set 587 as alternate if you plan to use that for message submission). Change port forwarding from your Internet firewall/router accordingly, and you should be able to receive incoming mail.

Note that the MX records for the domain points to a different IP address:

 Name=ezish.com

    Type=MX, Class=1, TTL=86400 (1 Day), RDLENGTH=10

    Preference=21, Mail Exchange=mail2.ezish.com

- Name=ezish.com

    Type=MX, Class=1, TTL=86400 (1 Day), RDLENGTH=9

    Preference=10, Mail Exchange=mail.ezish.com

Additional Records Section:

- Name=mail2.ezish.com

    Type=A, Class=1, TTL=86400 (1 Day), RDLENGTH=4

    IP Address=174.37.88.145

- Name=mail.ezish.com

    Type=A, Class=1, TTL=86400 (1 Day), RDLENGTH=4

    IP Address=174.37.88.145

/Rolf 

Thanks, Sailor21 and Rolf. I really was writing rubbish there. As you say, it's my mail client which is sending the traffic with the incorrect EHLO, nothing to do with Mercury.It has also 'spontaneously' (probably due to a reboot for an unconnected reason) fixed itself.

The client, incidentally, is Thunderbird. I'm not sure where the EHLO is set; can't find it in Thunderbird or Windows.

I did have 127.0.0.1 in hosts, but Sailor's post set me thinking, and in Thunderbird I've now replaced the domain name for Mercury with 127.0.0.1. My intent is that traffic will no longer go via the router, and it is in fact much faster.

 As suggested, thanks, I have whitelisted 127.0.0.1 and my local subnet.

[quote user="Rolf Lindby"]
As you already noticed there is no built-in option to remove MIME parts with HTML coding for mailing list messages. It would certainly be possible to create a policy or daemon to do that, though. Maybe someone already did?[/quote]
That's what I'm hoping; but I know of no such animal.  Is there a "central repository" or similar for Merc add-ons that I could search?

[quote]Rejecting certain attachments during the SMTP session is a bit tricky as the entire message is sent at once. All data is already received when it's decoded and split into MIME parts.[/quote]
Yes, I am aware of that, which is why I'm only looking at this in the context of messages destined for redistribution by the mailing list.  I would then make an exception to my already-existing Global Filtering Rule which (currently) bounces any message with HTML content.

Frankly, I'd like to get rid of that Rule altogether.  Several years ago I lobbied here for expanding the Transaction-Level Filtering function to at least permit testing all the headers, if not the full message (including the body), before having to make the decision to accept or reject; but AFAIK, nothing ever came of that.  Now that "backscatter" is even more unacceptable than it was then, perhaps David will take another look at that idea.

I can't say where the line with the IP address and the asterisks comes from, but it's not added by Mercury.

/Rolf 

> I would like to know how to add the "smtp" address (cant get anything to

resolve) info into the php webpage
> so that my mail server will send the

email.

Depends on the PHP mailer and your going to have to someone else about that.  Most PHP mailers use mail() and that can be set to connect to the IP address of the host running Mercury.  Mercury must have MercuryS loaded and connection control set so that only authorized users can relay mail.  The PHP mailer must use some sort of SMTP authentication to relay the mail off MercuryS. 

There is no separate log for this, but there should be a line in the MercuryS log when an IP address is blacklisted.

/Rolf

Hello,

 to answer myself - to use 'Only authenticated SMTP connections may relay mail' was the solution for this.

Unclear to me was the exact meaning of 'relaying mail' in this context. I can send mail to external recipients, and I can receive mail from external senders. But if somebody fakes a local address, then he must be authenticated, which he will not be. Mail will be rejected. 

If the spammer does not fake, then he will be filtered by SpamCop and the local SpamHalter.

I hope this is correct now - seems to work.

jupiter11

Thank you Mr. Stephenson for your reply. Always learning...[:)]

I checked old list messages and Mercury has been adding a Sender header since at least 2004. So if the on behalf text has started to appear recently it's probably because of some change in the mail client software.

There is no setting for including or not including the Sender header, but you could perhaps rename Maiser to ListServer or something similar if that would make more sense. Other than that it would probably be possible to create a daemon to remove Sender headers from list messages.

/Rolf 

Got everything working. Will donate $5 to David next week if I get time.

Really? It shouldn't have let me install it their then... Oh bloody hell this software is truly becoming pathetic. I'm moving on.. Thanks guys.

There is a removal form here:

http://barracudacentral.org/rbl/removal-request

Make sure MercuryS is set to use strict relaying restrictions before removing.

/Rolf

Ok, I actually take that last post back...

It works to an extent.

So far it only works with Yahoo and other normal email providers, however i tried using "mynumber@vtext.com" and it keeps giving me connection error.

 I configured mercury on my local system. However, when I try to send mail it get struck in 'pending' mode.

Answer Section:
    guerrillamailblock.com, A, 184.154.136.50
    guerrillamailblock.com, MX, 0, guerrillamailblock.com
    guerrillamailblock.com, NS, ns2.jobboardhosting.com
    guerrillamailblock.com, NS, ns1.jobboardhosting.com

This is a valid host with a valid MX record.  The first thing that comes to mind is that you are trying to use MercuryE to send the mail and you do not have a valid fixed IP address and registered host name.  The other very good possibility is that your ISP is blocking port 25.  Convert to MercuryC and use your ISPs SMTP host as a relay host.

Hey guys, thanks for the reply.

What I did was copy the MAIL, LOGS and SESSIONS folder over to the new installation directory, and just reconfigured everything manually (as there may be new settings in the newer version).

Everything is tip top. Thank you. :)

[quote user="dilberts_left_nut"]

Maybe I'm missing what you are trying to achieve.

How often would the rule need to be modified?

I would either modify the source template and regenerate the rules, or use something like the following to replace the rule in each .rul file.

for %a in (*.rul) do copy /y %a temp && cat temp | sed "s/oldstring/newstring/" > %a

This uses 'cat' (probably inappropriately, but I'm fuzzy on the sed syntax ;)) & 'sed' from Gnu tools for windows, but there may be a (nastier?) way to do it with native tools.

[/quote]

It's for a high school, I'll have many rules whose 'root' won't be modified ('root' is for me the top of the rule where is the filtering process), the only thing that will be modified is the forward addresses, but it will be completely renewed once a year. That's why I would have prefer to have all this filtering process (same for all rules: check if the sender is allowed) in a separate rule that could be ran from within the main rule, if I want to modify the filtering process I'd just have to modify one rule.

BTW I won't do it via  batch but vbscript.

Regards

Hi,

 I'd like to configure ClamWall to ban e-mails with ZIP files that contain EXE files (or other dangerous file types).

Any tips on how to do that?  Or (if not possible with ClamWall) block them with Mercury filtering rules?

Thanks

Ron

Please note Thomas' recommendation to change the password to something that hasn't been published on the Internet! Otherwise the server will soon be relaying lots of spam and become blacklisted.

/Rolf

[quote user="Thomas R. Stephenson"]

If 'user' (local address 'user@mydomain.me') has an alias on

'user@outside.you' and receives a mail whose to: field was only 'user'

it is not redirected to the alias address.

How could I change

this? I've a lot of aliases and I would prefer to have a setting on

Mercury saying: if there is no domain name in the To: field then add

'@default.domain' and check the aliases.

Since an alias test is a string match using the e-mail address in it's simplest form the only way I can see to do this is to setup the alias user == user@outside.you.  [/quote]

If there is no solution within Mercury that's what I'm going to do, a script to add 'user  == user@outside.you' when there is a line 'user@mydomain.me == user@outside.you' and modify the way I process the datas when a user creates his/her own alias.

[quote user="Thomas R. Stephenson"]

If you are using a system address book though you might be able to setup the user "USER" with an e-mail address USER@mydomain.me so when a user used this e-mail address is would be resolved in the address book to a full e-mail address. 

 [/quote]

But not all my users are in an AB (too many users, too difficult to script it when I create/remove a user), and there is not only PM which generates emails, our copying machines send some also...

Thanks for your help

The From header in the autoreply message will be the address the original message was sent to. Mercury won't attempt to normalize it in any way.

If you want to control this in some special way you can use a templated autoreply file, which will allow you to specify headers yourself. Have a look in Mercury help for more information about this.

/Rolf