On 17.7.2018 22:30, Erik Kangas, Ph.D. wrote:
For MIX no broken mailbox repair tool exists
Mark has made available mixrbld and mixdfix tools for fixing indexes and
message files.
Thanks, I has not been aware of it.
May be I will try MIX in the future.
On 17.7.2018 22:46, Tim Mooney wrote:
On Tue, 17 Jul 2018, Dan Lukes wrote:
On 17.7.2018 20:56, David B Funk wrote:
Not to mention, for years Mark Crispin adamantly opposed anything greater
than 32 bit code (for portability sake). So there may still be dark corners
of the UW/Panda IMAP code that will break on a 64 bit system.
Ac
Tim,
On 7/17/2018 1:46 PM, Tim Mooney wrote:
With an adjusted setting for MIXDATAROLL, it works
very well.
What value do you find best?
thanks,
David
--
David Severance
Enterprise Unix Services
Office of Information Technology
(949) 824-7552
s...@uci.edu
_
In regard to: Re: [Imap-uw] mbox file size limitations?, Dan Lukes said (at...:
I can' withstand to answer you using your own footer:
Better is not better, 'standard' is better. B{
Classic "UNIX" format used by most of MTA. It's de-facto standard. It's
s
For MIX no broken mailbox repair tool exists. I consider it unfinished
work I'm not ready to finish by self - as a result, I can't use it for
production deployment.
Mark has made available mixrbld and mixdfix tools for fixing indexes
and message files. These fix 98% of issues. The remaining
On 17.7.2018 20:56, David B Funk wrote:
Not to mention, for years Mark Crispin adamantly opposed anything
greater than 32 bit code (for portability sake). So there may still be
dark corners of the UW/Panda IMAP code that will break on a 64 bit system.
According my experience, it's more stable
On Tue, 17 Jul 2018, Dan Lukes wrote:
GLEN HERRMANNSFELDT wrote on 17. 7. 2018 3:35:
Many C implementations using 32 bit int have a 2G
file size limit. This happens even if there are
no fseek() calls.
Moreover, even on those systems having larger int, there's an issue somewhere
in the commo
GLEN HERRMANNSFELDT wrote on 17. 7. 2018 3:35:
Many C implementations using 32 bit int have a 2G
file size limit. This happens even if there are
no fseek() calls.
Moreover, even on those systems having larger int, there's an issue
somewhere in the common part of code. Sometime, about 128 byte
Many C implementations using 32 bit int have a 2G
file size limit. This happens even if there are
no fseek() calls.
-- glen
> On July 16, 2018 at 6:16 PM Ken Johnson wrote:
>
>
> On a Debian system I support, exim4 delivers mail to /var/mail/
> mbox files. Is there a known limitation to the
On a Debian system I support, exim4 delivers mail to /var/mail/
mbox files. Is there a known limitation to the size of those files that
uw-imap imapd and pop3d can support?
Thanks,
Ken
___
Imap-uw mailing list
Imap-uw@u.washington.edu
http://mailma
10 matches
Mail list logo
