Displaying 20 results from an estimated 10000 matches similar to: "Pigeonhole proxy errors"
2013 Jul 03
2
LMTP Proxy
Trying to figure out Proxying with LMTP to a few back end storage servers
for quota checking before accepting email delivery on the front end nodes.
If I connect to the back end server directly via telnet, everything works
great.
If I use a front-end server to proxy to the back end server, I don't get
the same result.
Running 2.2.4 on both front and back end servers.
Any help would be
2010 Sep 08
3
Pigeonhole and Dovecot2 with custom config file
I start my dovecot with the "-c /path/to/custom/config" option so I
can run multiple instances. Been trying out 2.0.1 so I can upgrade my
boxes cleanly, but I require managesieve. So after installing the
latest sources of the Pigeonhole plugin, I'm getting this when trying
to start dovecot:
# /usr/local/sbin/dovecot -c /usr/local/etc/dovecot/dovecot_custom.conf
managesieve(root):
2015 May 16
4
charset_to_utf8 assertion of remaining src_size
On 16 May 2015, at 09:39, Xin Li <delphij at delphij.net> wrote:
>
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA512
>
> Hi,
>
> On 5/15/15 10:58, Xin Li wrote:
>> Hi,
>>
>> I have seen the following assertion fails on my own mail server
>> (indexer-worker):
>>
>> Panic: file charset-iconv.c: line 132 (charset_to_utf8):
2014 Oct 27
1
doveadm throws Panic: file dsync-mailbox-tree-fill.c: line 65
Running 2.2.15 on FreeBSD 10.0.
Forcing replication with: doveadm replicator replicate -f user at host.com
on one user that I've seen some syslogs show up to see what's going on.
Other users are fine.
When I run the above command on the one user it produces a core dump. See
below for syslog output and full backtrace:
syslog output:
Oct 26 22:44:09 d3cstorage dovecot: dsync-server(user
2007 Feb 19
2
NTLM oddities
Started implementing the MasterUser changes to my config files so I can
finally offer SPA for pop3/imap.
Things are working fine with the MasterUser (horray!), however one of my
guys started using SPA with Outlook Express and started getting another
users mailbox.
Turns out to be related to NTLM. His Outlook express is configured for the
username of 'johnsmith'. However, you'll see
2007 Jul 25
1
Errors logging in
Out of the blue my proxy installations started showing this:
dovecot: login: tried to change state 2 -> 2 (if you can't login at all, see
src/lib/fdpass.c)
Nobody can login.
Running 1.0.0 on the proxy and 1.0.2 on my storage boxes. Anybody have any
insights?
-c
2013 Jul 11
1
Multiple Folders Continually Auto-Created
I've had reports of a number of clients running Outlook 2011 on Mac where
they have quite a few folders with the same name appended by multiple
"1"s. So far I've only narrowed it down to Outlook 2011 on Mac. We've
been in the process of migrating to sdbox on a new server from maildir
using dsync backup.
Example folder structure:
INBOX
INBOX 1
INBOX 1 1
INBOX 1 1 1
INBOX 1
2014 Oct 28
1
dsync-server throwing Resource temporarily available
Running 2.2.15 on FreeBSD 10.0 with two back end storage boxes using TCP to
sync.
Seeing a couple of users that always seem to be throwing these kind of
errors in the logs:
dovecot: dsync-server(user at host.com): Error:
write(/var/run/dovecot/replicator-doveadm) failed: Resource temporarily
unavailable
Just wondering what's the proper course of action to fix it?
Thanks.
2006 Dec 17
1
Proxy with MasterUser + Authentication issues
Per Timo's direction, I decided to give the MasterUser a try in connecting
my proxy to my destination server.
This might allow for the use of 'secure password' for my clients that like
to check that box by default.
A couple of problems I'm running into running RC15:
#1: My Proxy's SQL password_query line:
password_query = SELECT a.clearpasswd AS password, v.storeIP AS host,
2006 Dec 15
1
Proxy MD5/NTLM requests not working
Having some problems with setting up a proxy with any authentication
mechanisms other than PLAIN. My passwords are
stored in my database in plaintext (and MD5), so I figure I could use
whatever scheme I want. Using the latest RC15. MySQL for the backend.
This first one is CRAM-MD5. It fails (scheme_r != NULL??) then PLAIN tries
to take over, but the auth server is restarting:
Info:
2011 Jan 12
2
Problem after migration dovecot 1.2 -> dovecot 2.0
I have migrated from dovecot 1.2 to dovecot 2.0. When I connect via
telnet to 110 port of the dovecot server the client hangs:
telnet 192.168.4.80 110
Trying 192.168.4.80...
/Connected to 192.168.4.80.
Escape character is '^]'./
In syslog I got the following error:
/Jan 12 12:14:44 buzon dovecot: imap-login: Error: auth: connect(login)
in directory / failed: Permission denied
2007 Feb 19
1
Weird Issues with latest nightly (pre-rc23)
Just updated one of my proxy boxes to the latest nightly (20070217),
restarted the dovecot process and got a bit of errors showing up for each
pop3/imap connection.
Feb 19 11:14:00 marbella dovecot: pop3-login: Login: user=<user1 at host.com>,
method=PLAIN, rip=209.33.217.218, lip=204.17.177.60
Feb 19 11:14:00 marbella dovecot: POP3(user1 at host.com): Set pop3_uidl_format
in config file
2015 May 22
1
charset_to_utf8 assertion of remaining src_size
On 05/22/15 13:18, Cassidy Larson wrote:
> We're using FreeBSD 10.1
I see. Yes that's the same problem I have seen.
There is a behavioral difference (I think it's a FreeBSD bug) between
FreeBSD's iconv(3) and GNU implementation, and there is arguably a bug
with Dovecot that iconv(3) state should be reset for each multipart
part. The two together would trigger the problem
2017 May 01
2
Problem with Pigeonhole/Sieve
Hi,
I am trying to configure Pigeonhole to get filters in RoundCube working.
Unfortunately I am getting following error in DoveCot log instead:
May 01 14:35:41 managesieve-login: Error: auth: connect(login) in
directory / failed: Permission denied (euid=248(<getpwuid() error>)
egid=248(<getgrgid() error>) missing +x perm: /, we're not in group 202,
dir owned by 0:202
2007 Jul 30
2
dovecot-auth core dumps
Seeing a few core dumps on my two proxy servers with dovecot-auth since
upgrading to 1.0.2.
Example:
Jul 30 13:36:51 alora kernel: pid 20234 (dovecot-auth), uid 0: exited on
signal 11 (core dumped)
Jul 30 13:36:51 alora dovecot: child 20234 (auth) killed with signal 11
Jul 29 19:17:08 marbella kernel: pid 70627 (dovecot-auth), uid 0: exited on
signal 11 (core dumped)
Jul 29 19:17:08 marbella
2010 Sep 28
1
problems and dovecot & manegesieve
Hello,
my server is working with dovecot-2.0.2+dovecot-2.0-pigeonhole-0.2.0.
but if activate managesieve, is not listening in 4190!
any help?
I setup this:
----------------------------------
##
## ManageSieve specific settings
##
# Service definitions
service managesieve-login {
inet_listener sieve {
port = 4190
}
#inet_listener sieve_deprecated {
# port = 2000
#}
2010 Oct 25
1
Prevent dovecot.sieve.log logs
Hello,
When an account overquota happens, a log is generated:
/var/lib/imap/sieve/username/dovecot.sieve.log
Is there a way to prevent this?
My `dovecot -n` :
################################################################################
# 2.0.6 (a7d99b69523a): /etc/dovecot/dovecot.conf
# OS: Linux 2.6.35-23-server x86_64 Ubuntu 10.04.1 LTS
auth_master_user_separator = *
auth_mechanisms =
2015 Aug 04
2
Dovecot sieve pigeonhole permission
Hello,
I'm running dovecot in a classical vmail.vmail setup with pigeonhole and
LMTP. Permission worked well in the initial setup but currently (maybe
after Fedora 22 update) I'm having the following permission issue:
lmtp(root): Error: 7fPZFOL9wFXePQAABcdabc: sieve: binary open: failed to
open: open(/etc/dovecot/sieve_after.svbin) failed: Permission denied
(euid=9999(vmail)
2010 Sep 22
1
Sieve error on Quota full (Dovecot 2.0.3)
Just switched my storage boxes to 2.0.3 with Pigeonhole. Noticing for
those that have quota fulls, my syslog is getting full of errors from
sieve:
dovecot: lda(user at host.com): Error: sieve: script
/data/mail/host.com/user at host.com//.dovecot.sieve failed with
unsuccessful implicit keep (user logfile
/data/mail/host.com/user at host.com//.dovecot.sieve.log may reveal
additional details)
2006 Dec 23
1
customizable idle login timeouts?
We're in the process of migrating from mbox over to maildir.
I'm running into a problem with the proxy and timeouts. Appears the idle
timeout is set to 60 seconds. This is a bit too low for some of our large
mbox files :(
Any plans on adding the:
#define CLIENT_LOGIN_IDLE_TIMEOUT 60
#define AUTH_REQUEST_TIMEOUT
to the .conf file to be tunable on the fly?
I ended up just patching the