Aquileo | Recent changes to feature-requestshttps://sourceforge.net/p/vpopmail/feature-requests/2010-09-01T21:13:56ZRecent changes to feature-requestsAquileo | vusage daemon should use auth module for lastauth time2010-09-01T21:13:56Z2010-09-01T21:13:56ZMatt Brookingshttps://sourceforge.net/u/volz0r/https://sourceforge.netfe96cd169aa07c53560d2986a4e49b1f116c4f8e<div class="markdown_content"><p>The vusage daemon checks for a lastauth file on the disk to determine last authentication time for userstore aging. It should call the backend module API.<br /> To do this, the user portion of the code should take up USERSTORE_AGE_MAX and USERSTORE_DAY_AGE. Enforcement of these two configurations should not be done under the userstore.</p></div>Aquileo | add load_connection_info support to backends/postgres/ 2009-08-17T15:50:20Z2009-08-17T15:50:20ZItamar Reis Peixotohttps://sourceforge.net/u/ispbrasil/https://sourceforge.netd5bb83309c5499f3f24b448ed1aacacbc7d5f498<div class="markdown_content"><p>mysql backend uses load_connection_info function to load mysql connections details from vpopmail.mysql</p> <p>Can you add the same feature into backends/postgres/ and create a file called vpopmail.postgres with postgresql connections details ?</p></div>Aquileo | Make symlink following configurable in vusaged2009-07-31T17:34:48Z2009-07-31T17:34:48ZMatt Brookingshttps://sourceforge.net/u/volz0r/https://sourceforge.net894da969f91d561ea3f25fdc6ea9376539296a36<div class="markdown_content"><p>vusaged blindly follows symlinks<br /> While this is not a security issue, this should be configurable. </p></div>Aquileo | Updated LDAP code2009-07-31T17:33:20Z2009-07-31T17:33:20ZMatt Brookingshttps://sourceforge.net/u/volz0r/https://sourceforge.netb5ef841618e2811ac9edf8b72ed6a6c2d1130764<div class="markdown_content"><p>Update the LDAP schema to use Inter7-assigned OIDs<br /> Update module to support this new schema. The LDAP module<br /> must be backwards compatible.</p></div>Aquileo | Remove domain alias limitations2009-05-18T20:28:10Z2009-05-18T20:28:10ZMatt Brookingshttps://sourceforge.net/u/volz0r/https://sourceforge.net0d1f700215af9420fcab49349b3636f6a894f8eb<div class="markdown_content"><p>MAX_DOM_ALIAS is set to 100 in vpopmail.h<br /> Not only is that limitation very small, but there shouldn't be a limitation<br /> Furthermore, some of the code that handles domain aliases cause segfaults<br /> when the limit has been reached or exceeded</p></div>Aquileo | dotqmail support in vdeloldusers2009-02-03T16:31:46Z2009-02-03T16:31:46ZMatt Brookingshttps://sourceforge.net/u/volz0r/https://sourceforge.net84e61e53ea9c5c51fde173ddda9ebd43d547e059<div class="markdown_content"><p>Ignore old users with dotqmail files that forward</p></div>Aquileo | vmoduser options2008-04-22T07:48:07Z2008-04-22T07:48:07ZWouter van der Schagthttps://sourceforge.net/u/woutersteven/https://sourceforge.net69b6f461fb03af7185a84caa46ac339f90077ca2<div class="markdown_content"><p>Suggested additional flags for vmoduser to unset flags without having to clear them all. For example</p> <p>-p = disable popaccess<br /> -P = enable popaccess (capitalized)</p> <p>For my current purpose i modified vmoduser.c</p> <p>Line 84 and Line 110 was:<br /> if ( GidFlag != 0 ) mypw-&gt;pw_gid |= GidFlag;<br /> Change to:<br /> if ( GidFlag != 0 ) mypw-&gt;pw_gid ^= GidFlag;</p> <p>the flags now flip. it will set if unset and unset if set. This is good enough for my purpose, but a better solution would be preferable. Basically, the |= is changed to ^=.</p></div>Aquileo | Per-user message size limits2008-02-06T06:50:33Z2008-02-06T06:50:33ZThanosKhttps://sourceforge.net/u/thanosk/https://sourceforge.netc66d644d30fb55d3109209de7cc1f197b017dbe9<div class="markdown_content"><p>What would be extremely useful is to be able to set <br /> per-user message size limits.<br /> It is quite useful in company environments where you might want different people or groups of people to be able to send different sized emails.</p> <p>At the moment to achieve this you either need to do it per IP basis in tcp.smtp file which is quite messy or use<br /> John Simpsons' 'qmail AUTH_CDB patch' and edit the file that is produced by vpopmail with all the addresses by hand which is equally tedious.</p></div>Aquileo | List Users for domain2006-01-13T20:48:07Z2006-01-13T20:48:07ZAnonymoushttps://sourceforge.net/u/userid-None/https://sourceforge.net1adfee04ce4bcdabfcc2f2493980f3c4d5343c19<div class="markdown_content"><p>List users for domain in console.</p></div>Aquileo | vadddomain - add forwards for postmaster/abuse2005-02-11T01:36:09Z2005-02-11T01:36:09ZCharles Sprickmanhttps://sourceforge.net/u/sfspork/https://sourceforge.net8254f0a6a4cbeb51e3bb598f1d7a7199285d2746<div class="markdown_content"><p>Hi,</p> <p>I use vpopmail at an ISP. As such, we generally find users don't really <br /> want/need/understand accounts such as "postmaster@" or <br /> "abuse@". We like to handle any complaints or questions directed at <br /> those addresses. I think that's generally good karma. I don't want <br /> any domains under our control to not have at the very least an <br /> "abuse@" address answered by real humans that know how to deal <br /> with complaints.</p> <p>How about a switch to vadddomain that takes a domain as an <br /> argument? ie:</p> <p>vadddomain -a isp.com newdomain.com (-a for "abuse"?)</p> <p>Which would make two .qmail files in that domain's home:</p> <p>.qmail-postmaster (contents: postmaster@isp.com)<br /> .qmail-abuse (contents: abuse@isp.com)</p> <p>It would be extra cool if one specified a "-a" with no args that the <br /> defaultdomain would be used...</p></div>