[Dovecot] Disabling access for one user
I'm converting my system from mbox to Maildir one user at a time, and I'd like to disable access for the user I'm working on. Is there a way to tell Dovecot to lock out a specific user? Perhaps with a control file in the home directory?
At the same time, how can I get sendmail+procmail to tempfail incoming messages for one user until I'm done?
On Aug 7, 2008, at 1:17 PM, Kenneth Porter wrote:
I'm converting my system from mbox to Maildir one user at a time,
and I'd like to disable access for the user I'm working on. Is there
a way to tell Dovecot to lock out a specific user? Perhaps with a
control file in the home directory?
http://wiki.dovecot.org/Authentication/RestrictAccess (deny passwd- file for example).
At the same time, how can I get sendmail+procmail to tempfail
incoming messages for one user until I'm done?
If you used Dovecot's deliver, the deny passwd should have worked, but
I've no idea about procmail.
--On Thursday, August 07, 2008 3:37 PM -0400 Timo Sirainen tss@iki.fi wrote:
If you used Dovecot's deliver, the deny passwd should have worked, but I've no idea about procmail.
I'll note that I'm using procmail because of the ability to filter and run SpamAssassin from it. Does the Dovecot LDA provide the equivalent? (I know there's Sieve, though haven't looked into how one uses it.) If so, how hard is it to migrate my procmailrc files?
On Aug 7, 2008, at 3:55 PM, Kenneth Porter wrote:
--On Thursday, August 07, 2008 3:37 PM -0400 Timo Sirainen
tss@iki.fi wrote:If you used Dovecot's deliver, the deny passwd should have worked,
but I've no idea about procmail.I'll note that I'm using procmail because of the ability to filter
and run SpamAssassin from it. Does the Dovecot LDA provide the
equivalent? (I know there's Sieve, though haven't looked into how
one uses it.) If so, how hard is it to migrate my procmailrc files?
Typically you'd run SpamAssassin first and Dovecot deliver after that.
Sieve doesn't allow executing external binaries.
I'll note that I'm using procmail because of the ability to filter and run SpamAssassin from it.
Typically you'd run SpamAssassin first and Dovecot deliver after that.
Is anyone here doing this for virtual users who could describe what they did?
Bonus points for actual configuration files :-)
Thanks,
/jordan
Jordan Hayes wrote:
I'll note that I'm using procmail because of the ability to filter and run SpamAssassin from it.
Typically you'd run SpamAssassin first and Dovecot deliver after that.
Is anyone here doing this for virtual users who could describe what they did?
Bonus points for actual configuration files :-)
Thanks,
/jordan What SMTP server are you running?
-- Daniel
Typically you'd run SpamAssassin first and Dovecot deliver after that.
Is anyone here doing this for virtual users who could describe what they did?
Bonus points for actual configuration files :-)
What SMTP server are you running?
Sendmail.
Hello!
You can use sendmail/MailScanner/Spamassassin/deliver/procmail.
Maybe you find my procmail patch usefull. http://markmail.org/message/v4gga3ba75xqemra http://www.dovecot.org/list/dovecot/2007-March/020787.html
If you need any help just let me know it.
BTW: Timo please fix the bugs regarding deliver and dovecot index bugs as already discussed. >Scanning large mailbox folders takes a lot of time. If you need any help just let me know it.
Ciao, Gerhard
On Tue, 12 Aug 2008, Jordan Hayes wrote:
I'll note that I'm using procmail because of the ability to filter and run SpamAssassin from it.
Typically you'd run SpamAssassin first and Dovecot deliver after that.
Is anyone here doing this for virtual users who could describe what they did?
Bonus points for actual configuration files :-)
Thanks,
/jordan
On Aug 13, 2008, at 12:02 AM, Gerhard Wiesinger wrote:
BTW: Timo please fix the bugs regarding deliver and dovecot index
bugs as already discussed. >Scanning large mailbox folders takes a
lot of time. If you need any help just let me know it.
I was never able to reproduce the problem myself, and the last time we
found a solution to one problem it was a configuration mistake in your
end. So I'm a bit afraid if I again spend a lot of time with it we'll
only find out that it's a configuration issue again.. Or possibly an
issue in filesystem/something.
Hello Timo!
A configuration issue as we had with the config discussed below can be definitly barred.
locate only finds somehting in /home/gerhard/Mail/.imap/ which is correct.
Config: ~/.imap 3 > ls -l total 0 lrwxrwxrwx 1 gerhard users 30 Jun 13 22:30 INBOX -> /home/gerhard/Mail/.imap/INBOX
# Users should have access to the whole home directory mail_location = mbox:~:INBOX=/var/mail/%u
deliver section: # Mail folders should be in ~/Mail mail_location = mbox:~/Mail:INBOX=/var/mail/%u
How can I make a more consistent configuration with namespaces? To avoid the symlink we might include: INBOX_CACHE_DIR=~/Mail
Do you have the warnings patch (inconsitent sizes/timesptamps between index and filesystem) running at your servers, too? Do you get warnings?
Maybe you can include these warnings in the normal release and some other people have the same problems.
I think the used filesystem ext3 is rock solid.
Ciao, Gerhard
On Wed, 13 Aug 2008, Timo Sirainen wrote:
On Aug 13, 2008, at 12:02 AM, Gerhard Wiesinger wrote:
BTW: Timo please fix the bugs regarding deliver and dovecot index bugs as already discussed. >Scanning large mailbox folders takes a lot of time. If you need any help just let me know it.
I was never able to reproduce the problem myself, and the last time we found a solution to one problem it was a configuration mistake in your end. So I'm a bit afraid if I again spend a lot of time with it we'll only find out that it's a configuration issue again.. Or possibly an issue in filesystem/something.
participants (5)
-
Daniel L. Miller
-
Gerhard Wiesinger
-
Jordan Hayes
-
Kenneth Porter
-
Timo Sirainen