Displaying 20 results from an estimated 2000 matches similar to: "Lost sub-mailboxes - not showing after upgrading to Dovecot from Courier-IMAP"
2019 Jan 30
3
"unknown user - trying the next userdb" Info in log
On 30 Jan 2019, at 10:57 am, Stephan Bosch <stephan at rename-it.nl <mailto:stephan at rename-it.nl>> wrote:
>
> Op 30/01/2019 om 00:06 schreef James Brown via dovecot:
>>
>>> On 30 Jan 2019, at 9:24 am, Stephan Bosch <stephan at rename-it.nl <mailto:stephan at rename-it.nl>> wrote:
>>>
>>>
>>>
>>> Op 29/01/2019
2019 Jan 30
0
"unknown user - trying the next userdb" Info in log
<!doctype html>
<html>
<head>
<meta charset="UTF-8">
</head>
<body>
<div>
<br>
</div>
<blockquote type="cite">
<div>
On 30 January 2019 at 07:12 James Brown <
<a href="mailto:jlbrown@bordo.com.au">jlbrown@bordo.com.au</a>> wrote:
</div>
2023 Feb 20
1
service(imap-login): Fatal: setrlimit(RLIMIT_DATA, 268435456): Invalid argument macOS
I fixed the issue with Dovecot not starting on macOS Ventura by adding this to 10-master.conf:
service log {
vsz_limit = 0
}
But now when I try to login via Imap on port 143 I get the same error for imap-login:
Feb 20 15:55:41 imap-login: Error: Feb 20 15:55:41 service(imap-login): Fatal: setrlimit(RLIMIT_DATA, 268435456): Invalid argument
Feb 20 15:55:41 imap-login: Fatal: master:
2009 Dec 17
3
Upgrade 1.0->1.2 dbox mysql
Hi,
I just upgraded to from dovecot v1.1.15 to v1.2.9 so I can use dovecot-
sieve.
Most everything seems to work but my webmail (roundcube) clients are
not seeing their subscribed folders.
Reading over the upgrade docs at http://wiki.dovecot.org/Upgrading/1.2
I'm wondering if I have the two settings below configured correctly.
dovecot.conf:
mail_location =
2013 Dec 10
1
undoing a zlib test
I'm trying to undo a dovecot zlib test and uncompress 6 emails in my Junk mailbox. There are about 25 total in different mailboxes but I thought I'd first start with those in my Junk. I ran:
# dsync -v -u terry at dop.com -m Junk -o plugin/zlib_save= backup maildir:/path/to/temp/folder
which returned without error and backed up my Junk mailbox but didn't uncompress the 6 emails. Am I
2006 Jul 28
1
Problems reading mbox
I'm having problems getting dovecot to read my mbox file. I have
turned on mail_debug. Log says:
Jul 28 11:03:20 Bordo-Mail-Server dovecot: Dovecot v1.0.rc2 starting up
Jul 28 11:03:36 Bordo-Mail-Server dovecot: pop3-login: Login:
user=<jlbrown>, method=PLAIN, rip=192.168.1.10, lip=192.168.1.9
Jul 28 11:03:36 Bordo-Mail-Server dovecot: POP3(jlbrown): Effective
uid=501, gid=501
Jul
2019 Jan 29
2
"unknown user - trying the next userdb" Info in log
> On 30 Jan 2019, at 9:24 am, Stephan Bosch <stephan at rename-it.nl> wrote:
>
>
>
> Op 29/01/2019 om 01:51 schreef James Brown via dovecot:
>> I?ve set up a new mail server. Auth-worker is giving me this error all the time:
>>
>> auth-worker(11160): Info: passwd(sales at bordo.com.au <mailto:sales at
2018 Dec 04
2
Lda fatal: setgid (102 from userdb lookup) failed
Sorry if this is a nubbie question, but I?m getting:
lda(jlbrown at bordo.com.au)<4444><QFg5KRHVBBxcEQAAYBwt+A>: Fatal: setgid(102 from userdb lookup) failed with euid=501(jlbrown), gid=20(staff), egid=20(staff): Operation not permitted (This binary should probably be called with process group set to 102 instead of 20(staff))
How can I fix this?
(macOS Mojave, Dovecot 2.3.4)
2011 Jun 17
0
pop3-login Error after dovecot 1.2.11 to dovecot 2.0.13
I recently upgaded from dovecot 1.2.11 to 2.0.13.
I used this command on my dovecont.conf after the upgrade and then moved the new file into place after removing some plugins.
$ sudo doveconf -n -c dovecot-1.conf > dovecot-2.conf
After 24+ hours with no issues I was getting pop3 login failures.
...
/path/to/log/dovecot.log:master: Error: service(pop3): read(status) failed: Interrupted system
2023 Feb 22
1
Auth-worker, unknown scheme ARGON2ID
On 21 Feb 2023, at 10:12 pm, James Brown <jlbrown at bordo.com.au> wrote:
>
> The new one has Dovecot compiled with same configure options, same configuration files, but fails to authenticate:
>
> Feb 21 21:51:03 master: Info: Dovecot v2.3.20 (80a5ac675d) starting up for imap, pop3 (core dumps disabled)
> Feb 21 21:51:33 auth-worker(11701): Error: conn unix:auth-worker
2019 Jan 30
2
"unknown user - trying the next userdb" Info in log
On 30 Jan 2019, at 4:35 pm, Aki Tuomi <aki.tuomi at open-xchange.com <mailto:aki.tuomi at open-xchange.com>> wrote:
>
>>
>> On 30 January 2019 at 07:12 James Brown < jlbrown at bordo.com.au <mailto:jlbrown at bordo.com.au>> wrote:
>>
>>
>> >> My settings:
>> ...
>> >> userdb {
>> >> driver = passwd
2023 Feb 22
1
Auth-worker, unknown scheme ARGON2ID
> On 22/02/2023 07:00 EET James Brown <jlbrown at bordo.com.au> wrote:
>
>
> On 21 Feb 2023, at 10:12 pm, James Brown <jlbrown at bordo.com.au> wrote:
>
> >
> >
> > The new one has Dovecot compiled with same configure options, same configuration files, but fails to authenticate:
> >
> > Feb 21 21:51:03 master: Info: Dovecot v2.3.20
2018 Mar 01
0
Make fails with 2.3.0.1 & 2.2.34 on Mac OS X 10.7.5
On 01.03.2018 07:34, James Brown wrote:
> On 1 Mar 2018, at 4:09 pm, Aki Tuomi <aki.tuomi at dovecot.fi
> <mailto:aki.tuomi at dovecot.fi>> wrote:
>>
>>
>>> On 01 March 2018 at 06:21 James Brown <?jlbrown at bordo.com.au
>>> <mailto:jlbrown at bordo.com.au>> wrote:
>>>
>>>
>>> Have tried 2.3.0, 2.3.0.1 &
2018 Aug 27
0
Fatal: setgroups(6) failed: Too many extra groups when authenticating using mysql - macOS 10.13.6
Using mysql for authentication.
Successful username & password gives:
Aug 27 15:10:03 master: Info: Dovecot v2.3.2.1 (0719df592) starting up for imap, pop3 (core dumps disabled)
Aug 27 15:10:50 imap-login: Info: Login: user=<jlbrown at bordo.com.au>, method=PLAIN, rip=::1, lip=::1, mpid=24924, secured, session=<E+DEvWN0xcoAAAAAAAAAAAAAAAAAAAAB>
Aug 27 15:10:50
2018 Dec 04
0
Lda fatal: setgid (102 from userdb lookup) failed
On 4.12.2018 3.27, James Brown via dovecot wrote:
> Sorry if this is a nubbie question, but I?m getting:
>
> lda(jlbrown at bordo.com.au)<4444><QFg5KRHVBBxcEQAAYBwt+A>: Fatal: setgid(102 from userdb lookup) failed with euid=501(jlbrown), gid=20(staff), egid=20(staff): Operation not permitted (This binary should probably be called with process group set to 102 instead of
2010 Jan 12
0
ZFS auto-snapshot in zone
Hello,
I''ve got auto-snapshots enabled in global zone for home directories of all users. Users log in to their individual zones and home directory loads from global zone. All works fine, except that new auto-snapshot have no properties and therefore can''t be accessed in zones.
example from zone:
[~/.zfs/snapshot]:$ ls -Alh
ls: cannot access
2019 Nov 21
0
Samba4 - Printer Drivers install fails
On 21/11/2019 11:03, Julien TEHERY via samba wrote:
> Hi,
>
>
> I have a question about printer drivers management in Samba4 (Samba
> version 4.7.6, Ubuntu 18)
>
> I use MMC to add new drivers to an existing cups printers, and some of
> them are simply refused.
>
> I know the samba4/cups server is operationnal as i'm able to add new
> printers or drivers to
2012 May 29
1
iscsitarget-1.40.20 error during make in CentOS v6.1 x86_64bit
Hello,
Need anyone's help regarding issues I encountered during make on
iscsitarget-1.40.20 which I get from "svn co
https://iscsitarget.svn.sourceforge.net/svnroot/iscsitarget/trunkiscsitarget"
checkout revision 481
Issues where found below after a series of my command, as shown:
[junix at thesisQRMproject iscsitarget]$ make
*cc:
2019 Nov 21
1
Samba4 - Printer Drivers install fails
https://wiki.samba.org/index.php/Setting_up_Samba_as_a_Print_Server#Supported_Print_Server_Back_Ends
Did you:
# net rpc rights grant "SAMDOM\Domain Admins" SePrintOperatorPrivilege -U "SAMDOM\administrator"
Greetings
Daniel
-----Urspr?ngliche Nachricht-----
Von: Rowland penny via samba [mailto:samba at lists.samba.org]
Gesendet: Donnerstag, 21. November 2019 13:01
An:
2019 Jun 25
2
W10 Pro 1903 and Samba with Roaming Profiles: "We can't sign in to your account"
[see also my thread started here
https://social.technet.microsoft.com/Forums/en-US/b653e756-f966-4f8f-9d13-f19a88d4cc5e/w10-pro-1903-and-samba-with-roaming-profiles-quotwe-cant-sign-in-to-your-accountquot?forum=win10itprogeneral]
Hello,
since the upgrade from W10 pro 1809 to 1903 roaming users can still
logon, but they are 'greeted' with the message: "We can't sign in to
your