[xmail] Spamassassin and SMTP Filter
Hi, I thought about integrating SA into a XMail SMTP Filter, so that it = would be possible to reject SPAM directly. At the SMTP Stage, XMail hasn't put = it's headers into the spoolfile - IMHO SA *needs* this headers for looking up HELO/IP/etc. Now Davide could change the code that the headers are there = in the spoolfile at this stage, but I guess he doesn't want to and he has = good reasons for this. I think it's possible to build the Received header = from scratch from the INFO-DATA by my own, prepend it to the spoolfile and = pass the whole thing (without the XMail Headers) to spamc. Any thoughts? - 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: HeloDomain question
Liron Newman wrote: My current HeloDomain is set to one of my domains (The first one I had, actually). However, a reverse resolve on my IP gives something else, not that domain or a name under it. I was wondering if maybe it would be better to set my HeloDomain to what my IP resolves to, or maybe even RootDomain? (I wouldn't chnge POP3Domain because that would require people to change their settings, and it has nothing to do with it anyway) What do you think? What could be the implications of the current status, and of changing it? Does it even matter (SPAM scores maybe? I don't know..)? Thanks to all who answered, I changed my HeloDomain. :) Now I'm wondering - Should I change my RootDomain as well? What does RootDomain do, anyway?The Readme just says Indicate the primary domain for the server.. From what I saw, its function is when answering a HELO somedomain.com in an incoming SMTP session with 250 RootDomain. Is that RootDomain's only use? If so, when does it matter? - 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: Spamassassin and SMTP Filter
It is a good idea, however... Here are a few things to know about what you would like to do: 1) You could create your own Received: headers before passing the email = on to SA. No problems. Then I would suggest you strip them back off after = you get the results back from SA... 2) I suspect XMail's author doesn't write the Received: header at the post-data stage because of a couple reasons... a) Here you can get the untouched original email. b) What would you put in the for section if there were multiple recipients? (More than one RCPT TO)? 3) If you reject a SPAM after it has been sent to you, you didn't gain anything... the time and bandwidth has already been wasted. 4) Rejecting spam often means the sending server will attempt endlessly again and again even if you pass a 554 or other similar fatal error meaning that the one 40KB spam now can take up 400KB or more bandwidth = as the spammer keeps trying to resend. Personal experience tells me that you need to just accept it, score it, label it as [SPAM], and if you wish, delete it, or move it to another folder if it scores high enough (I use XMail-WAI web interface... so = spams show up in a spam box folder). When I did what you propose, my bandwidth use shot up over 10x! Now, an idea I have would be to combine the SA scoring with perhaps a greylisting? That's what I am looking at writing up right now... 1) PRE-DATA: check triplets database, temp error if in list and not = enough time has past. 2) POST-DATA: check SA score for email, if above a 5, then temp error it = and add to greylist. I like this modified form of greylisting because it allows low scored = emails to be delivered immediately (which I often want when buying things = online, retrieving lost password for websites, etc). Only high-scoring emails = get delayed. Any comments on my idea? Jason J Ellingson Sr. Web Software Developer 615.301.1682 : nashville 612.605.1132 : minneapolis www.ellingson.com [EMAIL PROTECTED] -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] = On Behalf Of S=F6nke Ruempler Sent: Tuesday, January 11, 2005 2:04 AM To: xmail@xmailserver.org Cc: Henrik Steffen; Alexander Hagenah Subject: [xmail] Spamassassin and SMTP Filter Hi, I thought about integrating SA into a XMail SMTP Filter, so that it =3D would be possible to reject SPAM directly. At the SMTP Stage, XMail hasn't put = =3D it's headers into the spoolfile - IMHO SA *needs* this headers for looking up HELO/IP/etc. Now Davide could change the code that the headers are there = =3D in the spoolfile at this stage, but I guess he doesn't want to and he has = =3D good reasons for this. I think it's possible to build the Received header = =3D from scratch from the INFO-DATA by my own, prepend it to the spoolfile and = =3D pass the whole thing (without the XMail Headers) to spamc. Any thoughts? - 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: Spamassassin and SMTP Filter
[EMAIL PROTECTED] wrote on Tuesday, January 11, 2005 2:41 PM: Hi, thx for your answer It is a good idea, however... =20 Here are a few things to know about what you would like to do: =20 1) You could create your own Received: headers before passing the email =3D on to SA. No problems. Then I would suggest you strip them back off after =3D you get the results back from SA... Yes, that is right. I'll have to strip it afterwards. 2) I suspect XMail's author doesn't write the Received: header at the post-data stage because of a couple reasons... a) Here you can get the untouched original email. b) What would you put in the for section if there were multiple recipients? (More than one RCPT TO)? Right. 3) If you reject a SPAM after it has been sent to you, you didn't gain anything... the time and bandwidth has already been wasted. Because simply deleting the message is not possible (justice and some customers), a real sender would get back a 5xx error and he knows that = his mail has'nt been read. The Problem with marking as SPAM is that = 99% of our spam-protected customers don't know anything about it and so it's besser that the don't get the spam. I want to realize it as option, if = spam is deleted or is being marked and forwarded. 4) Rejecting spam often means the sending server will attempt endlessly again and again even if you pass a 554 or other similar fatal error meaning that the one 40KB spam now can take up 400KB or more bandwidth =3D as the spammer keeps trying to resend. Nope, 5xx is permanent - the client should not try to resend it. 4xx is temporarly. Personal experience tells me that you need to just accept it, score it, label it as [SPAM], and if you wish, delete it, or move it to another folder if it scores high enough (I use XMail-WAI web interface... so =3D spams show up in a spam box folder). see above about my personal expirience. When I did what you propose, my bandwidth use shot up over 10x! mhm I use spamcop and other blacklists and the other nice features of = Xmail so that 70-80% of the incoming mail is rejected in SMTP session before = it reaches any filter ;-) Now, an idea I have would be to combine the SA scoring with perhaps a greylisting? That's what I am looking at writing up right now... I think in a few month the spammers will have a solution against = greylisting so I don't think about implementing it. 1) PRE-DATA: check triplets database, temp error if in list and not = =3D enough time has past. 2) POST-DATA: check SA score for email, if above a 5, then temp error it =3D and add to greylist. =20 I like this modified form of greylisting because it allows low scored =3D emails to be delivered immediately (which I often want when buying things =3D online, retrieving lost password for websites, etc). Only high-scoring emails =3D get delayed. SA autolearning (bayes) and auto-whitelisting is IMHO very effective and = a better solution as greylisting. - 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: Abemus Papam ...
Feel free to update that ebuild and use it however you like.
Dustin C. Hatch wrote:
Has someone created an ebuild for 1.21 yet? If not, I will create it
and submit it to gentoo's bugzilla. Kevin, is it alright if I update
the ebuild you sent me? I prefer it to the chrooted version.
Dustin C. Hatch
http://www.dchweb.com/
Davide Libenzi wrote:
1.21 it is, at the end:
http://www.xmailserver.org
* Sun Jan 9 2005 Davide Libenzi davidel@xmailserver.org
Added a fix for 64 bits porting compatibility.
Added the ability to exclude filters from execution in case of
authenticated user.
By pre-pending the filter command token with a token containing !aex,
the filters
won't be run if the user authenticated himself.
Added @@USERAUTH macro even to standard in/out filters (before it was only
defined
for SMTP ones).
Added a new NoSenderBounce variable inside the SERVER.TAB file, to enable
XMail generated bounce messages to have the empty SMTP sender ('MAIL
FROM:').
Added a new SMTP-MaxErrors variable inside the SERVER.TAB file to set
the maximum
errors allowed in a single SMTP session (default zero, unlimited).
Added a LastLoginTimeDate variable to the userstat CTRL command.
Added external aliases support in the CTRL protocol.
The MESSAGE.ID file is now automatically created, if missing.
Changed the logic used to treat domain and user MAILPROC.TAB files.
Before, a user's
MAILPROC.TAB was overriding the domain one, while now the rules are merged
together,
with domain's ones first, followed by user's ones.
The maximum mailbox size of zero is now interpreted as unlimited.
Fixed XMail's sendmail to detect non-RFC822 data and handle it correctly.
The IP:PORT addresses emission in spool files (and Received: lines) has
been changed
to the form [IP]:PORT.
Added filter logging, that is enabled with the new -Qg command line option.
Fixed an error message in the SMTP server, that was triggered by the
remote client
not using the proper syntax for the MAIL FROM: and RCPT TO: commands.
Fixed explicit routing through SMTPGW.TAB file.
Fixed a possible problem with file locking that might be triggered from
CTRL commands
cfgfileget/cfgfileset.
Added a check to avoid the CTRL server to give an error when a domain
created with
older versions of XMail does not have the domain directory inside
cmdaliases.
The SMTP server FQDN variable should be set to the value of
SmtpServerDomain, when
this is used inside the SERVER.TAB file.
- 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]
--
Scanned for viruses by ClamAV
--
Scanned for viruses by ClamAV
--
Scanned for viruses by ClamAV
--
Scanned for viruses by ClamAV
-
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: HeloDomain question
Matic wrote: I think RootDomain allows user of that domain to log in without using whole e-mail adress as their username [EMAIL PROTECTED] can login olny with user if domain.com is rootdomain AFAIK that's POP3Domain... - 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: Spamassassin and SMTP Filter
Ya I've been doing that for a while now heres the script i use and wrote for it. http://xmail.nomadcf.com/info.php?program=anti-spam -- Chris L. Franklin -- - Original Message - From: Sönke Ruempler [EMAIL PROTECTED] To: xmail@xmailserver.org Cc: Henrik Steffen [EMAIL PROTECTED]; Alexander Hagenah [EMAIL PROTECTED] Sent: Tuesday, January 11, 2005 3:04 AM Subject: [xmail] Spamassassin and SMTP Filter Hi, I thought about integrating SA into a XMail SMTP Filter, so that it = would be possible to reject SPAM directly. At the SMTP Stage, XMail hasn't put = it's headers into the spoolfile - IMHO SA *needs* this headers for looking up HELO/IP/etc. Now Davide could change the code that the headers are there = in the spoolfile at this stage, but I guess he doesn't want to and he has = good reasons for this. I think it's possible to build the Received header = from scratch from the INFO-DATA by my own, prepend it to the spoolfile and = pass the whole thing (without the XMail Headers) to spamc. Any thoughts? - 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: Abemus Papam ...
1) If I may ask, why do you prefer nonchroot over chroot ? 2) If you add a nonchrooted version to portage, will that make my server nonchrooted too if I use that ebuild to update? If it does, I guess some people will not like that (myself included) Kevin Williams schrieb: Feel free to update that ebuild and use it however you like. Dustin C. Hatch wrote: Has someone created an ebuild for 1.21 yet? If not, I will create it and submit it to gentoo's bugzilla. Kevin, is it alright if I update the ebuild you sent me? I prefer it to the chrooted version. Dustin C. Hatch http://www.dchweb.com/ Davide Libenzi wrote: 1.21 it is, at the end: http://www.xmailserver.org *snip impressive list of changes snip* - 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: Abemus Papam ...
When I introduced the XMail Server ebuild to Gentoo, I tried to achieve the same resulting install that one would have if following the Readme.html document. This way, the documentation would match one's file system. Also, since it was new to Gentoo, I thought following the documentation would be a Good Idea. I don't prefer non-chroot over chroot. I think a chroot-ed server that doesn't match the distributed documentation is a poor choice for an audience of users who likely have never used the server before. Davide specifically addresses his choice of permissions and file locations in the documentation, and I don't believe his setup is any less secure than he claims. I also don't agree that the ebuild should do the chroot for you. Most other servers in Gentoo don't do that. That is a server setup left to the skills of dedicated administrators. I wouldn't mind having two ebuilds in Gentoo, as long as it's clear which is which. The documentation would have to be changed or appended for the chroot-ed version, too. QuinoX wrote: 1) If I may ask, why do you prefer nonchroot over chroot ? 2) If you add a nonchrooted version to portage, will that make my server nonchrooted too if I use that ebuild to update? If it does, I guess some people will not like that (myself included) Kevin Williams schrieb: Feel free to update that ebuild and use it however you like. Dustin C. Hatch wrote: Has someone created an ebuild for 1.21 yet? If not, I will create it and submit it to gentoo's bugzilla. Kevin, is it alright if I update the ebuild you sent me? I prefer it to the chrooted version. Dustin C. Hatch http://www.dchweb.com/ Davide Libenzi wrote: 1.21 it is, at the end: http://www.xmailserver.org *snip impressive list of changes snip* - 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] -- Scanned for viruses by ClamAV - 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: Abemus Papam ...
Portage is not specific about what you name your ebuilds, so it would be feasible to create two ebuilds, ie xmail-1.21.ebuild and xmail_chroot-1.21.ebuild. The only foreseeable problem with this is if you don't unmerge the original chrooted version before installing the new chrooted version would be that you would have two ebuilds merged onto your system. This would be a simple problem to correct, using portage's package blocker detection. ie, emerge -p xmail_chroot with xmail previously installed would return # emerge --pretend xmail_chroot These are the packages I would merge, in order Calculating dependencies ...done! [blocks B ] mail-mta/xmail (from pkg mail-mta/xmail_chroot-1.21) [ebuild N] mail-mta/xmail_chroot-1.21 Would this be a good solution? I think it can be done, then Sergey can maintain the chroot, and Kevin or whoever wants to can maintain the standard. I do, however like the Gentoo file structure, which doesn't veer too far from the documentation, merely replacing $MAIL_ROOT = /var/MailRoot with $MAIL_ROOT = /etc/xmail. I did remove the symlink into /home/xmail as that merely confused me :D Dustin C. Hatch http://www.dchweb.com Kevin Williams wrote: When I introduced the XMail Server ebuild to Gentoo, I tried to achieve the same resulting install that one would have if following the Readme.html document. This way, the documentation would match one's file system. Also, since it was new to Gentoo, I thought following the documentation would be a Good Idea. I don't prefer non-chroot over chroot. I think a chroot-ed server that doesn't match the distributed documentation is a poor choice for an audience of users who likely have never used the server before. Davide specifically addresses his choice of permissions and file locations in the documentation, and I don't believe his setup is any less secure than he claims. I also don't agree that the ebuild should do the chroot for you. Most other servers in Gentoo don't do that. That is a server setup left to the skills of dedicated administrators. I wouldn't mind having two ebuilds in Gentoo, as long as it's clear which is which. The documentation would have to be changed or appended for the chroot-ed version, too. QuinoX wrote: 1) If I may ask, why do you prefer nonchroot over chroot ? 2) If you add a nonchrooted version to portage, will that make my server nonchrooted too if I use that ebuild to update? If it does, I guess some people will not like that (myself included) Kevin Williams schrieb: Feel free to update that ebuild and use it however you like. Dustin C. Hatch wrote: Has someone created an ebuild for 1.21 yet? If not, I will create it and submit it to gentoo's bugzilla. Kevin, is it alright if I update the ebuild you sent me? I prefer it to the chrooted version. Dustin C. Hatch http://www.dchweb.com/ Davide Libenzi wrote: 1.21 it is, at the end: http://www.xmailserver.org *snip impressive list of changes snip* - 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] -- Scanned for viruses by ClamAV - 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: Abemus Papam ...
Actually, I believe the ebuild I sent you is set up for use with CourierIMAP, because users need direct access to their maildir. A strict POP3 SMTP install, like my earlier ebuilds in Gentoo's bugzilla, were closer to the documentation. I haven't touched the ebuild in quite a while except for version bumps, so I might not remember it correctly (don't have it in front of me ATM). Sorry. I hope that doesn't mess anyone up. Dustin C. Hatch wrote: Portage is not specific about what you name your ebuilds, so it would be feasible to create two ebuilds, ie xmail-1.21.ebuild and xmail_chroot-1.21.ebuild. The only foreseeable problem with this is if you don't unmerge the original chrooted version before installing the new chrooted version would be that you would have two ebuilds merged onto your system. This would be a simple problem to correct, using portage's package blocker detection. ie, emerge -p xmail_chroot with xmail previously installed would return # emerge --pretend xmail_chroot These are the packages I would merge, in order Calculating dependencies ...done! [blocks B ] mail-mta/xmail (from pkg mail-mta/xmail_chroot-1.21) [ebuild N] mail-mta/xmail_chroot-1.21 Would this be a good solution? I think it can be done, then Sergey can maintain the chroot, and Kevin or whoever wants to can maintain the standard. I do, however like the Gentoo file structure, which doesn't veer too far from the documentation, merely replacing $MAIL_ROOT = /var/MailRoot with $MAIL_ROOT = /etc/xmail. I did remove the symlink into /home/xmail as that merely confused me :D Dustin C. Hatch http://www.dchweb.com Kevin Williams wrote: When I introduced the XMail Server ebuild to Gentoo, I tried to achieve the same resulting install that one would have if following the Readme.html document. This way, the documentation would match one's file system. Also, since it was new to Gentoo, I thought following the documentation would be a Good Idea. I don't prefer non-chroot over chroot. I think a chroot-ed server that doesn't match the distributed documentation is a poor choice for an audience of users who likely have never used the server before. Davide specifically addresses his choice of permissions and file locations in the documentation, and I don't believe his setup is any less secure than he claims. I also don't agree that the ebuild should do the chroot for you. Most other servers in Gentoo don't do that. That is a server setup left to the skills of dedicated administrators. I wouldn't mind having two ebuilds in Gentoo, as long as it's clear which is which. The documentation would have to be changed or appended for the chroot-ed version, too. QuinoX wrote: 1) If I may ask, why do you prefer nonchroot over chroot ? 2) If you add a nonchrooted version to portage, will that make my server nonchrooted too if I use that ebuild to update? If it does, I guess some people will not like that (myself included) Kevin Williams schrieb: Feel free to update that ebuild and use it however you like. Dustin C. Hatch wrote: Has someone created an ebuild for 1.21 yet? If not, I will create it and submit it to gentoo's bugzilla. Kevin, is it alright if I update the ebuild you sent me? I prefer it to the chrooted version. Dustin C. Hatch http://www.dchweb.com/ Davide Libenzi wrote: 1.21 it is, at the end: http://www.xmailserver.org *snip impressive list of changes snip* - 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] -- Scanned for viruses by ClamAV - 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] -- Scanned for viruses by ClamAV - 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] Log files format
Hello, World ! (Yes: I´ve started with 'K Ritchie' too) Can anyone tell me where to find the exact file structure of log files? Thank you. Sergio - 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] Fedora Core 3 Advice?
I'm building a Fedora box to run Xmail among other things. I want X on this machine, though I know of the security risks. Once I install XMail via RPM, the machine hangs on sendmail during startup. Also note that I have done the removing sendmail from rc.d trick to fix the boot problem, but the system is very unstable after that for some reason. The Fedora RPM manager is limited to the Fedora packages only and doesn't offer much in the way of configuration changes or 3rd party packages being installed. Worse, it won't let me remove the sendmail or spamasassin packages. Does anyone have any advice or URLs to point me into a better direction. I'm more familiar with SuSE (pre-Novell). Any help is appreciated, Bryn - 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: Fedora Core 3 Advice?
One more note: Pointers to how to add it to the Fedora service manager are also helpful. I'm happy to write some instructions for the whole process of install under Core 3 when I'm done. Davide: Is there a good way or best practices to submit it for the normal XMail documentation or should I submit it to the Fedora folks? Thanks all, Bryn - Original Message - Subject: [xmail] Fedora Core 3 Advice? Date: Tue, 11 Jan 2005 18:01:18 -0800 From: NOTA Postmaster I'm building a Fedora box to run Xmail among other things. I want X on this machine, though I know of the security risks. Once I install XMail via RPM, the machine hangs on sendmail during startup. Also note that I have done the removing sendmail from rc.d trick to fix the boot problem, but the system is very unstable after that for some reason. The Fedora RPM manager is limited to the Fedora packages only and doesn't offer much in the way of configuration changes or 3rd party packages being installed. Worse, it won't let me remove the sendmail or spamasassin packages. Does anyone have any advice or URLs to point me into a better direction. I'm more familiar with SuSE (pre-Novell). Any help is appreciated, Bryn - 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: Log files format
http://xmail.eye-catcher.com/products/XMail/LogFiles/index.asp Sergio Perrone wrote: Hello, World ! (Yes: I´ve started with 'K Ritchie' too) Can anyone tell me where to find the exact file structure of log files? Thank you. Sergio - 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: New Admin Protocol Commands
On Mon, 10 Jan 2005, Luca Giuranna wrote: it would be useful to have some admin commands to deal with messages scheduled for resend (those in the rsnd folders in the spool tree), the same way xmail has commands to deal with frozen messages. They could be rsndlist, rsndgetlog and rsndgetmsg, like the froz... equivalents. Why would we need them? I mean, message are already rescheduled for delivery. In my personal case the mail server i'm working on is part of a complex system where mail delivery is of primary importance and the system must know if a message is deferred and the reason why. By analizing xmail log files is possible to discovery if a message has not been sent, then, by looking for the frozen message, one can know that the message has bounced and why. If it is just deferred, there is no frozen message and the only way to know why is to look for the rsnd/slog pair in the spool tree. Not that this is a big problem, in fact I was able to write a small software to accomplish this, but I think that, conceptually, frozen and deferred message are both problems that a system may want to be informed about and new admin commands would make xmail more internally coherent. Of course this is just my opinion, maybe I'm the only one in the world with such needs :-) I am gonna put it in queue, with low priority, and if it does not require too much code to handle. - 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: Fedora Core 3 Advice?
On Tue, 11 Jan 2005, NOTA Postmaster wrote: I'm building a Fedora box to run Xmail among other things. I want X on this machine, though I know of the security risks. Once I install XMail via RPM, the machine hangs on sendmail during startup. Also note that I have done the removing sendmail from rc.d trick to fix the boot problem, but the system is very unstable after that for some reason. The Fedora RPM manager is limited to the Fedora packages only and doesn't offer much in the way of configuration changes or 3rd party packages being installed. Worse, it won't let me remove the sendmail or spamasassin packages. Does anyone have any advice or URLs to point me into a better direction. # find /etc/rc.d -name 'S??sendmail' | xargs rm -f # /etc/rc.d/init.d/sendmail stop Then, install XMail - 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: Fedora Core 3 Advice?
Thanks for that Davide. Now on to configuration ;) Rusty command line guy, Bryn - Original Message - Subject: [xmail] Re: Fedora Core 3 Advice? Date: Tue, 11 Jan 2005 22:35:12 -0800 (PST) From: Davide Libenzi On Tue, 11 Jan 2005, NOTA Postmaster wrote: I'm building a Fedora box to run Xmail among other things. I want X on this machine, though I know of the security risks. Once I install XMail via RPM, the machine hangs on sendmail during startup. Also note that I have done the removing sendmail from rc.d trick to fix the boot problem, but the system is very unstable after that for some reason. The Fedora RPM manager is limited to the Fedora packages only and doesn't offer much in the way of configuration changes or 3rd party packages being installed. Worse, it won't let me remove the sendmail or spamasassin packages. Does anyone have any advice or URLs to point me into a better direction. # find /etc/rc.d -name 'S??sendmail' | xargs rm -f # /etc/rc.d/init.d/sendmail stop Then, install XMail - 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]
