On 3/17/23 14:55, Gedalya wrote:
That's the setting you want. In IMAP / dovecot context, "mailbox" means
"folder".
The basic directory structure for an account, with INBOX and the various mailboxes
("folders") as defined in your namespace / mailbox configuration where auto =
[create|subscribe
This may be more of a CPanel issue than Dovecot but CPanel uses Dovecot
and not sure if this is a knob we have available in Dovecot or we need
to reach out to Cpanel directly to see if this is some custom code they
added to their distros.
Anyway, W/R/T emails sent with dtails/ + addresses ie:
Recently moving to newer storage platforms for mailbox storage so looking at
moving mounts from NFSv3 with lots of issues with locking and caching to NFSv4.
There seems to be a lot of benefits to v4 along with some other new features,
namely “delegation”.
So the question boils down to, to deleg
On Aug 5, 2016, at 12:12 PM, Aki Tuomi wrote:
>
> The response time will be same anyways.
>
> Anyways. It is better to enforce this kind of thing when users define the
> password than during login.
The idea would be to mitigate unnecessary database dips for password that don’t
clearly pass
Is there a way to configure Dovecot to perhaps filter/enforce which passwords
are accepted before authenticating?
Ie: Reject immediately (without a database lookup) if password is not X
characters in length?
?
--
Robert
inoc.net!rblayzor
XMPP: rblayzor.AT.inoc.net
PGP Key: 78BEDCE1 @ pgp.mit
> This doesn't make much sense. Is it reproducible?
I’m not sure what triggered it exactly, was just completely random. Looking in
the logs there was nothing at the time.
If it happens again (with similar trace) will follow-up.
--
Robert
inoc.net!rblayzor
XMPP: rblayzor.AT.inoc.net
PGP Key: 78
pid 31943 (dovecot), uid 0: exited on signal 11 (core dumped)
dovecot --version
2.2.21 (5345f22)
uname -a
FreeBSD 10.3-BETA2 #0 r295966M: amd64
bt full
#0 0x0008008eb037 in t_push (marker=0x0) at data-stack.c:133
133 data-stack.c: No such file or directory.
in data-stack.c
On Jan 31, 2016, at 4:26 AM, Timo Sirainen wrote:
>
> There's no way it can crash here, unless something's badly broken. Either a
> buggy compiler or maybe memory corruption earlier in the process. Can you
> reproduce it? Can you run it via valgrind?
I’ve been tracking this with an open bug i
dovecot --version
2.2.21 (5345f22)
FreeBSD 10.2-RELEASE-p11 FreeBSD 10.2-RELEASE-p11 #0 r294908M: amd64
Core was generated by `dovecot'.
Program terminated with signal 11, Segmentation fault.
Reading symbols from /usr/local/lib/dovecot/libdovecot.so.0...done.
Loaded symbols for /usr/local/lib/
dovecot --version
2.2.21 (5345f22)
FreeBSD 10.2-RELEASE-p10 FreeBSD 10.2-RELEASE-p10 #0 r294322M:
having repeated core dumps on imap process… autoexpunge issue?
GNU gdb 6.1.1 [FreeBSD]
Copyright 2004 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public Lic
On Dec 23, 2015, at 3:17 AM, Timo Sirainen wrote:
>
> So this keeps finding mails that aren't being automatically deleted? (You
> were testing with savedbefore, right?) :
>
> doveadm search -u user@domain mailbox Trash savedbefore 2w
>
> If that works, try if it happens to work with mailbox_li
On Dec 22, 2015, at 2:56 PM, Teemu Huovila wrote:
>
> The autoexpunge feature does not check the \Deleted flag.
>
> Are any errors logged in "doveadm log errors"? Could you post your complete
> output of doveconf -n please.
That’s what I thought. If I run expunge from doveadm manually, it wi
> On Dec 22, 2015, at 9:49 AM, Dominik Breu wrote:
> the autoexpunge feature only removes mails wich have the \Delete Flag so no
> deletion of mails wich doesn't have this Flag(see
> https://tools.ietf.org/html/rfc4315#section-2.1 or
> http://wiki2.dovecot.org/Tools/Doveadm/Expunge)
>
> you c
I have configured autoexpunge on some folders:
namespace inbox {
inbox = yes
location =
mailbox Junk {
auto = subscribe
autoexpunge = 30 days
special_use = \Junk
}
mailbox Trash {
auto = subscribe
autoexpunge = 2 weeks
special_use = \Trash
}
prefix =
separat
dovecot -n
# 2.2.19: /usr/local/etc/dovecot/dovecot.conf
# Pigeonhole version 0.4.9 (357ac0a0e68b+)
# OS: FreeBSD 10.2-RELEASE-p7 amd64
doveconf: Warning: Dovecot was last started using /etc/dovecot/dovecot.conf,
but this config is /usr/local/etc/dovecot/dovecot.conf
auth_cache_size = 10 M
auth_c
On May 28, 2015, at 4:24 PM, l...@airstreamcomm.net wrote:
>
> A bit off topic, but I was wondering if anyone here has a solution for
> centrally managing sieve for multiple users from a custom web application?
> We would like to implement pigeonhole sieve on our dovecot cluster, however
> we
Is it possible the Sieve/ManageSieve documentation on the Wiki can be cleaned
up? It's incredibly confusing now. Some of the Sieve configuration information
says certain options are deprecated, but then the example on how to configure
it uses the deprecated options rather than what they *should*
On Jan 13, 2015, at 8:44 PM, Reindl Harald wrote:
>> A 5xx reject would let the sending server know the message could not be
>> delivered due a failure
>
> which belongs in the MTA and not the LDA
>
>> (ie: user policy rejection, without receiving MTA generating NDR
>> backscatter).
>> I would
On Jan 13, 2015, at 8:30 PM, Reindl Harald wrote:
>
> so what you want in your OP is just DISCARD in a sieve script and there is no
> point in "Using Dovecot LMTP it would be more optimal to kick a 5xx back"
> when the desired result is DISCARD
>
> why do you want the burden of keep the SMTP s
On Jan 13, 2015, at 7:34 PM, Reindl Harald wrote:
>
> and what would that change?
> nothing if you think about how mail works!
>
> * the MTA receives the message
> * the MTA confirms with 2xx status code
> * later the delivery server rejects
> * the MTA *must* create a bounce
>
> just don't rej
Currently pigeonhole supports reject which would generate a NDR for each
message. (If I understand the current documentation)
Using Dovecot LMTP it would be more optimal to kick a 5xx back to the primary
MTA to reject the delivery rather than generating more back scatter NDRs.
Anyone know if t
On Jan 1, 2015, at 9:58 AM, Robert Blayzor wrote:
>
>> Hmm. This smells like a bug. I notice that your modification times of
>> the .sieve and .svbin file are exactly the same (that is somewhat
>> unusual). I'm looking at a potential bug that would explain your problem
On Jan 1, 2015, at 9:50 AM, Stephan Bosch wrote:
>
> Hmm. This smells like a bug. I notice that your modification times of
> the .sieve and .svbin file are exactly the same (that is somewhat
> unusual). I'm looking at a potential bug that would explain your problem.
>
> To confirm, could you try
On Jan 1, 2015, at 9:12 AM, Gene Heskett wrote:
>
> Obviously, the last 3 lines are showing a perms problem.
Yes, I know it's a permissions problem. But there should be NO permissions
problem as it should not be trying to recompile the script. The script was
already pre-compiled and has not
On Jan 1, 2015, at 8:10 AM, Stephan Bosch wrote:
>
> Could you enable mail_debug? That should show why it is trying to
> recompile the Sieve script.
Well, that it does! And it's saying the script is "not up to date" and tries
to recompile it. However, I'm not sure why it would say it's NOT u
On Dec 31, 2014, at 1:23 PM, Wojciech Puchar wrote:
>
> i use dovecot 2 under FreeBSD (dovecot2-2.2.15 compiled from ports).
>
> tried both with kqueue enabled or not.
>
> everything works very fast, EXCEPT fetching big mail.
>
> tried multiple clients (thunderbird on windows, alpine on the sa
On Dec 31, 2014, at 11:18 AM, Robert Schetterer wrote:
> Am 31.12.2014 um 17:05 schrieb Robert Blayzor:
>> missing +w perm: /etc/dovecot/sieve, dir owned by 26:0 mode=0755)
>
>
>
> Best Regards
> MfG Robert Schetterer
Which is correct. Dovecot-lda is running as the
On Dec 10, 2014, at 1:52 AM, Steffen Kaiser
wrote:
>
>> Global scripts were compiled:
>>
>> /usr/local/etc/dovecot/sieve # ls
>> 10-move-spam.sieve 10-move-spam.svbin
>
>> However, I ran sievec again and tried saving a modified script and got the
>> same:
>
> Actually this "ls" output a
to=subscribe
}
}
--
Robert Blayzor
INOC, LLC
rblay...@inoc.net
http://www.inoc.net/~rblayzor/
can choose an action now when you swipe a message to
move it to a folder or just delete it. The GMail app/Gmail does something
similar by default I believe.
--
Robert Blayzor
INOC, LLC
rblay...@inoc.net
http://www.inoc.net/~rblayzor/
;` && kill -USR1 `cat
/var/run/dovecot/master.pid`
--
Robert Blayzor
INOC, LLC
rblay...@inoc.net
http://www.inoc.net/~rblayzor/
gt; solution anyway.
Why SIGHUP? If it's an already open file handle you could just compare the
string expansion against the currently opened log/FH, and if different open a
new FH?
If not possible perhaps able to pipe logs to an external programs like apache's
rotatelogs ?
--
Ro
Does (or can) the ability to use expansion variables in Dovecot's log_path
exist?
ie:
log_path = /var/log/dovecot/dovecot-%Y%m%d
--
Robert Blayzor
INOC, LLC
rblay...@inoc.net
http://www.inoc.net/~rblayzor/
31357
Works perfectly, thanks!
--
Robert Blayzor
INOC, LLC
rblay...@inoc.net
http://www.inoc.net/~rblayzor/
On Jul 17, 2012, at 6:59 AM, Timo Sirainen wrote:
> On 17.7.2012, at 1.35, Robert Blayzor wrote:
>
>> So is there any way possible to turn off advertising of TLS on port or turn
>> it off/on per IP?
>>
>> Something like:
>
> If those work, then yes. If they
We have the requirement to provide SSL on some IP addresses, but not others on
our servers.
Providing SSL is the easy part and we're able to use multiple SSL certificates
now. (thanks Timo!)
All is working ok, but we several IP hosts that do not require SSL and do not
have valid certificates.
ce
> flags/keywords are stored.
I'm not really up to speed on the dbox format, but I did look at it briefly.
I'd like to stick with maildir if at all possible. It's worked for us for
years, even over NFS, with little or no problems. I think your always going to
have problem
would help.
But neither of those help when the client is connecting from a different IP
address.
Robert Blayzor
INOC, LLC
rblay...@inoc.net
http://www.inoc.net/~rblayzor/
g their mobile
phone access it via IMAP. (obviously from different IP addresses). So I guess
there is some possibly index file write contention there as well. (though
hopefully this should be rare).
I'm curious as to know others experiences with a similar deployment.
TIA
--
Ro
ogin (not ~/Maildir/.lastlogin as that would
obviously cause some issues)
Seems like something that would be far less overhead than calling a shell,
execing another command, etc.
I'm open to other ideas/alternatives if they are out there!
TIA
--
Robert Blayzor
INOC, LLC
rblay...@inoc.net
http
41 matches
Mail list logo
