Fwd: [Imap-uw] inbox corruption by iphone

[Brian W.]

Based on the below I would like to suggest that imap-uw, which hasnt been
updated since the author's death, be replaced with panda-imap, which solved
at least my problem.

Brian
-- Forwarded message --
From: David B Funk 
Date: Sat, Aug 1, 2015 at 7:59 AM
Subject: Re: [Imap-uw] inbox corruption by iphone
To: brian 
Cc: UW imap list 


Have you tried the "Panda IMAP" distro?
https://github.com/jonabbey/panda-imap

The mailbox locking problem can be avoided by using an alternate form of
mailbox (such as MIX) instead of the traditional mbox. Of course this won't
work in an environment that requires local direct access to the mailbox by
non-C-client aware mail clients. If you can switch to MIX format there are
many advantages (performance, scale-ability, backup facilitation, etc).
However if you do switch to MIX be -sure- to run the Panda distro, there
were some unfixed bugs in the UW-imap distro that can bite you.

After Mark left UW he started his own company with a fork of the UW-imap
which he called "Panda" and then started developing a commercial product
from there.

He kept Panda alive and semi-open sourced, making bug-fixes and adding some
small improvements (I know from conversations I had with him in '09 about a
UW-imap bug I found/fixed ). He made it available to people who explicitly
asked him for it.

After his death people took the last known version of Panda and turned it
into a github project and made additional improvements to it (I contributed
one of them ;).



On Sat, 1 Aug 2015, brian wrote:

as expected, thanx for confirming.
>
> Brian
>
> On 8/1/2015 1:25 AM, Chris Bunch wrote:
>
>> I have been running a UW_IMAP server  on Mac OS X mainly for family
>> accounts for around 12 years. We are all Mac/iOS users: we noted early on
>> that UW_IMAP doesn't cope well with more than one client logged into an
>> account at the same time. When the most any of us had was two machines
>> (home/office or home/laptop) that was relatively easy to manage but when
>> iOS came along(iPhones, iPads) came along things began to unravel and the
>> situation became unworkable. iPhones never stayed in sync with the server,
>> though I have not seen the specific corruption you mention.
>>
>> I am now in the process of transferring family accounts to Fastmail and
>> am setting up Dovecot on Linode/Ubuntu for a few other accounts I manage.
>> Sadly, UW_IPAD’s future died with Mark Crispin.
>>
>> C
>> 
>>
>>
>> On 22 Jul 2015, at 08:57, brian  wrote:
>>>
>>> One of the users on my freebsd server that runs uw imap has an
>>> intermittent problem with inbox corruption. Is a fix planned? I see others
>>> have had this issue already. I am essentially seeing this
>>> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=557103 though on
>>> Freebsd.
>>>
>>>
>>> Brian
>>>
>>
-- 
Dave Funk  University of Iowa
College of Engineering
319/335-5751   FAX: 319/384-0549   1256 Seamans Center
Sys_admin/Postmaster/cell_adminIowa City, IA 52242-1527
#include 
Better is not better, 'standard' is better. B{
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Fwd: [Imap-uw] inbox corruption by iphone

[Brian W.]

Based on the below it seems the imap-uw port ought to go to an unsupported
state or be otherwise modified?

Brian

-- Forwarded message --
From: David B Funk
Date: Sat, Aug 1, 2015 at 7:59 AM
Subject: Re: [Imap-uw] inbox corruption by iphone
To: brian
Cc: UW imap list imap...@u.washington.edu


Have you tried the Panda IMAP distro?
https://github.com/jonabbey/panda-imap

The mailbox locking problem can be avoided by using an alternate form of
mailbox (such as MIX) instead of the traditional mbox. Of course this won't
work in an environment that requires local direct access to the mailbox by
non-C-client aware mail clients. If you can switch to MIX format there are
many advantages (performance, scale-ability, backup facilitation, etc).
However if you do switch to MIX be -sure- to run the Panda distro, there
were some unfixed bugs in the UW-imap distro that can bite you.

After Mark left UW he started his own company with a fork of the UW-imap
which he called Panda and then started developing a commercial product
from there.

He kept Panda alive and semi-open sourced, making bug-fixes and adding some
small improvements (I know from conversations I had with him in '09 about a
UW-imap bug I found/fixed ). He made it available to people who explicitly
asked him for it.

After his death people took the last known version of Panda and turned it
into a github project and made additional improvements to it (I contributed
one of them ;).



On Sat, 1 Aug 2015, brian wrote:

as expected, thanx for confirming.

 Brian

 On 8/1/2015 1:25 AM, Chris Bunch wrote:

 I have been running a UW_IMAP server  on Mac OS X mainly for family
 accounts for around 12 years. We are all Mac/iOS users: we noted early on
 that UW_IMAP doesn't cope well with more than one client logged into an
 account at the same time. When the most any of us had was two machines
 (home/office or home/laptop) that was relatively easy to manage but when
 iOS came along(iPhones, iPads) came along things began to unravel and the
 situation became unworkable. iPhones never stayed in sync with the server,
 though I have not seen the specific corruption you mention.

 I am now in the process of transferring family accounts to Fastmail and
 am setting up Dovecot on Linode/Ubuntu for a few other accounts I manage.
 Sadly, UW_IPAD’s future died with Mark Crispin.

 C
 


 On 22 Jul 2015, at 08:57, brian br...@brianwhalen.net wrote:

 One of the users on my freebsd server that runs uw imap has an
 intermittent problem with inbox corruption. Is a fix planned? I see others
 have had this issue already. I am essentially seeing this
 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=557103 though on
 Freebsd.


 Brian


-- 
Dave Funk  University of Iowa
dbfunk (at) engineering.uiowa.eduCollege of Engineering
319/335-5751   FAX: 319/384-0549   1256 Seamans Center
Sys_admin/Postmaster/cell_adminIowa City, IA 52242-1527
#include std_disclaimer.h
Better is not better, 'standard' is better. B{
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org

denyhosts port

[Brian W.]

I have been using this for awhile. Starting Tuesday night at about 8PM
pacific time I have been getting notifications every few minutes, for the
same host, over and over. Is anyone else seeing this?

Brian
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org

Bash and pkgng

[Brian W.]

Thanx to those who put work in to get bash working properly. Previous
builds failed with a bison error but today a pig reinstall occurred and an
install of bash 4.3.30 was also successful.

Brian

Brian
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org

Re: squid-3.4.8_1 leaking memory

[Brian W.]

I added my observations via forward to the freebsd ports list since that is
the listed maintainer for squid.

Brian
On Sep 25, 2014 10:11 PM, Victor Sudakov v...@mpeks.tomsk.su wrote:

 Dewayne Geraghty wrote:
  
   squid-3.4.8_1 seems to be leaking memory heavily. Its SIZE and RES are
   growing several MB per minute until eventually swapping begins.

 [dd]

  I think you should file a bug report

 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=193938

 If anyone has anything to add or just say me too, please do.

 --
 Victor Sudakov,  VAS4-RIPE, VAS47-RIPN
 sip:suda...@sibptus.tomsk.ru

___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org

Re: squid-3.4.8_1 leaking memory

[Brian W.]

You seem to be onto something. On a single user testbox I use I see this

  PID USERNAMETHR PRI NICE   SIZERES STATE   C   TIMEWCPU
COMMAND

 6100 squid 1  200   612M 84076K kqread  1   4:01   0.00% squid

I then restarted squid and saw

73400 squid 1  200 61568K 21456K kqread  0   0:00   0.00% squid

I am on the i386 flavor of 10.0-RELEASE-p9

On Wed, Sep 24, 2014 at 9:56 PM, Victor Sudakov v...@mpeks.tomsk.su wrote:

 Colleagues,

 squid-3.4.8_1 seems to be leaking memory heavily. Its SIZE and RES are
 growing several MB per minute until eventually swapping begins.

 Is anyone using it? Have you encountered this problem?

 The relevant entries in squid.conf are:

 cache_mem 128 MB
 cache_dir ufs /webcache/cache 512 16 256
 memory_pools off # neither on nor off have any effect on leaking.

 As you see, the memory requirements should be rather modest.

 Running on 8.4-RELEASE-p16 i386.

 --
 Victor Sudakov,  VAS4-RIPE, VAS47-RIPN
 sip:suda...@sibptus.tomsk.ru
 ___
 freebsd-questi...@freebsd.org mailing list
 http://lists.freebsd.org/mailman/listinfo/freebsd-questions
 To unsubscribe, send any mail to 
 freebsd-questions-unsubscr...@freebsd.org

___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org

ports since 9.3-i386 upgrade

[Brian W.]

I have been having a bear of a problem maintaining ports since upgrading to
9.3. Currently, on a box primarily used as a mail server with postfix,
spamassassin, and other necessary pieces, I cannot get 2 of the support
pieces to compile, forcing me to run with older packages. It looks like
these 2 failures are causing other ports to fail.

I usually use this to upgrade ports.
portsnap fetch update  portupgrade -aP --batch  portsclean -CD  ls
-lrt /var/db/pkg  sa-update

first fail
BEGIN failed--compilation aborted at ./Makefile.PL line 27.
*** [do-configure] Error code 255
Stop in /usr/ports/dns/p5-Net-DNS.
** Command failed [exit code 1]: /usr/bin/script -qa
/tmp/portupgrade20140806-79109-1e1sedr env UPGRADE_TOOL=portupgrade
UPGRADE_PORT=p5-Net-DNS-0.74_1 UPGRADE_PORT_VER=0.74_1 make BATCH=yes
** Fix the problem and try again.

second fail
===  Configuring for p5-Socket-2.014
Attempt to reload Socket.pm aborted.
Compilation failed in require at /usr/local/lib/perl5/5.16/IPC/Cmd.pm line
46.
BEGIN failed--compilation aborted at /usr/local/lib/perl5/5.16/IPC/Cmd.pm
line 46.
Compilation failed in require at
/usr/local/lib/perl5/site_perl/5.16/ExtUtils/CBuilder/Base.pm line 9.
BEGIN failed--compilation aborted at
/usr/local/lib/perl5/site_perl/5.16/ExtUtils/CBuilder/Base.pm line 9.
Compilation failed in require at
/usr/local/lib/perl5/site_perl/5.16/ExtUtils/CBuilder/Platform/Unix.pm line
4.
BEGIN failed--compilation aborted at
/usr/local/lib/perl5/site_perl/5.16/ExtUtils/CBuilder/Platform/Unix.pm line
4.
Compilation failed in require at (eval 9) line 2.
BEGIN failed--compilation aborted at (eval 9) line 2.
Compilation failed in require at ./Makefile.PL line 19.
*** [do-configure] Error code 255
Stop in /usr/ports/net/p5-Socket.
** Command failed [exit code 1]: /usr/bin/script -qa
/tmp/portupgrade20140806-80837-1afrfnk env UPGRADE_TOOL=portupgrade
UPGRADE_PORT=p5-Socket-2.013 UPGRADE_PORT_VER=2.013 make BATCH=yes
** Fix the problem and try again.

** Listing the failed packages (-:ignored / *:skipped / !:failed)
! dns/p5-Net-DNS (p5-Net-DNS-0.74_1)(unknown build error)
! net/p5-Socket (p5-Socket-2.013)(unknown build error)
* net/p5-IO-Socket-IP (p5-IO-Socket-IP-0.27)
* security/p5-IO-Socket-SSL (p5-IO-Socket-SSL-1.962)
* net/p5-Net-HTTP (p5-Net-HTTP-6.06)
* www/p5-libwww (p5-libwww-6.05)
* mail/spamassassin (p5-Mail-SpamAssassin-3.3.2_8)

Brian
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org

portupgrade problem?

[Brian W.]

I am having a problem with portupgrade; is anyone else seeing this?

===  Building package for portupgrade-2.4.11.2,2
Creating package /usr/ports/packages/All/portupgrade-2.4.11.2,2.tbz
Registering depends: ruby19-bdb-0.6.6_1 db41-4.1.25_4 ruby-1.9.3.448,1
libexecinfo-1.1_3 libffi-3.0.13 libyaml-0.1.4_2.
Registering conflicts: portupgrade-devel-*.
Creating bzip'd tar ball in
'/usr/ports/packages/All/portupgrade-2.4.11.2,2.tbz'
tar: libdata/ldconfig/portupgrade: Cannot stat: No such file or directory
tar: Error exit delayed from previous errors.
pkg_create: make_dist: tar command failed with code 256
*** [do-package] Error code 1

Stop in /usr/ports/ports-mgmt/portupgrade.
*** [reinstall] Error code 1

Stop in /usr/ports/ports-mgmt/portupgrade.
** Command failed [exit code 1]: /usr/bin/script -qa
/tmp/portupgrade20130923-47104-x5ofv env UPGRADE_TOOL=portupgrade
UPGRADE_PORT=portupgrade-2.4.11.1,2 UPGRADE_PORT_VER=2.4.11.1,2 make
BATCH=yes reinstall
---  Restoring the old version

--
  Fill ALT_PKGDEP section in pkgtools.conf file for portupgrade to be
  aware of alternative dependencies you use.
  E.g.
  ALT_PKGDEP = {
# Use the -nox11 port when another port depends on
category/portexample
'category/portexample' = 'category/portexample-nox11',
  }

  Note also, portupgrade knows nothing about how to handle ports with
  different suffixes (E.g. -nox11). So you should explicitly define
  variables (E.g. WITHOUT_X11=yes) for the ports in /etc/make.conf or
  pkgtools.conf (MAKE_ARGS section) files.
--

** Fix the installation problem and try again.
[Updating the pkgdb format:bdb_btree in /var/db/pkg ... - 99 packages
found (-0 +1) . done]
** Listing the failed packages (-:ignored / *:skipped / !:failed)
! ports-mgmt/portupgrade (portupgrade-2.4.11.1,2) (install error)
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org

spamassassin port/package

[Brian W.]

 Any chance this could by default do a sa-update? I have this happen 
twice now where  portupgrade -ap got me a new spamassassin, but spamd 
wouldn't start until I ran sa-update.


Brian




===
Email scanned by PC Tools - No viruses or spyware found.
(Email Guard: 7.0.0.18, Virus/Spyware Database: 6.15810)
http://www.pctools.com/
===
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org

Re: The new cups ports seem to not recognize usb printers on FreeBSD 7.2-STABLE

[Brian W.]

Dirk Meyer wrote:

eculp schrieb:,

  
would seem that I'm going to have to upgrade all my 7.2-STABLE servers  
to either 8.0 or 9.0 that all have usb printers that are being shared  
by others through cups.



Please update the ports and try again.
I would like to know if using libusb solves your problems.

kind regards Dirk

- Dirk Meyer, Im Grund 4, 34317 Habichtswald, Germany
- [dirk.me...@dinoex.sub.org],[dirk.me...@guug.de],[din...@freebsd.org]
http://people.freebsd.org/~dinoex/errorlogs/
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
  
I have been having a different cups problem related to the man page 
portion of this on a FreeBSD 8 system.  This has been  a problem that I 
believe appeared early this week.


Compiling mantohtml.c...
cc  -Wall -Wno-format-y2k -fPIC -Os -g -fstack-protector -I.. 
-D_CUPS_SOURCE -I/usr/local/include -O2 -pipe  -fno-strict-aliasing 
-I/usr/local/include   -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE 
-D_THREAD_SAFE -D_REENTRANT  -c mantohtml.c
cc  -L../cgi-bin -L../cups -L../filter -L../ppdc -L../scheduler 
-L/usr/local/lib -Wl,-R/usr/local/lib  -pie -fPIE -Wall -Wno-format-y2k 
-fPIC -Os -g -fstack-protector -o mantohtml mantohtml.o

echo Converting man pages to HTML...
Converting man pages to HTML...
for file in cancel.1 cupstestdsc.1 cupstestppd.1 lp.1 lpoptions.1 
lppasswd.1 lpq.1 lprm.1 lpr.1 lpstat.1 ppdc.1 ppdhtml.1 ppdi.1 
ppdmerge.1 ppdpo.1; do \

   echo $file...; \
   ./mantohtml `basename $file .1`.man 
../doc/help/man-`basename $file .1`.html; \

   done
   cancel.1...
/libexec/ld-elf.so.1: ./mantohtml: invalid PT_PHDR
   cupstestdsc.1...
/libexec/ld-elf.so.1: ./mantohtml: invalid PT_PHDR
   cupstestppd.1...
/libexec/ld-elf.so.1: ./mantohtml: invalid PT_PHDR
   lp.1...
/libexec/ld-elf.so.1: ./mantohtml: invalid PT_PHDR
   lpoptions.1...
/libexec/ld-elf.so.1: ./mantohtml: invalid PT_PHDR
   lppasswd.1...
/libexec/ld-elf.so.1: ./mantohtml: invalid PT_PHDR
   lpq.1...
/libexec/ld-elf.so.1: ./mantohtml: invalid PT_PHDR
   lprm.1...
/libexec/ld-elf.so.1: ./mantohtml: invalid PT_PHDR
   lpr.1...
/libexec/ld-elf.so.1: ./mantohtml: invalid PT_PHDR
   lpstat.1...
/libexec/ld-elf.so.1: ./mantohtml: invalid PT_PHDR
   ppdc.1...
/libexec/ld-elf.so.1: ./mantohtml: invalid PT_PHDR
   ppdhtml.1...
/libexec/ld-elf.so.1: ./mantohtml: invalid PT_PHDR
   ppdi.1...
/libexec/ld-elf.so.1: ./mantohtml: invalid PT_PHDR
   ppdmerge.1...
/libexec/ld-elf.so.1: ./mantohtml: invalid PT_PHDR
   ppdpo.1...
/libexec/ld-elf.so.1: ./mantohtml: invalid PT_PHDR
gmake[1]: *** [html] Error 1
gmake[1]: Leaving directory `/usr/ports/print/cups-base/work/cups-1.4.2/man'
gmake: *** [all] Error 1
*** Error code 1

Stop in /usr/ports/print/cups-base.
*** Error code 1

Stop in /usr/ports/print/cups-base.
** Command failed [exit code 1]: /usr/bin/script -qa 
/tmp/portupgrade20091204-2776-1rxg9wx-0 env UPGRADE_TOOL=portupgrade 
UPGRADE_PORT=cups-base-1.3.10_4 UPGRADE_PORT_VER=1.3.10_4 make

** Fix the problem and try again.



___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org