Recent changes to feature-requests

#10 Cfg:3:Log more info when an invalid entry in user.conf is found

mfg8876 — Sun, 02 Nov 2014 13:25:11 -0000

summary: Feat:3:Log more info when an invalid entry in user.conf is found --> Cfg:3:Log more info when an invalid entry in user.conf is found

#10 Feat:3:Log more info when an invalid entry in user.conf is found

mfg8876 — Sun, 02 Nov 2014 08:45:51 -0000

status: open --> closed-fixed
assigned_to: mfg8876

#10 Feat:3:Log more info when an invalid entry in user.conf is found

mfg8876 — Sun, 02 Nov 2014 08:45:23 -0000

fixed
See commit [r368].

Feat:3:Log more info when an invalid entry in user.conf is found

mfg8876 — Sun, 02 Nov 2014 08:44:09 -0000

Ticket 10 has been modified: Feat:3:Log more info when an invalid entry in user.conf is found
Edited By: mfg8876 (mfg8876)
Status updated: u'open' => u'closed-fixed'
Owner updated: None => u'mfg8876'

Feat:3:Log more info when an invalid entry in user.conf is found

mfg8876 — Sun, 02 Nov 2014 08:44:09 -0000

A little bit more specific intel on why an entry in user.conf is skipped/ignored would be nice.

Cfg:3:Log more info when an invalid entry in user.conf is found

mfg8876 — Sun, 02 Nov 2014 08:44:09 -0000

Ticket 10 has been modified: Cfg:3:Log more info when an invalid entry in user.conf is found
Edited By: mfg8876 (mfg8876)
Summary updated: u'Feat:3:Log more info when an invalid entry in user.conf is found' => u'Cfg:3:Log more info when an invalid entry in user.conf is found'

Undesired lines and sort

Anonymous — Mon, 28 Mar 2011 23:56:17 -0000

Hi there, it's Loulou.

Interested in new version, i just tested it and i just have a question :

Why there is no defined domain in realm.conf but some users defined in user.conf, by default? Indeed, i have filled realm.conf and user.conf, leaving the 2 defaults lines in users.conf, adding my users after those lines. After starting the server, one of my 3 users user was - i think - sorted before the 2 default users (mydomain.com), and not the other two. When i tested for an email delivery, error was "mailbox unavailable" and log file said "address rejected".

After deleting those lines - which seems to serve on nothing - delivery was OK and no error.

Are those lines really importants to keep them in default conf file?

Loulou.

filter email based on 'TO' destinations

mfg8876 — Thu, 24 Dec 2009 19:02:22 -0000

What we want to establish is for JES to deliver messages from domain
'mydomain.com' to the local domain ( 'mydomain.com') and relay those
destined for domain 'abc.com' but block all mails going to other
destinations. (abc.com is handled by another mailserver, so it is not
one of the 'local' domains in mail.conf)

Direct outgoing messages to a specific destination

mfg8876 — Tue, 16 Jun 2009 14:35:19 -0000

In the context of a testing framework outside the scope of the JES internal testing suite, it is desirable to have the ability to direct all outgoing messages to a specific destination.

JES 1 SpamBlocker / Attachment Stripper

Wed, 07 Jul 2004 17:37:27 -0000

When I switched my employer's system to JES, we gained
more flexibility in managing user names & email
addresses across multiple domains, and a very simple
configuration scheme. However, the prior system did
have the ability to strip out attachments based on the
file extension and offered third-party add-ons to call
our virus scanner. It also offered limited ability to
block spam.

I would like to see those kinds of capabilities arise
in JES. Something similar to this
http://sourceforge.net/projects/spamsentinel/ as an
add-on here would be great. Note that the project
mentioned is C#, and very early in the game.

The attachment stripper is a must-have, to the degree
that I'm willing to lend my pitiful Java skills to the
effort if someone who knows what they are doing will
lead the way.

Currently running JES on Windows 2000, although we are
about to experiment with Linux or one of the BSDs as well.