Re: [vchkpw] Info on upgrading vpopmail.

2007-09-24 Thread Allie Daneman
I only recompile Qmailadmin, I run Dovecot as my imap server.

On Mon, 24 Sep 2007 08:08:16 -0600, mlist [EMAIL PROTECTED] wrote:
 Hello,
 
 I have a question regarding vpopmail upgrades.  The UPGRADE
 documentation states:
 
 When recompiling vpopmail, you need to recompile all binaries that link
 into the vpopmail libraries.  These include QmailAdmin, qmail-smtpd (if
 you have the chkuser patch applied), Courier-IMAP etc.
 
 I have a test machine that I upgraded to vpopmail 5.4.23.  I
 recompiled/reinstalled qmailadmin and vqadmin.  I didn't recompile
 courier-imap nor did I recompile qmail-smtpd.
 
 I was able to telnet and successfully login to ports 25, 110, 143.  So,
 is it necessary to recompile qmail-smtpd and Courier?  I didn't
 recompile qmail-smtp because I'm not using the chkuser patch - I am
 using john simpsons combined patch 1.7.01.  Would I still need to
 recompile?
 
 Thanks for the help,
 
 Matt



Re: [vchkpw] vpopmail 5.4.23 released

2007-09-23 Thread Allie Daneman
So far so good...thanks for your time and effort. I have it installed and
quickly tested with Qmailadmin 1.2.11. 

On Sun, 23 Sep 2007 17:44:50 -0600, Rick Widmer [EMAIL PROTECTED]
wrote:
 http://vpopmail.sf.net/
 
 5.4.23 - released 23-Sep-2007
 
 Release Notes:
 
 This release reverts the maildirquota warnings patch.  I
 believe the correct way to fix this is to make the quota
 variable a 64 bit unsigned value so we can go past the 2GB (or
 is it 4GB) size limit on the current 32 bit values.  That can
 be done in the 5.5 branch which will be created once we have a
 good stable 5.4 release.
 
 
 
 ChangeLog:
 
 5.4.23 - Released 23-Sep-2007
   Rick Widmer
   - Upgrade build system to match my dev server  (SuSE 10.2)
   - Revert maildirquota warnings change



[vchkpw] 5.4.22 + Qmailadmin...is it going to be fixed ?

2007-09-21 Thread Allie Daneman
Is there any movement to fix 5.4.22 to co-habitate with Qmailadmin ? I'm
not in any hurry to try and upgrade again BUT I really like running the
latest version if possible ;)



Re: [vchkpw] 5.4.22 + Qmailadmin...is it going to be fixed ?

2007-09-21 Thread Allie Daneman
Ok great...I'll wait for the official release and test that, thanks for all
your work on this.

On Fri, 21 Sep 2007 16:33:05 -0600, Rick Widmer [EMAIL PROTECTED]
wrote:
 
 
 Allie Daneman wrote:
 Is there any movement to fix 5.4.22 to co-habitate with Qmailadmin ? I'm
 not in any hurry to try and upgrade again BUT I really like running the
 latest version if possible ;)
 
 There is a patch for qmailadmin on SourceForge.  Its tracker number is
 [1795973].  On the other hand, this weekend I will release 5.4.23 that
 backs out the change that caused this problem.  I want a stable release
 that does not require any changes to existing code before the next batch
 of innovation.
 
 
 Rick



Re: [vchkpw] vpopmail 5.4.22 breaks qmailadmin 1.2.X

2007-09-16 Thread Allie Daneman
Rick Widmer([EMAIL PROTECTED])@Sun, Sep 16, 2007 at 09:02:31PM -0600:
 Allie Daneman wrote:
 I have no issues with building this version BUT it breaks qmailadmin
 1.2.11. I get the following when trying to make qmailadmin on vpopmail
 5.4.22:
 
 Thanks for testing!  Can you please tell me the ./configure options you 
 are using?  I want to get an idea which ones are being used.
No additional options...just ./configure.
 
 
 I posted a patch on qmailadmin's SourceForge site.  The tracker number 
 is [ 1795973 ].  It should allow qmailadmin to work with 5.4.22.  On the 
 other hand, I think I am going to revert the part of the patch that 
 caused this problem, and apply it later.  I plan to review all the 
 buffer size definitions in the next development effort, and that is 
 probably a better time for things that change the library interface. 
 Look for another release with this change reverted next weekend.
 
 I'm not sure if the issue is because I am compiling new options in 
 vpopmail, or the fact that I recently upgraded from SuSE 9.3 to Open 
 SuSE 10.2.  It doesn't matter, I don't want to see any warnings when I 
 compile, but it can wait.  Right now I want a good stable version of 
 vpopmail for the stable branch.
 
 In the mean time, if any lurkers feel nervous about your favorite 
 combination of ./configure options not working, now would be a good time 
 to build and test.
 
 
 P.S. Can you guys also update the version...the configure results have
 been a version behind since 5.4.21. Thanks.
 
 I'm trying...  I'm sure I changed it for 22, but something must have 
 gone wrong.
 
 Rick


[vchkpw] vpopmail 5.4.22 breaks qmailadmin 1.2.X

2007-09-15 Thread Allie Daneman
I have no issues with building this version BUT it breaks qmailadmin
1.2.11. I get the following when trying to make qmailadmin on vpopmail
5.4.22:
make  all-am
source='qmailadmin.c' object='qmailadmin.o' libtool=no
depfile='.deps/qmailadmin.Po' tmpdepfile='.deps/qmailadmin.TPo'
depmode=gcc3 /bin/sh ./depcomp  gcc -I. -I/home/vpopmail/include -I. -I.
-I.  -g -O2 -Wall -c `test -f 'qmailadmin.c' || echo
'./'`qmailadmin.c
In file included from qmailadmin.c:48:
qmailadmin.h:66: error: conflicting types for `readuserquota'
/home/vpopmail/include/vpopmail.h:219: error: previous declaration of
`readuserquota'
*** Error code 1

Stop in /home/src/qmailadmin-1.2.11.
*** Error code 1

Stop in /home/src/qmailadmin-1.2.11 (line 163 of Makefile).

I had to cut back to 5.4.21 ,my OS is OpenBSD 4.1, and I don't use a
database backend or vpopmaild.

P.S. Can you guys also update the version...the configure results have
been a version behind since 5.4.21. Thanks.

Rick Widmer([EMAIL PROTECTED])@Sat, Sep 15, 2007 at 05:02:03PM -0600:
 
 NOTE:  If you use any unusual ./configure options when you build 
 vpopmail, please give this version a try.  I would like to get a stable 
 version of vpopmail that works for everyone before moving on with new 
 development.  Now would be a good time to report any problems you have 
 with your particular set of ./configure options!
 
 
 ===
 
 http://vpopmail.sf.net/
 
 5.4.22 - released 15-Sep-07
 
 Release Notes:
 
 This is an all bug fix release.
 
 o segfault from isCatchall when MySQL back end is used with valias.
 
 o Missing ERR defines in vpopmaild.msg
 
 o Fix Help text for *_ip_map in vpopmaild.
 
 o Incompatible type warnings in maildirquota.
 
 
 
 ChangeLog:
 
 5.4.22 - Released 15-Sep-2007
  Steve Cole
   - invalid MySQL info in UPGRADE
 
   Bill Shupp
   - Missing ERR defines in vpopmaild.msg
   - Fix help text for add_ip_map and del_ip_map in vpopmaild.c
 
   Rick Widmer
   - attack warnings in maildirquota by making some variables
 unsigned everywhere
 
  Steve Cole, Marcello Lupo, Japheth Cleaver,  Rick Widmer
   - segfault in vdeluser with MySQL back end.  Work around
 applied, and note added to TODO about making database valias
 return .qmail files if they exist which is the long term fix.
 
 
 


Re: [vchkpw] qmail+vpopmail smtp-auth for roaming-users]

2007-02-08 Thread Allie Daneman
Rick Widmer([EMAIL PROTECTED])@Thu, Feb 08, 2007 at 07:49:31AM -0700:
 
 
 Otto Rodusek (AP-SGP) wrote:
 Hi Micheal,
 
 Thanks for the reply. Indeed, I did use the --with-authvchkpw 
 --without-authdaemon but it made no difference.
 
 If I understand your email correctly, since I'm using courier-imap 4.1.2 
 it is impossible for imap authentication to update the open-smtp file?? 
 
 I believe that is correct.  Courier no longer provides the IP address 
 needed to authenticate roaming users.
 
 Hence it is IMPOSSIBLE for any roaming users to send mail?? So what's 
 the solution (if any) - is it possible that ALL users who use 
 courier-imap 4++ are unable to send email and this is acceptable to 
 them??
 
 SMTP Auth.  Have the roaming users login to smtp by adding a user name 
 and password to the outgoing mail server configuration of their browser, 
 and enable that function.  (The same one they use to receive mail)
 
 Since you are using Bill Shupp's toaster, it should already be installed 
 on your server.
SMTP Auth is the only way to go...I've tried every other method and they just 
don't work well.

-- 
~Allie D.

The chief cause of problems is solutions.
-- Eric Sevareid