http://software.dolist.net/xav.asp
We use now UUDeview that works much better than munpack on MIME
decoding and support UUDeview supports the uuencoding, xxencoding,
Base64 and BinHex encoding methods, and is able to handle split-files
(which have been sent in multiple parts) as well as multiple
Have installed, tested with eicar (it failed to stop the email), and
reverted back to 22/08/2003 version. This is the last version that works on
my system.
Whatever DOLIST did after the 22/08/2003 version, it has it broken here.
The xmail debug shows Retcode=0 on the filter. So xav is either
Hi Davide,
in case of a mail loop the postmaster gets a message, but the sender not?
--
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]
On Tue, 30 Mar 2004, Sönke Ruempler wrote:
in case of a mail loop the postmaster gets a message, but the sender not?
Mail loops typically born due postmaster screw ups, so you don't want to
notify the user about this. It will be up to the postmaster to fix the
problem and re-inject the
I'm looking at extending a few of the DNS functions for things I want to
check on incoming connections and mails, and I was wondering if there's any
particular reason that NS and MX records were the only things cached
locally by Xmail? Specifically I was thinking about A and PTR records - was
On Tue, 30 Mar 2004, Tracy wrote:
I'm looking at extending a few of the DNS functions for things I want to
check on incoming connections and mails, and I was wondering if there's any
particular reason that NS and MX records were the only things cached
locally by Xmail? Specifically I was
At 13:12 3/30/2004, Davide Libenzi wrote:
I'd rather avoid the round trip time for DNS queries if I can, but if
there's some overriding reason here, I'll just go straight to the wire for
A and PTR queries
You don't need to do that. XMail uses the existing OS infrastrcture for A
and PTR
Well when i try to log-on with the control account, it just says
Network is unreachable It is running on the same box as xmail.
Dustin
On 29-Mar-04, at 6:38 PM, Xmail wrote:
Dustin,
What types of problems are you having? I have been using the xpai
interface
for a while now.
The author
On Tue, 30 Mar 2004, Tracy wrote:
FCrDNS: Take the connecting IP address, retrieve all PTR records (hopefully
only one, but possible to get more). Then take the PTR record(s) and do A
lookup on it. Compare the connecting IP address to the A records returned -
if no match, either the DNS
At 14:03 3/30/2004, Davide Libenzi wrote:
Nope. But I was thinking that XMail could have a special filter call right
before sending the response to the DATA command. A file with all the info
(IPs, sender, recipients, etc..) will be passed to the filter, that in
turn can reject by returning
On Tue, 30 Mar 2004, Tracy wrote:
At 14:03 3/30/2004, Davide Libenzi wrote:
Nope. But I was thinking that XMail could have a special filter call right
before sending the response to the DATA command. A file with all the info
(IPs, sender, recipients, etc..) will be passed to the filter,
At 14:09 3/30/2004, Tracy wrote:
At 14:03 3/30/2004, Davide Libenzi wrote:
Nope. But I was thinking that XMail could have a special filter call right
before sending the response to the DATA command. A file with all the info
(IPs, sender, recipients, etc..) will be passed to the filter, that
That would be a nice addition :)
S
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On
Behalf Of Davide Libenzi
Sent: Tuesday, March 30, 2004 2:04 PM
To: XMail mailing list
Subject: [xmail] Re: DNS and Cached DNS in Xmail
On Tue, 30 Mar 2004, Tracy wrote:
FCrDNS:
Yup Yup it would :)
- Original Message -
From: Shawn Anderson [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Tuesday, March 30, 2004 11:13 AM
Subject: [xmail] Re: DNS and Cached DNS in Xmail
That would be a nice addition :)
S
-Original Message-
From: [EMAIL PROTECTED]
+1
Dick
On Tue, 2004-03-30 at 21:03, Davide Libenzi wrote:
On Tue, 30 Mar 2004, Tracy wrote:
FCrDNS: Take the connecting IP address, retrieve all PTR records (hopefully
only one, but possible to get more). Then take the PTR record(s) and do A
lookup on it. Compare the connecting IP
Can you ping the address 127.0.0.1? Do you have the xmail ctrl protocol
bound to this address at 6017? Have you verified the settings in your xpai
config.php file? Is the server address and port in the servers array? Is
the xpai control user in your ctrlaccounts.tab file?
-Original
On Tue, 30 Mar 2004, Don Drake wrote:
Can you update the default distribution to not have 0.0.0.0[TAB]0.0.0.0
as the default value for smtprelay.tab?
It makes no sense to distribute the default configuration of the server as
an open relay. I forgot to change that file on a second
I agree also - no need to make it easy for spammers.
The doco should also state that this is a closed relay by default, so that
we don't get too many I can't relay emails.
Rob :-)
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On
Behalf Of RaveRod
Sent: Wednesday,
I also agree to close it by default so that it will force people to
understand what they are doing before opening. So long as there is a
suitable message in the docs, this should be ok.
why doesn't my xmail work is better than why am I listed in
blacklists? (after sending thousands of spam
On Wed, 31 Mar 2004, William Denniss wrote:
why doesn't my xmail work is better than why am I listed in
blacklists? (after sending thousands of spam emails) I feel.
For you maybe. It's me that I'll receive personal emails whining about
missing capabilities :-/
(note that 70% of XMail users
Are there any other mail servers that ship with an open relay? All the mail
servers I've used have closed relays and in the manual/docs/whatever they
say that to use a relay you must open it first and that doing so, you should
understand the risks.
I hazard to guess at the amount of people who
I guess I don't understand the use case of a new installation with a
closed-relay not sending email.
At least add some more verbiage to the documentation in the SMTPRELAY.TAB
mentioning an example line showing how to make it a closed relay. It's only
mentioned in one other section of the doc,
A big fat red warning message would be appropriate I think.
Not everyone realises the risks (who would find our server in a few
days anyway? I'll read the docs and secure it all up next week.)
Will.
On Wed, 2004-03-31 at 12:58, Don Drake wrote:
I guess I don't understand the use case of a new
I guess I don't understand the use case of a new installation with a
closed-relay not sending email.
At least add some more verbiage to the documentation in the SMTPRELAY.TAB
mentioning an example line showing how to make it a closed relay.
It's only
mentioned in one other section of the
Hi!
I am having a wierd situation using CustMapsList function of XMail. I have this line
CustMapsList[TAB]sbl-xbl.spamhaus.org.:0
in server.tab (real TAB instead of [TAB]). Amount of SPAM has decreased since using
this DNSBL, but not all mails from DNSBL do get blocked. I know this because I am
On Tue, 30 Mar 2004, Tim McGarvey wrote:
I have to agree. I'll admit this makes me an idiot, but my first
installation I accumulated 40,000 bounces in my postmaster inbox between
going home on the go-live date and coming in the next morning. At the very
least a note in the tab file saying
So basically I have to decide who pays. Myself being personally
annoied with those cr*p, or ppl that does not read the doc and gets
open relay. I'd better stick my the current setup, what do you think?
Davide, you should mention it in the doc like
h3 style=color: redEMPTY SMTPRELAY.TAB OR
I agree. An email server admin should now about relaying and configure
it appropiatly=20
-Oorspronkelijk bericht-
Van: Davide Libenzi [mailto:[EMAIL PROTECTED]
Verzonden: woensdag 31 maart 2004 9:02
Aan: [EMAIL PROTECTED]
Onderwerp: [xmail] Re: Default Open Relay
=20
On Tue, 30 Mar
On Wed, 31 Mar 2004, Sönke Ruempler wrote:
Davide, you should mention it in the doc like
h3 style=color: redEMPTY SMTPRELAY.TAB OR YOU HAVE AN OPEN RELAY/h3
I won't help, sadly. Ppl does not read the doc, otherwise they will be
reading the configuration section, expecially the 'THIS IS
My experience from http://xmailforum.homelinux.net tells me, that this=20
is the No.1 error. This information is simply overseen in the manual,
even
if you read it. Instead of pls configure my server, admins get tons of
bouncing SPAM when they run an open relay, which is more critical ...
I won't help, sadly. Ppl does not read the doc, otherwise they will be
reading the configuration section, expecially the 'THIS IS IMPORTANT'
thing.
Another idea: Maybe it helps if you just add 127.0.0.1/32 and 192.168.0.0/16
in the smtprelay.tab by default.
I guess most people that don't read
IMHO it would make sense to split these things off the manual into a
small
seperate IMPORTANT.txt or READ_THIS_FIRST.txt file. There is too many
info to
digest. Most people fly thru the manual, do some trial and error and
when port 25 is up they think that their server is configured properly
Good idea - also 10.0.0.0/32
--Harald
-Urspr=FCngliche Nachricht-
Von: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Im Auftrag von S=F6nke Ruempler
Gesendet: Mittwoch, 31. M=E4rz 2004 09:18
An: [EMAIL PROTECTED]
Betreff: [xmail] Re: Default Open Relay
=20
=20
I won't help, sadly.
It is in the interest of everybody to prevent any open relays. Making it
clearer in the manual might help. Installers might help. =20
-Oorspronkelijk bericht-
Van: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Namens Harald Schneider
Verzonden: woensdag 31 maart 2004 9:20
Aan: [EMAIL
On [Tue, 30.03. 23:02], Davide Libenzi wrote:
http://www.xmailserver.org/Readme.html#configuration
In particular the step that says 'THIS IS IMPORTANT'. The difference,
giving for granted that user do not read the documentation, is that if I
close the relay I will receive tons of email
Good idea - also 10.0.0.0/32
All private networks:
10.0.0.0/8
172.16.0.0/12
192.168.0.0/16
-
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]
36 matches
Mail list logo
