[xmail] Re: XMail 1.21 Pre-02
[EMAIL PROTECTED] wrote on Monday, January 03, 2005 7:01 PM: > On Mon, 3 Jan 2005, [iso-8859-1] S=3DF6nke Ruempler wrote: >=20 >> Second: Could you implement my request that bounce messages > can generate =3D > =3D3D >> an >> empty MAIL_FROM? I get sick of returning bogus bounces (~300 per >> day) =3D3D and I have to go through them because it's our Postmaster >> address.=20 >=20 > Did you ever try with this? >=20 > "PostMaster"=3D09"" Mhm, IMHO then the *real* people which reply to a bounce message with a question cannot send. And what about the mail-loop messages? They would = go into /dev/null - wouldn't they? :[ --=20 soenke - To unsubscribe from this list: send the line "unsubscribe xmail" in the body of a message to [EMAIL PROTECTED] For general help: send the line "help" in the body of a message to [EMAIL PROTECTED]
[xmail] glst
Hello, Finally, I compiled the glst modules by adding Davide's mkdep scripts and a .depend file. Then I run it by adding this line "/var/MailRoot/bin/glst" "--mfile" "@@FILE" into the filters.pre-data.tab. Then I run xmail under debug mode. I can see that the filter is triggered but it give retcode = 2. Does the filter run correctly?? Gideon So -- ::MigDal-Gad CrossNet Ltd:: ==We do the Best for Christ== Tel: 2671-7015 Fax: 3005-4526 Web: http://www.mcnet.com.hk - To unsubscribe from this list: send the line "unsubscribe xmail" in the body of a message to [EMAIL PROTECTED] For general help: send the line "help" in the body of a message to [EMAIL PROTECTED]
[xmail] R: Re: SMTP GreyListing module
That's true, I want to know how Davide will use them... I think the IPs could be checked/combined with triplets and used to avoid greylisting time outs... Dario -Messaggio originale- Da: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] conto di Tracy Inviato: lunedi 3 gennaio 2005 22.54 A: xmail@xmailserver.org Oggetto: [xmail] Re: SMTP GreyListing module At 16:40 1/3/2005, Dario wrote: >ahhh, that global DNS based GLST derived blacklist would be perfect, >but would that have an impact on legitimate e-mail? *Any* DNSBL can have an impact on legitimate email. There is no way to avoid this possibility completely without simply not using them. - To unsubscribe from this list: send the line "unsubscribe xmail" in the body of a message to [EMAIL PROTECTED] For general help: send the line "help" in the body of a message to [EMAIL PROTECTED] - To unsubscribe from this list: send the line "unsubscribe xmail" in the body of a message to [EMAIL PROTECTED] For general help: send the line "help" in the body of a message to [EMAIL PROTECTED]
[xmail] Re: SMTP GreyListing module
At 16:40 1/3/2005, Dario wrote: >ahhh, that global DNS based GLST derived blacklist would be perfect, >but would that have an impact on legitimate e-mail? *Any* DNSBL can have an impact on legitimate email. There is no way to avoid this possibility completely without simply not using them. - To unsubscribe from this list: send the line "unsubscribe xmail" in the body of a message to [EMAIL PROTECTED] For general help: send the line "help" in the body of a message to [EMAIL PROTECTED]
[xmail] Re: SMTP GreyListing module
ahhh, that global DNS based GLST derived blacklist would be perfect, but would that have an impact on legitimate e-mail? Dario -Messaggio originale- Da: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] conto di Davide Libenzi Inviato: lunedi 3 gennaio 2005 20.40 A: xmail@xmailserver.org Oggetto: [xmail] Re: R: Re: SMTP GreyListing module On Mon, 3 Jan 2005, Dario wrote: > You are right Davide, it would make senese only if next > generation of spamming software will use that trick. > > BTW, are you planning to share those lame IPs in a client/ > server environment? Am I right? I still don't do anything with them, just log them in the lame-db. They could be used to create IP blacklist automatically though, especially when shared between many GLST setups. In theory they could feed a system when those info are analyzed, and feed a DNS based GLST derived blacklist. Of course, to do that, some sort of authentication will have to be in place when accepting lame-db data. - Davide - To unsubscribe from this list: send the line "unsubscribe xmail" in the body of a message to [EMAIL PROTECTED] For general help: send the line "help" in the body of a message to [EMAIL PROTECTED] - To unsubscribe from this list: send the line "unsubscribe xmail" in the body of a message to [EMAIL PROTECTED] For general help: send the line "help" in the body of a message to [EMAIL PROTECTED]
[xmail] Re: R: Re: SMTP GreyListing module
On Mon, 3 Jan 2005, Dario wrote: > You are right Davide, it would make senese only if next > generation of spamming software will use that trick. > > BTW, are you planning to share those lame IPs in a client/ > server environment? Am I right? I still don't do anything with them, just log them in the lame-db. They could be used to create IP blacklist automatically though, especially when shared between many GLST setups. In theory they could feed a system when those info are analyzed, and feed a DNS based GLST derived blacklist. Of course, to do that, some sort of authentication will have to be in place when accepting lame-db data. - Davide - To unsubscribe from this list: send the line "unsubscribe xmail" in the body of a message to [EMAIL PROTECTED] For general help: send the line "help" in the body of a message to [EMAIL PROTECTED]
[xmail] R: Re: SMTP GreyListing module
You are right Davide, it would make senese only if next generation of spamming software will use that trick. BTW, are you planning to share those lame IPs in a client/ server environment? Am I right? Dario - To unsubscribe from this list: send the line "unsubscribe xmail" in the body of a message to [EMAIL PROTECTED] For general help: send the line "help" in the body of a message to [EMAIL PROTECTED]
[xmail] Re: Problem with Received IP Address
On Mon, 3 Jan 2005, Dan Porter wrote: > Hi All, > I am having a problem where the IP Address I specify at the command line > when starting up xmail is not the same as the IP address showing up in > mail headers under Received. > > /I'm making the #s up for simplification:/ > The servers main IP Address is 222.222.222.222 (and this is the IP > address that keeps showing up in the received header): > > Received: from 222.222.222.222 ([222.222.222.222]) > by mx.gmail.com with ESMTP id 71si194406rnc; > > I start up xmail with the command line options -PI 222.222.222.223 -SI > 222.222.222.223 (and this is the address I want to show up in the headers). > > Also, the domain *mail.mydomain.com *resolves to 222.222.222.223, and in > my server.tab I have specified "RootDomain", > "SmtpServerDomain","POP3Domain" and "HeloDomain" all to be > *mail.mydomain.com*. > > So, it is obviously causing a problem to other mail servers when they > see an email coming from mail.mydomain.com which resolves to .223, but > the IP address on the received is .222. > > Any suggestions? The -PI and -SI command line options bound *listening* interfaces to such IP:PORT combinations. They do not bound *connecting* interfaces, that are ruled by the system default routing tables. - Davide - To unsubscribe from this list: send the line "unsubscribe xmail" in the body of a message to [EMAIL PROTECTED] For general help: send the line "help" in the body of a message to [EMAIL PROTECTED]
[xmail] Re: SMTP GreyListing module
On Sun, 2 Jan 2005, Dario wrote: > Very usefull filter, thanks Davide! > > Just a few words on a possible improvement. > It would be nice to have something like the > embargo policy implemented in DCC greylist. > > Maybe I'm wrong, but it would just need the md5 > checksum algorithm of the message body, a few > new columns in the dbm and... some code... > > "DCC greylisting normally requires not only > that a triple of sender, recipient and SMTP > client IP address be familiar, but also that > a triple does not become familiar until the > same message has been presented and temporarily > embargoed or rejected. This significant difference > from other implementations prevents a spammer from > retransmitting a different message > (e.g. with different random words) > to get past greylist filtering." > > from: > http://www.rhyolite.com/anti-spam/dcc/greylist.html I took a quick look at it, and IMO does not help much. Looking at the patterns I see here in the glst-lame db, only one attempt is made in the delivery phase. On top of that, DCC requires the full message to be received, on the contrary of standard greylist implementations (like GLST) where the message is blocked at tha DATA handshake. - Davide - To unsubscribe from this list: send the line "unsubscribe xmail" in the body of a message to [EMAIL PROTECTED] For general help: send the line "help" in the body of a message to [EMAIL PROTECTED]
[xmail] Problem with Received IP Address
Hi All, I am having a problem where the IP Address I specify at the command line when starting up xmail is not the same as the IP address showing up in mail headers under Received. /I'm making the #s up for simplification:/ The servers main IP Address is 222.222.222.222 (and this is the IP address that keeps showing up in the received header): Received: from 222.222.222.222 ([222.222.222.222]) by mx.gmail.com with ESMTP id 71si194406rnc; I start up xmail with the command line options -PI 222.222.222.223 -SI 222.222.222.223 (and this is the address I want to show up in the headers). Also, the domain *mail.mydomain.com *resolves to 222.222.222.223, and in my server.tab I have specified "RootDomain", "SmtpServerDomain","POP3Domain" and "HeloDomain" all to be *mail.mydomain.com*. So, it is obviously causing a problem to other mail servers when they see an email coming from mail.mydomain.com which resolves to .223, but the IP address on the received is .222. Any suggestions? Thanks, Dan - To unsubscribe from this list: send the line "unsubscribe xmail" in the body of a message to [EMAIL PROTECTED] For general help: send the line "help" in the body of a message to [EMAIL PROTECTED]
[xmail] Re: XMail 1.21 Pre-02
On Mon, 3 Jan 2005, [iso-8859-1] S=F6nke Ruempler wrote: > Second: Could you implement my request that bounce messages can generate = =3D > an > empty MAIL_FROM? I get sick of returning bogus bounces (~300 per day) =3D > and I > have to go through them because it's our Postmaster address. Did you ever try with this? "PostMaster"=09"" - Davide - To unsubscribe from this list: send the line "unsubscribe xmail" in the body of a message to [EMAIL PROTECTED] For general help: send the line "help" in the body of a message to [EMAIL PROTECTED]
[xmail] Re: XMail 1.21 Pre-02
On Mon, 3 Jan 2005, [iso-8859-1] S=F6nke Ruempler wrote: > [EMAIL PROTECTED] wrote on Monday, December 27, 2004 9:47 PM: >=20 > > On Mon, 27 Dec 2004, Mike Harrington wrote: > >=3D20 > >> Been running nicely on my server since its release. > >=3D20 > > I plan to make a pre03 in a few days, and release 1.21 before > > Jan 15 2005. >=20 > Davide, >=20 > First: Happy new year! >=20 > Second: Could you implement my request that bounce messages can generate = =3D > an > empty MAIL_FROM? I get sick of returning bogus bounces (~300 per day) =3D > and I > have to go through them because it's our Postmaster address. I liked the "First:" better :=3D) - Davide - To unsubscribe from this list: send the line "unsubscribe xmail" in the body of a message to [EMAIL PROTECTED] For general help: send the line "help" in the body of a message to [EMAIL PROTECTED]
[xmail] Re: Error when compling glst module
On Mon, 3 Jan 2005, Gideon So wrote:
> Hello,
>
>When I try to compile the new glst module. I get the following error:
>
> # make -f Makefile.unx
>
> Makefile.unx:81: .depend: No such file or directory
> mkdep -f .depend -I. -DUNIX -DLINUX ./glst.c ./dbdump.c ./dbload.c
> make: mkdep: Command not found
> make: *** [.depend] Error 127
You need the mkdep script (see below) ...
- Davide
#!/bin/sh -
#
# $OpenBSD: mkdep.gcc.sh,v 1.13 2003/07/16 09:38:01 otto Exp $
# $NetBSD: mkdep.gcc.sh,v 1.9 1994/12/23 07:34:59 jtc Exp $
#
# Copyright (c) 1991, 1993
# The Regents of the University of California. All rights reserved.
#
# Redistribution and use in source and binary forms, with or without
# modification, are permitted provided that the following conditions
# are met:
# 1. Redistributions of source code must retain the above copyright
#notice, this list of conditions and the following disclaimer.
# 2. Redistributions in binary form must reproduce the above copyright
#notice, this list of conditions and the following disclaimer in the
#documentation and/or other materials provided with the distribution.
# 3. Neither the name of the University nor the names of its contributors
#may be used to endorse or promote products derived from this software
#without specific prior written permission.
#
# THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
# ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
# IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
# ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
# FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
# DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
# OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
# HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
# LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
# OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
# SUCH DAMAGE.
#
# @(#)mkdep.gcc.sh8.1 (Berkeley) 6/6/93
#
#
# Scan for a -o option in the arguments are record the filename given.
# This is needed, since "cc -M -o out" writes to the file "out", not to
# stdout.
#
scanfordasho() {
while [ $# != 0 ]
do case "$1" in
-o)
file="$2"; shift; shift ;;
-o*)
file="${1#-o}"; shift ;;
*)
shift ;;
esac
done
}
D=.depend # default dependency file is .depend
append=0
pflag=
while :
do case "$1" in
# -a appends to the depend file
-a)
append=1
shift ;;
# -f allows you to select a makefile name
-f)
D=$2
shift; shift ;;
# the -p flag produces "program: program.c" style dependencies
# so .o's don't get produced
-p)
pflag=p
shift ;;
*)
break ;;
esac
done
if [ $# = 0 ] ; then
echo 'usage: mkdep [-p] [-f depend_file] [cc_flags] file ...'
exit 1
fi
scanfordasho "$@"
TMP=`mktemp /tmp/mkdep.XX` || exit 1
trap 'rm -f $TMP ; trap 2 ; kill -2 $$' 1 2 3 13 15
if [ "x$file" = x ]; then
${CC:-cc} -M "$@"
else
${CC:-cc} -M "$@" && cat "$file"
fi |
if [ x$pflag = x ]; then
sed -e 's; \./; ;g' > $TMP
else
sed -e 's;\.o[ ]*:; :;' -e 's; \./; ;g' > $TMP
fi
if [ $? != 0 ]; then
echo 'mkdep: compile failed.'
rm -f $TMP
exit 1
fi
if [ $append = 1 ]; then
cat $TMP >> $D
if [ $? != 0 ]; then
echo 'mkdep: append failed.'
rm -f $TMP
exit 1
fi
else
mv -f $TMP $D
if [ $? != 0 ]; then
echo 'mkdep: rename failed.'
rm -f $TMP
exit 1
fi
fi
rm -f $TMP
exit 0
-
To unsubscribe from this list: send the line "unsubscribe xmail" in
the body of a message to [EMAIL PROTECTED]
For general help: send the line "help" in the body of a message to
[EMAIL PROTECTED]
[xmail] Re: Error when compling glst module
I had the same error on my primary but everything worked fine on my secondary. I just copied the files from the secondary and all is well. Both machines are RH 9.0 and are pratically identical, t thougth it was just a file that I had corrupted on my end. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Gideon So Sent: Monday, January 03, 2005 1:42 AM To: xmail@xmailserver.org Subject: [xmail] Error when compling glst module Hello, When I try to compile the new glst module. I get the following error: # make -f Makefile.unx Makefile.unx:81: .depend: No such file or directory mkdep -f .depend -I. -DUNIX -DLINUX ./glst.c ./dbdump.c ./dbload.c make: mkdep: Command not found make: *** [.depend] Error 127 Any hints for that??? Thanks. Gideon So -- ::MigDal-Gad CrossNet Ltd:: ==We do the Best for Christ== Tel: 2671-7015 Fax: 3005-4526 Web: http://www.mcnet.com.hk - To unsubscribe from this list: send the line "unsubscribe xmail" in the body of a message to [EMAIL PROTECTED] For general help: send the line "help" in the body of a message to [EMAIL PROTECTED] - To unsubscribe from this list: send the line "unsubscribe xmail" in the body of a message to [EMAIL PROTECTED] For general help: send the line "help" in the body of a message to [EMAIL PROTECTED]
[xmail] Clamav for Windows
Good (and FREE) AV solution to be used with XMail Win32 http://www.sosdg.org/clamav-win32/ Edinilson - ATINET-Professional Web Hosting Tel Voz: (0xx11) 4412-0876 http://www.atinet.com.br - To unsubscribe from this list: send the line "unsubscribe xmail" in the body of a message to [EMAIL PROTECTED] For general help: send the line "help" in the body of a message to [EMAIL PROTECTED]
