On Oct 25, 5:00pm, Rob MacGregor wrote:
} On 04/06/05, Nauman Habib [EMAIL PROTECTED] wrote:
}
} I setted up a Mail server 2 days ago . It is sending and receving mails with
} out any problem , but it seams that MIMEDefang is not working at all - Mail
} log return these errors :
}
}
Paul Whittney wrote:
Most likely people here read slashdot at times (or all the time ;-), but
there is an article on filtering email, with graphs, and other ideas.
http://www.acme.com/mail_filtering/
Be warned, he doesn't like perl, so I bet he's never tried MIMEdefang,
and I don't quite agree
hey,
i've made a little addition to the filter_begin code
in the mimedefang-filter script
---
background: lets say i provide a free webmail service
and i use mimedefang + spamassassin to scan outgoing
emails.
problem: people who are sending mails to hotmal.com
instade of hotmail.com or to
On Thursday 09 June 2005 11:49, dead hero wrote:
code:
sub filter_begin() {
foreach $recip (@Recipients) {
if ($recip =~ /\.+\@(.+)\/) {
$domain = $1;
@mx = mx($domain);
unless (@mx) { delete_recipient($recip); }
}
}
}
-
i was wondering if there are
--- Guido
[EMAIL PROTECTED]
wrote:
1) MX records are not required, when non-existant
the A record will be used.
are you sure about that?
i think you must have a MX record, what do you mean
'the A record', which A record? there could be lots of
them.
for exemple, i'm sending an email to
dead hero wrote:
1) MX records are not required, when non-existant
the A record will be used.
are you sure about that?
He's right. Check the RFCs.
Also, your code will block mail if there's a temporary
DNS error. You should distinguish between SERVFAIL
and NXDOMAIN status codes from the DNS
Hi All,
Tried to search for the answer to this but the
archives don't reveal the answer but I know I've read
some similar posts this year ;)
If I use Net::LDAP at the top of mimedefang-filter I
see the file descriptor WARNING message: Something in
your Perl filter appears to have opened a file
-Original Message-
From: Kevin A. McGrail
Minor nit.
If I have a zone like this:
imacompany.com86400INA1.2.3.4
imacompany.com86400INMX51.2.3.5
mx1.imacompany.com86400INA1.2.3.5
Then 1.2.3.5 is the only MX destination and
Sorry, Mark's small change is correct. I meant to type in the MX record
name but forgot and type the IP address.
imacompany.com.86400INA1.2.3.4
imacompany.com.86400INMX5mx1.imacompany.com.
mx1.imacompany.com.86400INA1.2.3.5
hey,
i've made a little addition to the filter_begin code
in the mimedefang-filter script
---snip---
code:
sub filter_begin() {
foreach $recip (@Recipients) {
if ($recip =~ /\.+\@(.+)\/) {
$domain = $1;
@mx = mx($domain);
unless (@mx) {
--On Thursday, June 09, 2005 7:03 AM -0700 Chris Masters
[EMAIL PROTECTED] wrote:
If I use Net::LDAP at the top of mimedefang-filter I
see the file descriptor WARNING message: Something in
your Perl filter appears to have opened a file
descriptor I guess Net::LDAP is doing something
Gary Funck wrote:
$ makemap -u hash access.db | grep 1.2.3.4
1.2.3.4 REJECT
Entries in the access map should be tagged, try:
Connect:1.2.3.4 REJECT
--
Mike Atkinson - [EMAIL PROTECTED]
___
Visit http://www.mimedefang.org and
-Original Message-
From: Mike Atkinson
Gary Funck wrote:
$ makemap -u hash access.db | grep 1.2.3.4
1.2.3.4 REJECT
Entries in the access map should be tagged, try:
Connect:1.2.3.4 REJECT
Maybe that's it, but I've got a gazillion IP addresses listed without
a tage
13 matches
Mail list logo
