similar to: imap/pop3-login assertion failed in dovecot 2.2.27 (c0f36b0)

Hello Everyone, I'm having an issue with a recent install of postfix and Dovecot. I can authenticate without any issues for "incoming" mail server, but when I attempt to send an email from the account my client gives an auth error. the server shows that I was authed using plain-auth, which I would also like to change as these machines are accross the open internet. Any help would

On Sat, 6 Oct 2018 11:00:17 -0500, Tommy Lane stated: >Hello Everyone, > I'm having an issue with a recent install of postfix and Dovecot. I can > authenticate without any issues for "incoming" mail server, but when I > attempt to send an email from the account my client gives an auth error. > the server shows that I was authed using plain-auth, which I would also

An embedded and charset-unspecified text was scrubbed... Name: dovecot-n.txt URL: <https://dovecot.org/pipermail/dovecot/attachments/20181006/0f099ba8/attachment-0002.txt> -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: dovecotLog2.txt URL: <https://dovecot.org/pipermail/dovecot/attachments/20181006/0f099ba8/attachment-0003.txt>

Hello, I have this strange situation on nested mailboxes (directories) # dovecot --version 2.2.36 (1f10bfa63) # doveconf -n # 2.2.36 (1f10bfa63): /etc/dovecot/dovecot.conf # Pigeonhole version 0.4.24 (124e06aa) # OS: Linux 3.10.0-693.21.1.el7.x86_64 x86_64 CentOS Linux release 7.5.1804 (Core) mail_access_groups = vmail mail_location = maildir:%h mail_plugins = quota stats quota_clone

Dear Dovecot Team, We would like to use the LDAP iterate for dovecot replication, but I got this error: dovecot: auth-worker(10149): Error: ldap(*): ldap_search(base=ou=mail,o=asd,c=TLD filter=(objectClass=inetMailUser) failed: Size limit exceeded dovecot: replicator: Error: User listing returned failure dovecot: replicator: Error: listing users failed, can't replicate existing data When I

Dear Dovecot Team, We would like to use the LDAP iterate for dovecot replication, but I got this error: dovecot: auth-worker(10149): Error: ldap(*): ldap_search(base=ou=mail,o=asd,c=TLD filter=(objectClass=inetMailUser) failed: Size limit exceeded dovecot: replicator: Error: User listing returned failure dovecot: replicator: Error: listing users failed, can't replicate existing data When I

Package: xen-utils-3.4 Version: 3.4.3~rc6-1 Severity: important blktapctrl doesn't start. This means that none of the tap: disks work (eg tap:aio). It produces this in the log BLKTAPCTRL[6569]: blktapctrl.c:788: blktapctrl: v1.0.0 BLKTAPCTRL[6569]: blktapctrl.c:790: Found driver: [raw image (aio)] BLKTAPCTRL[6569]: blktapctrl.c:790: Found driver: [raw image (sync)]

Hi, Trying to keep abusive/buggy IMAP clients at bay on a number of Dovecot proxy servers, I've reconfigured them to use "mail_max_userip_connections = 50" in the "protocol imap" section, followed by restarting Dovecot. Yet, I'm still seeing 160+ established connections from a single IP address for the same email account. Am I missing anything? # 2.2.27

sieveshell cannot connect as any user Mar 14 23:53:45 srv1 saslauthd[22038]: do_auth : auth failure: [user=root] [service=sieve] [realm=] [mech=shadow] [reason=Unknown] Mar 14 23:53:45 srv1 sieve[22047]: Password verification failed Mar 14 23:53:45 srv1 perl: No worthy mechs found Mar 15 00:01:54 srv1 saslauthd[22164]: do_auth : auth failure: [user=root] [service=sieve] [realm=]

Hi, mail_max_userip_connections is only enforced at the backend level. The setting has no effect on proxy. If you want to force the limit then you can only do it in the backend. Sami > On 9 Mar 2017, at 12.05, Adi Pircalabu <adi at ddns.com.au> wrote: > > Quick follow-up: updated the proxies to 2.2.28, but I still couldn't find a way to limit the inbound IMAP connections per

https://bugzilla.samba.org/show_bug.cgi?id=13266 Bug ID: 13266 Summary: Writing of files to Apple's new "AP" controller model SSD's takes 4x longer. Product: rsync Version: 3.1.3 Hardware: x64 OS: Mac OS X Status: NEW Severity: critical Priority: P5

Hello everyone, I am trying to send a mail to newly autocreated users, using the welcome plugins, however, i am get unable to pipe user information correctly to the script, acording to the wiki the scripts are called just as the quota warnig scripts. Also, every time that a try something new i have created a new user...... is a pain. what can i do to test this without to create a new user

Quick follow-up: updated the proxies to 2.2.28, but I still couldn't find a way to limit the inbound IMAP connections per IP & username. I know "mail_max_userip_connections" limit works for the mail stores, but it doesn't seem to have any effect on the proxies. I'm using a mix of Dovecot & Courier-IMAP servers as backends. Basically I need to find a way to enforce

Thanks, I thought this might be the case. Is there any solution to enforce this on the proxy? If not, will a feature request be considered anytime soon? I see the proxies as the first line of defense against IMAP "abuse" and I think it's consistent having the same configurable option available on both backends and the proxies. --- Adi Pircalabu On 14-03-2017 20:17, Sami Ketola

hi i am maintainer of archicad 1, I receive messages about 2 bugreports... i did not know what should i do... can anybody explaine what should i do with this... i went with link that was in message i have 2 bugreport 13266, 13283 13266 ArchiCad 11 installer: Crashes after extraction (Java related?) UNCONFIRMED View [delete] Yes 13283 ArchiCAD 11 cannot install, overflow of free space?

Hi, I just noticed a crash in Dovecot (2.2.27) on Debian with the Debian version 1:2.2.27-2~bpo8+1: Jan 28 07:50:42 srv1 dovecot: imap(yyy at xxx.de): Panic: file mail-storage.c: line 2170 (mailbox_save_context_reset): assertion failed: (ctx->copying_via_save) Jan 28 07:50:42 srv1 dovecot: imap(yyy at xxx.de): Error: Raw backtrace: /usr/lib/dovecot/libdovecot.so.0(+0x97d8e) [0x7f3e7fab8d8e]

On Thu, Sep 3, 2015 at 11:03 AM, Greg Stark <stark at mit.edu> wrote: > On Thu, Sep 3, 2015 at 6:54 PM, Kostya Serebryany <kcc at google.com> wrote: > > Looks correct. > > Ah! With a fresh pair of eyes it's obvious what was wrong. I had > compiled everything with sanitize-coverage except the Fuzzer code > itself but that included the file with the wrapper

https://bugzilla.samba.org/show_bug.cgi?id=6569 Summary: chmod-temp-dir fails on QNX Product: rsync Version: 3.1.0 Platform: Other OS/Version: Windows XP Status: NEW Severity: normal Priority: P3 Component: core AssignedTo: wayned at samba.org ReportedBy: mkraai at beckman.com

http://bugs.freedesktop.org/show_bug.cgi?id=14491 Summary: enabling randr-1.2 support causes LVDS unknown config bits error when starting the X server Product: xorg Version: git Platform: x86 (IA32) OS/Version: Linux (All) Status: NEW Severity: normal Priority: medium Component:

Bugs item #14298, was opened at 2007-09-28 10:23 You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=411&aid=14298&group_id=85 Category: None Group: None Status: Open Resolution: None Priority: 3 Submitted By: Lars Olsson (lasso) Assigned to: Nobody (None) Summary: windows-api 0.2.0/windows-pr 0.7.1 causes segfault with require of win32/file Initial Comment: