Printable Version of Topic
Click here to view this topic in its original format
XMail Forum > Documentation and Knowledge Base > Read this, if you use XMAIL < 1.20 !


Posted by: hschneider May 31 2004, 06:26 AM
QUOTE

1.19 will be probably remembered as one of the shortest release ever.
After having plugged my leak-checker, XMail was crashing. Well, it turned
out that there was a leak plus a possible use-after-free bug. Both were in
a non really common path, so they were really hard to find. Nevertheless
XMail was crashing after 30-60 minutes in my machines, so my $64000
question is: why the heck valgrind did not catch them?
(I will be making 1.20 asap)

1.20 release files are available here:

http://www.xmailserver.org

This fixed the possible memory leak and the use-after-free bug:

http://www.xmailserver.org/ChangeLog.html#may_30__2004_v_1_20

I definitely recommend to update to 1.20


- Davide

-------------------------------------------------------

Implemented the ``filter'' command for custom mail processing (MAILPROC.TAB, cmdaliases and custom domains).

If ``RemoveSpoolErrors'' is set inside the SERVER.TAB file, messages are never frozen. Before there was a special case (delivery failure and delivery notification failure) that could have lead to frozen messages.

Made ``aliasdomainadd'' to check for the existence of the alias domain (and reject the command if existing).

Introduced a new environment variable recognized by XMail (XMAIL_PID_DIR), to let the user to specify a custom PID file directory (this is for Unix ports only).

Implemented ability to stop custom mail processing upon certain exit codes from external commands execution.

The SPAMMERS.TAB check is now bypassable (see doc for details).

'ATTENTION': Changed the ``aliasdomainlist'' syntax and output format (see doc for details).

Made (on Unix setups) the PID file name to be dependent on the daemon file name.

Implemeted a domain-wise MAILPROC.TAB and extended its ``redirect'' and ``lredirect'' commands to support account specific (USER@DOMAIN) and domain targets (DOMAIN).

Implemented SMTP filters to allow users to reject the SMTP session before and after the remote client data has been received.


Posted by: hschneider May 31 2004, 07:02 AM
Upgrade as usually:

- Stop XMail
- Replace all inside MailRoot/bin
- Start XMail

If you need SMTP level filtering, create these additional files inside MailRoot:
filters.pre-data.tab
filters.post-data.tab

Posted by: hschneider Jun 2 2004, 08:11 PM
IMPORTANT NOTE
According to very rare but random crashes or high mem usage on Unix/Linux systems, upgrading to 1.20 is urgently recommended. Since the codebase is the same, this is also true for all Win32 platforms. Version 1.20 fixes some mem leaks of all previous releases.

If your system is affected or if you experienced the "LD_ASSUME_KERNEL problem", please read this note and follow these instructions:

QUOTE

On Tue, 1 Jun 2004, Harald Schneider wrote:

> These reports are spread over the XMail Forum:
> http://xmailforum.homelinux.net/
>
> Crashes happen with .rpm and self built installations.
> Setting this variable is always the cure.
>
> The latest one happened with 1.20:
> http://xmailforum.homelinux.net/index.php?showtopic=1753

Pls, tell them to:

# export XMAIL_DEBUG=1
# make -f Makefile.lnx clean
# make -f Makefile.lnx
# cp bin/XMail $MAIL_ROOT/bin
# ulimit -c 50000
# $MAIL_ROOT/bin/XMail -Md ...

When the crash happens, they should have core files in /. Let them run:

# gdb -c /core.???? $MAIL_ROOT/bin/XMail
> bt full
> q

And send me the report. Tel them to save the core file and the XMail
binary.



- Davide


------

On Tue, 1 Jun 2004, Harald Schneider wrote:

> OK - thanks!

Also, please tell them to use 1.20



- Davide



Please post your coredump reports to davidel@xmailserver.org.

Posted by: vegetto34 Jun 3 2004, 06:09 AM
Any reason out there that tells me I need to upgrade from 1.18?

Posted by: hschneider Jun 3 2004, 06:56 AM
Memory leaks that are closed in 1.20.

Posted by: hschneider Jun 3 2004, 07:47 AM
QUOTE

Davide, et. all.

There appears to be a bug with the "AliasDomainList" command.  When an alias
domain wildcard is added to an aliasdomainlist command, the domain wildcard
is completely ignored.

Example 1:

aliasdomainlist [tab] mydomain.com

will return all alias domains for mydomain.com as it should.  However...

Example 2:

aliasdomainlist [tab] mydomain.com [tab] *

will return a full list of alias domains for all domains.


Will be fixed in the next release.

Posted by: FixFaier Jun 6 2004, 06:38 PM
What's about IMAP-Implementation? unsure.gif

Posted by: hschneider Jun 6 2004, 07:19 PM
Davide is working on the 2.0 branch in parallel. Not release date give, yet.

Posted by: FixFaier Jun 6 2004, 08:10 PM
Is there some release date for an ALPHA/BETA?

Posted by: hschneider Jun 6 2004, 08:12 PM
Sorry ... none. Davide keeps these things secretly ... ph34r.gif

Posted by: FixFaier Oct 1 2004, 03:40 AM
QUOTE (FixFaier @ Jun 6 2004, 06:38 PM)
What's about IMAP-Implementation? unsure.gif

same question
Are there some news? conf.gif

Posted by: atomant Oct 1 2004, 06:59 AM
Still in development. confused1.gif

Posted by: vegetto34 Nov 19 2004, 01:16 AM
It's been 6 months now, and I just wanted to see if this program still has life? I know releases can't be made every month, but there hasn't been a peep of news since 1.20.

Posted by: hschneider Nov 21 2004, 06:43 PM
Davide is working on a 2nd release branch as well: XMail 2.0 which includes IMAP. So there will only be a 1.2x release when bugs are discovered.

Powered by Invision Power Board (http://www.invisionboard.com)
© Invision Power Services (http://www.invisionpower.com)