Displaying 20 results from an estimated 1000 matches similar to: "IMAP ALERT on reason/nologin"
2018 Jan 11
0
login failure "reason" not returned (dovecot-2.2.32)
Hello,
In the past (older dovecot versions) I've tuned the SQL "password_query"
of our mail server so that when the user has the account blocked for
some reason (expired, need password change, etc.) the query returns
nologin=1 and a verbose reason like reason="Your account is expired
please change the password" and it worked very well with IMAP clients.
I'm now
2018 Sep 04
0
Specifying other mail_attachment_dir for namespace
Hello,
I have a Dovecot setup where I need to allow users to access a snapshot
of their messages (when they complain about missing messages/folders
deleted by mistake).
From time to time the system does a LVM snapshot of the volume holding
the mailboxes and sis storage and that messages are available via a
"special" namespace.
The problem is the messages that references
2011 Jul 25
1
Pigeon Sieve, redirect action and SPF
Since I've upgraded to dovecot 2.0.13 + Pigeonhole 0.2.3 (Gentoo
package) I've received a few complains of users about rejected messages.
Investigating the problem, I've seen that when the external sender
server publishes SPF information, when some message is sent from there
to one of my users that has a Sieve redirect action active to another
external system (that does SPF
2018 Jan 12
0
Questions about SPECIAL-USE IMAP extension
Is this what you are looking for?
https://wiki2.dovecot.org/Plugins/MailboxAlias
It seems already be implemented...
regards.
On 2018/01/12 14:25, Tanstaafl wrote:
> On Fri Jan 12 2018 01:29:37 GMT-0500 (Eastern Standard Time), Steffen
> Kaiser <skdovecot at inf.h-brs.de> wrote:
>> On Thu, 11 Jan 2018, Joseph Tam wrote:
>>> I'd like to configure my dovecot
2018 Jan 12
2
Questions about SPECIAL-USE IMAP extension
On Fri Jan 12 2018 01:29:37 GMT-0500 (Eastern Standard Time), Steffen
Kaiser <skdovecot at inf.h-brs.de> wrote:
> On Thu, 11 Jan 2018, Joseph Tam wrote:
>> I'd like to configure my dovecot service to use the IMAP SPECIAL-USE
> well, in my experience SPECIAL-USE is just a suggestions to clients. Check
> RFC 6154 for MUSTs, you'll find only few. Hence, how the client
2007 Feb 09
1
HP DL380 G2 does not boot off local disk from PXE boot menu
Hi, all:
I can't make my HP DL380 G2 servers to boot off local disk by using
"default local" line in my PXE boot menu.
For fully automated server setups, I have configured all my DL380
servers to always do PXE boot. By manipulating the default boot option
in boot menu, I can control a server whether to install a new OS via
kickstart or just boot off local disk. This scheme works
2016 Nov 21
0
nologin + reason -> logging reason
On Nov 21, 2016, at 7:39 AM, Arkadiusz Mi?kiewicz <arekm at maven.pl> wrote:
> reason is the only thing in maillog that allows to distinguish why user was
> not allowed to log in.
Um? the only thing? How about where you set the reason in the first place?
I think the assumption with nologin is that the admin knows the reason, especially considering that nologin is drastic and is
2016 Nov 21
1
nologin + reason -> logging reason
On Monday 21 of November 2016, @lbutlr wrote:
> On Nov 21, 2016, at 7:39 AM, Arkadiusz Mi?kiewicz <arekm at maven.pl> wrote:
> > reason is the only thing in maillog that allows to distinguish why user
> > was not allowed to log in.
>
> Um? the only thing? How about where you set the reason in the first place?
That "first" place is constantly changing
2016 Nov 21
0
nologin + reason -> logging reason
On 21 Nov 2016, at 16.39, Arkadiusz Mi?kiewicz <arekm at maven.pl> wrote:
>
>
> Hi.
>
> I'm using nologin with own reason [1]. That works fine. For example pop3
> client gets nice message like "-ERR [AUTH] Account is locked. Please contact
> support."
>
>
> Unfortunately maillog lacks information details about why user was not allowed
>
2016 Nov 21
4
nologin + reason -> logging reason
Hi.
I'm using nologin with own reason [1]. That works fine. For example pop3
client gets nice message like "-ERR [AUTH] Account is locked. Please contact
support."
Unfortunately maillog lacks information details about why user was not allowed
to log in.
pop3-login: Disconnected (auth failed, 1 attempts in 2 secs): user=<testuser>,
method=LOGIN, rip=1.1.1.1, lip=2.2.2.2,
2008 Mar 20
0
[RFC/PATCH 10/15] kvm-s390: intercepts for diagnose instructions
From: Carsten Otte <cotte at de.ibm.com>
From: Christian Borntraeger <borntraeger at de.ibm.com>
This patch introduces interpretation of some diagnose instruction intercepts.
Diagnose is our classic architected way of doing a hypercall. This patch
features the following diagnose codes:
- vm storage size, that tells the guest about its memory layout
- time slice end, which is used by
2010 Mar 10
2
PGSQL application
Does the application PGSQL has been removed from Asterisk? Couldn't find it on Asterisk source and addons.
Atenciosamente,
Vin?cius Fontes
Gerente de Seguran?a da Informa??o
Canall Tecnologia em Comunica??es
Passo Fundo - RS - Brasil
+55 54 2104-7000
Information Security Manager
Canall Tecnologia em Comunica??es
Passo Fundo - RS - Brazil
+55 54 2104-7000
2010 Jul 05
0
Reinvite to alaw after T.38 reception
I'm having issues with T.38 on Asterisk 1.6.2.8. A few lines are received OK and then I get only garbage. I'm using ReceiveFAX() provided by app_fax to receive the faxes.
After talking to the engineers on the telco, they said Asterisk is sending a REINVITE to alaw after the T.38 reception is complete, and that could be the cause of the problems.
I personally am not totally convinced of
2005 Apr 05
2
how to automatically create user homedir
Hello all,
Im using samba 3.0.11 and openldap.
I need a way to auto create my users home when they connect to their HOME share.
How can i do that?!
PS: i tried the preexec directive but it didnt work! :o|
Thanks!
+----------------------------------------
| Lu?s Miguel Ferreira da Silva
| Network Administrator @ISPGaya
| Instituto Superior Polit?cnico Gaya
| Rua Ant?nio Rodrigues da Rocha,
2013 Feb 03
0
CISTI'2013 Doctoral Symposium - CFP, Lisbon; Deadline: February 15
***************************************************************************************************
CISTI'2013 DOCTORAL SYMPOSIUM
8th Iberian Conference on Information Systems and Technologies
Lisbon, Portugal, June 19 - 23, 2013
http://www.aisti.eu/cisti2013/index.php?option=com_content&view=article&id=64&Itemid=68&lang=en
2013 Feb 03
0
CISTI'2013 Doctoral Symposium - CFP, Lisbon; Deadline: February 15
***************************************************************************************************
CISTI'2013 DOCTORAL SYMPOSIUM
8th Iberian Conference on Information Systems and Technologies
Lisbon, Portugal, June 19 - 23, 2013
http://www.aisti.eu/cisti2013/index.php?option=com_content&view=article&id=64&Itemid=68&lang=en
2007 Apr 18
2
[PATCH] Clean up x86 control register and MSR macros (corrected)
This patch is based on Rusty's recent cleanup of the EFLAGS-related
macros; it extends the same kind of cleanup to control registers and
MSRs.
It also unifies these between i386 and x86-64; at least with regards
to MSRs, the two had definitely gotten out of sync.
Signed-off-by: H. Peter Anvin <hpa@zytor.com>
diff -urN --exclude='o.*' --exclude '*~'
2007 Apr 18
2
[PATCH] Clean up x86 control register and MSR macros (corrected)
This patch is based on Rusty's recent cleanup of the EFLAGS-related
macros; it extends the same kind of cleanup to control registers and
MSRs.
It also unifies these between i386 and x86-64; at least with regards
to MSRs, the two had definitely gotten out of sync.
Signed-off-by: H. Peter Anvin <hpa@zytor.com>
diff -urN --exclude='o.*' --exclude '*~'
2007 Apr 18
1
No subject
[PATCH] Clean up x86 control register and MSR macros
This patch is based on Rusty's recent cleanup of the EFLAGS-related
macros; it extends the same kind of cleanup to control registers and
MSRs.
It also unifies these between i386 and x86-64; at least with regards
to MSRs, the two had definitely gotten out of sync.
Signed-off-by: H. Peter Anvin <hpa@zytor.com>
diff -urN
2007 Apr 18
1
No subject
[PATCH] Clean up x86 control register and MSR macros
This patch is based on Rusty's recent cleanup of the EFLAGS-related
macros; it extends the same kind of cleanup to control registers and
MSRs.
It also unifies these between i386 and x86-64; at least with regards
to MSRs, the two had definitely gotten out of sync.
Signed-off-by: H. Peter Anvin <hpa@zytor.com>
diff -urN