<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Recent changes to feature-requests</title><link>https://sourceforge.net/p/jamm/feature-requests/</link><description>Recent changes to feature-requests</description><atom:link href="https://sourceforge.net/p/jamm/feature-requests/feed.rss" rel="self"/><language>en</language><lastBuildDate>Tue, 18 May 2004 11:02:10 -0000</lastBuildDate><atom:link href="https://sourceforge.net/p/jamm/feature-requests/feed.rss" rel="self" type="application/rss+xml"/><item><title>multi page view SITE ADMINISTRATION</title><link>https://sourceforge.net/p/jamm/feature-requests/7/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;if domains number &amp;gt; 10&lt;br /&gt;
it could be useful show domain for letter&lt;/p&gt;
&lt;p&gt;A - B - C - D -E - F ...&lt;/p&gt;
&lt;p&gt;unlinked letter without domain&lt;/p&gt;&lt;/div&gt;</description><pubDate>Tue, 18 May 2004 11:02:10 -0000</pubDate><guid>https://sourceforge.net9f7930fa0f76bffa465cf7de020f7ae3a81a5d1c</guid></item><item><title>out of office message with forward option</title><link>https://sourceforge.net/p/jamm/feature-requests/6/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;Option to let the user set his own out of office reply.&lt;br /&gt;
and then forward the e-mail to another account that &lt;br /&gt;
you can specify&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Anonymous</dc:creator><pubDate>Thu, 29 Jan 2004 01:09:39 -0000</pubDate><guid>https://sourceforge.net236cb09a81d01d9e08658818b981c8c2fa8eaf86</guid></item><item><title>Quota for maildir and domains</title><link>https://sourceforge.net/p/jamm/feature-requests/5/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;A must-have for big envs is the hability to say how&lt;br /&gt;
much accounts and/or space a domain can have. One admin&lt;br /&gt;
could set a max of 20 accounts and 200MB for a domain.&lt;br /&gt;
It's domain admin will distribute those 200MB on at&lt;br /&gt;
mmost 20 account, say:&lt;br /&gt;
one account has 50MB;&lt;br /&gt;
other has 20 MB&lt;br /&gt;
three accounts has 10MB each&lt;br /&gt;
one account has 100MB&lt;br /&gt;
no more accounts possible, max of 200MB reached.&lt;/p&gt;
&lt;p&gt;Thanks and regards.&lt;/p&gt;
&lt;p&gt;--&lt;br /&gt;
Marcio Merlone&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Marcio Merlone</dc:creator><pubDate>Thu, 10 Jul 2003 12:39:54 -0000</pubDate><guid>https://sourceforge.net0b98ea5f2a4bda7ce3574046bd206391d8915059</guid></item><item><title>Get ready for maildrop</title><link>https://sourceforge.net/p/jamm/feature-requests/4/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;Maildrop requires both full maildir and homedir path.&lt;br /&gt;
Since .mailfilter is stored on user's homedir, one&lt;br /&gt;
could set homedir on same as maildir.&lt;br /&gt;
When ceating one account using jamm, you always get&lt;br /&gt;
homedir as &amp;amp;quot;/home/vmail/domains&amp;amp;quot; for all users and&lt;br /&gt;
maildir as relative path of this like domain/account/.&lt;br /&gt;
To maildrop use, both should be&lt;br /&gt;
/home/vmail/domains/domain/account/.&lt;br /&gt;
Would be also nice a chence to configure&lt;br /&gt;
/home/vmail/domains somewhere to use another path.&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Marcio Merlone</dc:creator><pubDate>Tue, 08 Jul 2003 12:23:42 -0000</pubDate><guid>https://sourceforge.net829ea045a6e57a05b6c79eb65f3ae78e02f96761</guid></item><item><title>Hashed Directory stucture for mail storage</title><link>https://sourceforge.net/p/jamm/feature-requests/3/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;How about a hashed directory structure? For example&lt;/p&gt;
&lt;p&gt;/domain.com/u/s/user&lt;/p&gt;
&lt;p&gt;this would scale much better. &lt;/p&gt;
&lt;p&gt;Ken McKittrick&lt;br /&gt;
Network Engineer&lt;br /&gt;
USADatanet&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Anonymous</dc:creator><pubDate>Thu, 06 Feb 2003 16:16:21 -0000</pubDate><guid>https://sourceforge.net8848f53fdf6d21faf68241031e8cd81c0a15d2be</guid></item><item><title>Add the possibility of custom 'username'</title><link>https://sourceforge.net/p/jamm/feature-requests/2/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;Your project is really *GREAT*. I've tried it and I'm &lt;br /&gt;
Impressed. Really. And I'd like to migrate to it with &lt;br /&gt;
postfix all my current qmail-ldap servers. &lt;/p&gt;
&lt;p&gt;BUT I've got a problem: I've lots of legacy accounts &lt;br /&gt;
which use different &amp;amp;quot;username&amp;amp;quot; for login than the &amp;amp;quot;email&amp;amp;quot; &lt;br /&gt;
(for example, for accessing the &lt;br /&gt;
mailbox &amp;amp;quot;jaja@jaja.com&amp;amp;quot;, you gotta login with &lt;br /&gt;
username: &amp;amp;quot;averagejoe&amp;amp;quot; pass: &amp;amp;quot;averagepass&amp;amp;quot;.&lt;/p&gt;
&lt;p&gt;I think I'm not alone in having such legacy accounts, &lt;br /&gt;
coming from very old sendmail-virtusertable setups, and &lt;br /&gt;
It would be really GREAT to be able to manage them &lt;br /&gt;
also with your tool, making possible a total migration.&lt;br /&gt;
I know it shouldn't be used on new installations, as it's &lt;br /&gt;
an administration PAIN, but for legacy accounts it would &lt;br /&gt;
be really great.&lt;/p&gt;
&lt;p&gt;It also would be great to be able to activate clearText &lt;br /&gt;
passwords. It's a security HOLE to have them, I know, &lt;br /&gt;
but  it makes support staff's life quite easier, so it would &lt;br /&gt;
be great to have it and let the user choose between &lt;br /&gt;
security and support-staff's ease of life :D&lt;/p&gt;
&lt;p&gt;Finally, for legacy accounts too, It would be great to be &lt;br /&gt;
able to specify the 'filters' onto a config file - for example, &lt;br /&gt;
I've seen that password has gb&lt;br /&gt;
Thank you again for your project. Now I'm leaving Qmail-&lt;br /&gt;
LDAP to postfix thanks to your app and your great &lt;br /&gt;
HOWTO.&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Anonymous</dc:creator><pubDate>Tue, 24 Dec 2002 17:49:13 -0000</pubDate><guid>https://sourceforge.net613c808bdc1a6b9a84ff35307c541c9c23b1e1ec</guid></item><item><title>stand-alone java admin app</title><link>https://sourceforge.net/p/jamm/feature-requests/1/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;I'm really excited about finding this project, except&lt;br /&gt;
for one little thing that I think I have in common with&lt;br /&gt;
a large majority of other developers looking for&lt;br /&gt;
something like this:  I'm a PHP developer, so my&lt;br /&gt;
webserver just has PHP, and were it not for this set of&lt;br /&gt;
scripts, I'd never have any need for a java servelet&lt;br /&gt;
container.&lt;/p&gt;
&lt;p&gt;The howto is masterfully written, and explains&lt;br /&gt;
everything anyone would need, except for that line&lt;br /&gt;
&amp;amp;quot;Installing and configuring a web servlet container&lt;br /&gt;
like Tomcat or Resin is outside the scope of this&lt;br /&gt;
document.&amp;amp;quot;&lt;/p&gt;
&lt;p&gt;I'm not above setting up a servlet container on my&lt;br /&gt;
server--given that the code is so many different&lt;br /&gt;
components it would be easier than rewriting it in&lt;br /&gt;
PHP--but it looks like *because* it's so modular, it&lt;br /&gt;
shouldn't be a great deal of work to put its&lt;br /&gt;
functionality into a java applet.  Are there any plans&lt;br /&gt;
in the works for doing such?&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Nathan Dial</dc:creator><pubDate>Fri, 06 Dec 2002 21:08:17 -0000</pubDate><guid>https://sourceforge.netcdb3deac85a332b22061737dcd3ee0b3b49b271b</guid></item></channel></rss>