In the absence of an [sasl_]auxprop_plugins statement, all plugins will be
queried. For example, running pluginviewer (or saslpluginviewer on debian)
should typically list sasldb if it's installed on your system.
The canon_user plugins and auxprop plugins are coded within the same code,
and so ar
On 09/29/16 14:27 +, Shawn Bakhtiar via Info-cyrus wrote:
trying to get rid of some emails that have large attachments (i.e. videos sent
over email, or cd images, etc...)
Would it be proper to
rm -rf /var/spool/imap/u/username/mailbox/4321.
then
reconstruct -rf user.username
Or is there
On 09/24/16 17:28 +0200, jesper--- via Info-cyrus wrote:
The following sample prompts for entering the password after ones actually
did enter the password. 1) Why is that e.g why does this sample write
"please enter your password: " after the password is entered, and then
exits?
The authenticati
On 06/23/16 16:49 +0200, Eric Luyten via Info-cyrus wrote:
On Wed, June 22, 2016 6:02 pm, Dan White wrote:
To enable SASL LOGIN support, add 'LOGIN' to your sasl_mech_list. Don't
confuse login with pre-sasl user/pass authentication.
If Office 365 isn't performing TLS, you'll need to configure
s
On 06/22/16 17:28 +0200, Eric Luyten via Info-cyrus wrote:
All,
After trying for a couple of days I have come to the conclusion
that the Office 365 IMAP import tool uses the LOGIN authentication
mech while Cyrus requires PLAIN or stronger for proxying to work.
Even when only announcing AUTH=PL
On 04/06/2016 01:32 PM, Dan White wrote:
On 04/06/16 13:20 -0500, Jack Snodgrass via Info-cyrus wrote:
Is there a documented process for taking a system from: Cyrus
v2.2.13 to Cyrus v2.4.17
Check the upgrade instructions here:
https://cyrusimap.org/docs/cyrus-imapd/2.5.3/install-upgrade.php
On 04/06/16 13:20 -0500, Jack Snodgrass via Info-cyrus wrote:
Is there a documented process for taking a system from: Cyrus v2.2.13
to Cyrus v2.4.17
I have rsync'd the mail between the two systems.
/usr/lib/cyrus/bin/reconstruct did NOT magically convert the system
from the old to the new.
On 03/28/16 14:16 -0300, francis picabia via Info-cyrus wrote:
We have migrated all email on a server to a cloud email platform.
The users were notified by email beforehand, but hundreds are still
connecting to the standard IMAP service. They may not
even remember they have set up devices to con
On 11/12/15 22:04 +0100, Daniel Schröter wrote:
On 11/12/2015 09:47 PM, Dan White wrote:
Are you using fetchmail to deliver these messages?
Yes, and that's the problem. Thanks very much.
My provider doesn't set the "Envelope-to" correct for more then one
recipient :-(
The envelop to is like
On 11/12/15 21:22 +0100, Daniel Schröter wrote:
Hello,
On 11/11/2015 10:13 PM, Dan White wrote:
What does syslog say?
Nothing special. Mail to cyrus.test and cyrus.test2. But only
cyrus.test2 appears in the logs:
I'm reordering, to make this easier to follow:
Nov 12 21:09:45 fetchmail[6236
On 11/11/15 22:02 +0100, Daniel Schröter via Info-cyrus wrote:
I deliver mail to cyrus (2.4.12) with postfix (2.9.6) under ubuntu by lmtp.
If a mail has multiple recipient just one recipient gets the mail. No
error occur in logs by bounced mail. AFAIK cyrus should generate
hardlinks for this(?).
On 11/06/15 10:17 +, Sunny via Info-cyrus wrote:
Hi
What is the difference between
authentication failure: checkpass failed
I would guess this is produced for non-sasl user/pass imap authentications,
or perhaps apop.
and
authentication failure: Password verification failed
Produced b
12 matches
Mail list logo
