Byteplant Forum

Home » CleanMail Support » CleanMail Server Talk » MailEnable filters not working.....
MailEnable filters not working..... [message #1566] Thu, 09 November 2006 23:57
gtojon
Messages: 13
Registered: November 2006
Junior Member
NST & SpamAssassin does not pass the IP address of the sender to MailEnable & instead passes the IP of the server. This makes the DNS blacklists not work for the addresses that are not covered by NST. Does anybody know how to fix this?

Thanks for any help!!



Jon S.
Re: MailEnable filters not working..... [message #1567 is a reply to message #1566] Fri, 10 November 2006 06:31 Go to previous message
Heidner
Messages: 121
Registered: February 2005
Senior Member
SPamassassin also supports DNS blacklists... why not just use it.. you could increase the scores of blacklisted sites causing the mail to be rejected.
Re: MailEnable filters not working..... [message #1568 is a reply to message #1566] Fri, 10 November 2006 06:48 Go to previous message
gtojon
Messages: 13
Registered: November 2006
Junior Member
I realize that & it works very very well......except for my users that were filtered before & don't want to pay for NST. The Blacklists in MailEnable no longer work because it doesn't get the IP that was originally sending the mail. I picked up a 50 user license & it's currently running at 40 user count, but I have about 15 users that don't want to pay for the fillter & their spam has increased 10 fold becuse they are no longer filtered at all. I was expecting the filters within MailEnable to keep working somehow. I have always charged hosting for the domain & offered email for free. At $10 or less per month for hosting.....it just doesn't pay for a little guy to do this. I know I am expecting too much or my clients are too, but I am trying to stay in business & keep them happy. They liked how it was working before. Other clients were going to move elsewhere unless I implemented something. So this is where I sit. Be nice if I could use the SpamAssassin with a pickup event without killing my server!

Thanks, Jon



Jon S.
Re: MailEnable filters not working..... [message #1569 is a reply to message #1566] Sat, 11 November 2006 01:06 Go to previous message
Heidner
Messages: 121
Registered: February 2005
Senior Member
If MailEnable is using a spamassassin engine - you might be able to tell MailEnable to "trust" the NST IP and check the other IP in the routing...
Re: MailEnable filters not working..... [message #1570 is a reply to message #1569] Sat, 11 November 2006 03:21 Go to previous message
gtojon
Messages: 13
Registered: November 2006
Junior Member
The only reason I went with NST is because of the front end for SpamAssassin. The criptic notes on Windows Install with Cygwin did not work well for me.....& it just didn't work for me. If it would have worked, I'm sure I probably wouldn't need NST. Your front end does not make it avaiable without executing everytime does it??

Thanks!



Jon S.
Re: MailEnable filters not working..... [message #1571 is a reply to message #1566] Sat, 11 November 2006 07:24 Go to previous message
Heidner
Messages: 121
Registered: February 2005
Senior Member
Jon, I'm not NST support... just a user..... as are most of the other people in the forum. Techsupport identifies them as tech support.
Re: MailEnable filters not working..... [message #1572 is a reply to message #1571] Sat, 11 November 2006 14:49 Go to previous message
gtojon
Messages: 13
Registered: November 2006
Junior Member
Sorry, I do appreciate your replies & suggestions. I emailed some of these questions to support & they seem to answer the easy ones & ignore the more important ones.

Thanks again!



Jon S.
Re: MailEnable filters not working..... [message #1573 is a reply to message #1566] Sun, 12 November 2006 01:40 Go to previous message
Heidner
Messages: 121
Registered: February 2005
Senior Member
If you paste some example inbound mail headers of what you are seeing... and what you really need.. (I.E. what it looks like with NST adding the info, and what you need dropped). I might be able to write a quick & dirty filter that would delete the prepended NST info.... (no guarentees... though) The filter would be added in NST as a custom filter and would have to be the very last one in the chain of filters... again no guarentee that I can do this...
Re: MailEnable filters not working..... [message #1574 is a reply to message #1573] Sun, 12 November 2006 01:52 Go to previous message
gtojon
Messages: 13
Registered: November 2006
Junior Member
Wow....your the greatest!! Really!

Below is the header of email that doesn't get filterted & the IP of the Sender is "80.51.233..205" . It's hard to believe that Yahoo would let this happen. Let me know if there is anything else you need.....I will be here at my computer for at least 4 hours. Thanks & no hurry!!! Header below ***

Message header of Client not filtered....between the "******":
**********************************************
Received: with MailEnable Postoffice Connector; Sat, 11 Nov 2006 16:11:01 -0600
Received: from mx5.biz.mail.yahoo.com ([192.168.1.30]) by gtojon.com with MailEnable ESMTP; Sat, 11 Nov 2006 16:10:59 -0600
Received: from mx5.biz.mail.yahoo.com ([80.51.233.205])
by better2 ([192.168.1.30], envelope-sender=)
with No Spam Today! Service V2.3.5.3 50 Recipients
for 192.168.1.30; Sat, 11 Nov 2006 16:10:55 -0600
Return-Path:
Received: from 66.162.217.100 (HELO USE1.mailhostsxode.net)
by brandtlawoffice.com with esmtp ()(845)):7-2 C23))
id .8=R*3--J(//6-)P
for rbmagnus@brandtlawoffice.com; Sat, 11 Nov 2006 22:11:10 -0060
Date: Sat, 11 Nov 2006 22:11:10 -0060
From: "Lucy Queen"
X-Mailer: The Bat! (v3.5.25) UNREG / CD5BF9353B3B7091
X-Priority: 3 (Normal)
Message-ID: <961482052.87742639377724@thebat.net>
To: rbmagnus@brandtlawoffice.com
Subject: Thinking you eat too much?
MIME-Version: 1.0
Content-Type: text/plain;
charset=Windows-1252
Content-Transfer-Encoding: 8bit
X-Spam: Not detected
****************************************************



Jon S.
Re: MailEnable filters not working..... [message #1575 is a reply to message #1566] Mon, 13 November 2006 04:25 Go to previous message
Heidner
Messages: 121
Registered: February 2005
Senior Member
Okay, what is happening is MailEnable is prepending on to the e-mail the name of the host that it is seeing the mail come in from... EVEN if it is the same host. From what I can see... if I erase the NST record... MailEnable would still thing the e-mail is coming from 192.168.1.30... and you still have a problem.

At a very low level -- this is a TCP socket issue. MailEnable is picking up the source address from the socket connection... with any proxy or gateway inbetween the internet and Mailenable -- MailEnable will always see that gateway... Sad

There may be an effective work around available from MailEnable. The fully qualified (FDQN)domain name is still reported on the first line. You should request the MailEnable people if there is a way not to do a reverse IP lookup -- but instead use the fullyqualified name instead... the DNS blocklists can use the FDQN.

Or if MailEnable can check the sender on the received by 192.168.1.30 entry (your host). In effect ask if there is a way to ignore e-mail gateway entries -- and process the remaining mail routing entries.

I'm pretty sure from what I am seeing that even if I were to write a filter to delete the NST info -- you would still see something like:


Received: with MailEnable Postoffice Connector; Sat, 11 Nov 2006 16:11:01 -0600
Received: from mx5.biz.mail.yahoo.com ([192.168.1.30]) by gtojon.com with MailEnable ESMTP; Sat, 11 Nov 2006 16:10:59 -0600
Received: from 66.162.217.100 (HELO USE1.mailhostsxode.net)
by brandtlawoffice.com with esmtp ()(845)):7-2 C23))
id .8=R*3--J(//6-)P
for rbmagnus@brandtlawoffice.com; Sat, 11 Nov 2006 22:11:10 -0060

And a lookup of 192.168.1.30 would never be found in a blocklist....

The catch is the IP would still be the local host that NST is sitting on... That information is being assembled by MailEnable not NST.

FWIW, I think the syntax that MailEnable is using on the "Received:" lines (first on in the e-mail) may not be compliant with the RFC's... I could be wrong but I think the "with" atom is supposed to be preceded by other "Received:" keywords like by, from or via...



Post Edited (11-13-06 04:30)
Re: MailEnable filters not working..... [message #1576 is a reply to message #1566] Wed, 15 November 2006 05:35 Go to previous message
gtojon
Messages: 13
Registered: November 2006
Junior Member
Thanks for looking at this for me!!! I had not replied sooner because I didn't get notification when you replied.....usually I do.

Thanks, I'll pose this to ME support!



Jon S.
Previous Topic: Connect aborted sending test mail
Next Topic: RelayCountryPlugin
Goto Forum:
  


Current Time: Fri Dec 09 22:15:01 CET 2016