>=net-mail/vpopmail-5.4.19 handling of quotas is not compatible with the solution before this version. The format for setting quota is the same but the retrieval of quota values is now handled by vusaged (server) and vusagec (client). The current ebuild does not build the server which is located within the vusaged subdirectory of vpopmail. It also does not copy config files for the client. I enhanced the current ebuild to provide these features. However my ebuild has no gentoo style init.d script for the vusaged daemon yet. Currently I use the default one. If someone is interested let me know. Reproducible: Always Steps to Reproduce: 1. emerge vpopmail 5.4.30 2. try to send emails to accounts which have a quota set 3. Actual Results: Error messages in qmail-send about missing conf files, duplicate E-Mail sending etc. . Expected Results: No Errors with quota functionality.
gentoo style init.d script completed, too.
After upgrade to net-mail/vpopmail-5.4.30 we have a problem with mail delivery. When we are trying to see vuserinfo we got segfault: # vuserinfo user@mail.com name: user passwd: $1$gW/2NGEA$Pp6B7ZNS8jAjcTMOf/Tpz0 clear passwd: comment/gecos: user uid: 0 gid: 0 flags: 0 gecos: user limits: No user limits set. dir: /var/vpopmail/domains/makrogroup.com/dmitrijus quota: 524288000S client_connect: warning: config_begin failed Segmentation fault In /var/log/qmail/qmail-send/current a lot of: starting delivery 10741: msg 6754 to local mail.com-user@mail.com status: local 1/10 remote 0/20 delivery 10741: deferral: client_connect:_warning:_config_begin_failed/Aack,_child_crashed._(#4.3.0)/ status: local 0/10 remote 0/20 We unsuccessfully tried rollback to vpopmail-5.4.16: make[2]: *** [libvpopmail_a-vpopmail.o] Error 1 Make failed. :(
Rollback to net-mail/vpopmail-5.4.19 helped.
ref comment #2: This is the error you get when you set quotas and do not have vusaged running and configured. As I still get errors with vusaged running and configured I deactivated the client in vusagec.conf in /var/vpomail/etc. This file however will not be copied by the 5.4.30 ebuild so you have to get it and the vusaged.conf from the vpopmail distribution tar.gz file. After that you can deactivate the usage of the client In vusagec.conf and everything should work as normal. At least for me... Tricky and time consuming problem though.
A solution can be found on the vpopmail mailinglist: http://www.mail-archive.com/vchkpw@inter7.com/msg27371.html
Because of the unstabling of .30 Portage downgraded me to .16, which breaks horribly. Build log at http://dirkjan.ochtman.nl/files/build.log.
(In reply to comment #1) > gentoo style init.d script completed, too. > can you please provide your ebuild/init.d changes as attachments to this bug?
Created attachment 219125 [details] Vpopmail ebuild supporting vusaged
Created attachment 219127 [details] vusaged init.d script for vpopmail ebuild Ebuild and vpopmail script do the following: -Building vpopmail AND vusaged -Installing necessary configuration files for vusaged -Installing init.d-script vusaged -Deactivating usage of vusagec and vusaged per default for compliance with older vpopmail versions -Symlinking the appropriate docs -Printing a BIG FAT warning about usage of vusaged and where docs can be found Addtionally I can say that I did not manage to get vusaged working although the client (vusagec) successfully connects to vusaged. Vdominfo always fails to do so so that you cannot use it in production. Regrettably I had no time yet to file a bug report for vpopmail. Suggestions are welcome Regards, Phillip
5.4.30-r1 in portage. please give it a try. i've disabled the build of vusaged, since it requires a vusaged aware libvpopmail.so to be already installed, and i have no time to patch the broken build system of vpopmail or split vusaged into its own package. thanks for reporting
(In reply to comment #10) > 5.4.30-r1 in portage. please give it a try. > > i've disabled the build of vusaged, since it requires a vusaged aware > libvpopmail.so to be already installed, and i have no time to patch the broken > build system of vpopmail or split vusaged into its own package. > > thanks for reporting > I tried the new Ebuild and I am using it in production now. Working! Thanks!
