RE: I can't configure shared mailbox ACLs using LDAP information

2024-05-23 Thread Marc via dovecot
> I thought it was just a lack of skill on my part in finding/making the > correct configuration. I am curious about your results, so keep posting! :) > But what do large email servers that use Dovecot do? > > I thought it was an orchestration between OpenLDAP, Postfix and Dovecot > because

RE: Dovecot logging to files causes issues

2024-05-19 Thread Marc via dovecot
> Am 19.05.2024 um 16:49 schrieb Richard Rosner via dovecot: > > It most certainly isn't. nginx isn't running as root, yet it can log > > without execution permissions just fine. Absolutely nothing should have > > execution permissions if they aren't meant to be executed, which should > > only be

RE: Failing to archive many messages

2024-05-18 Thread Marc via dovecot
> Today I realized that it was indeed the sa-learn that is slowing down my > Archiving. > > I added an «&» on the end of the line that calls the sa-learn (called by > the report-ham.sieve script): > > exec /usr/bin/sa-learn -u ${1} --ham & > > Does anyone thing this is a bad idea? I noticed

RE: Failing to archive many messages

2024-05-09 Thread Marc via dovecot
> On 2024-05-09 12:03, Marc wrote: > > I see report-ham, instead of archiving? I am not entirely sure if this > > is an efficient approach to archiving. My users can only set a flag for > > 'auto archiving' via sieve and then 3 months after every year messages > > are being moved by cron jobs, and

RE: Failing to archive many messages

2024-05-09 Thread Marc via dovecot
I see report-ham, instead of archiving? I am not entirely sure if this is an efficient approach to archiving. My users can only set a flag for 'auto archiving' via sieve and then 3 months after every year messages are being moved by cron jobs, and modification logs are put into their accounts.

RE: temporary auth errors

2024-05-02 Thread Marc via dovecot
> > auth_failure_delay = 2 secs ? > > That will still simply wait before *rejecting* the login, compared to > *dropping the connection*. > > We are thus looking for three different behaviours: > > 1. If backend confrims auth, ACK auth + proceed (grant access) to email. > > 2. If

RE: temporary auth errors

2024-05-02 Thread Marc via dovecot
> Looking for some advise. Hmmm, I am glad I took the time to arrange a proper ldap infrastructure. What ever gets hammered stays local > > What I'm hoping is that dovecot has some way to in case of such > "authentication backend" problem scenarios to ignore protocol and > politeness and

RE: doveadm backup empties the remote host? SERIOUSLY???

2024-04-26 Thread Marc via dovecot
> > Sure it's my own fault - no discussion about that, but seriously? How > dangerously unintuitive it that? > I don't really get what is going on with remote host. How is a host name even relevant other than setting up the initial connection. I don't even see it in my storage mail files.

RE: Which DKIM application for postfix 3.9.0

2024-04-23 Thread Marc via dovecot
I can remember looking at rspamd years ago. I thought it was a bit chaotic with all these rules. I can even remember asking developers some design questions which they could not answer. The fact that they generate their own graphs (still?) is also old fashioned. This Sergey that is working on

RE: Which DKIM application for postfix 3.9.0

2024-04-23 Thread Marc via dovecot
> > I am upgrading to postfix 3.9.0. I have not used DKIM in previous > postfix installs, but I would like to start now with the new google > rules. I have done some research and opendkim is the most recommended, > however, other research states the opendkim has been abandoned by it's >

RE: Uppercase username emails are rejected

2024-04-17 Thread Marc via dovecot
> > No they aren't. The *host part* is case insensitive because the DNS is, Indeed. Letsencrypt is utilizing this characteristic, they query the same hostname every time with different randomized(?) capitalizations. I have no idea what the logics behind this is. Preventing this from showing in

RE: Uppercase username emails are rejected

2024-04-16 Thread Marc via dovecot
> > > Linux user names are case sensitive. I tend not to argue with basis > > unix/linux implementations, those are mostly well thought through by > > experts. This is from before the time that 'idiot' companies started > > using email addresses for logins, so it is easier (to track users > >

RE: Uppercase username emails are rejected

2024-04-16 Thread Marc via dovecot
> > John Stoffel via dovecot skrev den 2024-04-16 14:51: > > > In general, usernames should NOT be case sensitive, that way leads > > madness. > Linux user names are case sensitive. I tend not to argue with basis unix/linux implementations, those are mostly well thought through by experts.

RE: Message Age Deletion Query

2024-04-11 Thread Marc via dovecot
> Hello.  Using Mochahost and want to delete mailbox items older than 1 > month (approx) from receipt . Reading DoveCot documentation, not finding > age query.  Can you please specify this for me and provide an example? > doveadm move -u $account Archive/$year mailbox "$mbox" SENTBEFORE

RE: server migration

2024-04-10 Thread Marc via dovecot
> > > > • Gandalf Corvotempesta via dovecot [2024-04-10 21:07]: > > Guys, any help? > > What you describe is exactly what I have been doing since ... forever > Why? The whole idea about having a LTS distribution is that you almost never need to do this? It is not like the imap/pop/smtp

RE: server migration

2024-04-10 Thread Marc via dovecot
> > Guys, any help? this lacks context. > Also, what would happen if the new server has a different hostname ? So put temporary haproxy infront of it? > Il giorno dom 10 mar 2024 alle ore 14:28 Gandalf Corvotempesta > ha scritto: > > > > Hi guys > > I have to migrate around 10k mailboxes

maybe list rocky and centos9 stream?

2024-04-10 Thread Marc via dovecot
maybe list rocky and centos9 stream on the repo page? https://repo.dovecot.org/ ___ dovecot mailing list -- dovecot@dovecot.org To unsubscribe send an email to dovecot-le...@dovecot.org

RE: Users with enough rope to hang themselves

2024-04-10 Thread Marc via dovecot
> > This is ... bug like. > > The user moves a folder inside another, the resulting path exceeds the > maximum length, the folder's content is no longer accessible, the user > complains. I don't think this is a bad idea. If this is really the issue. > Double trouble. The user proceeded to

RE: storage format migration for folders

2024-04-05 Thread Marc via dovecot
> > > > doveadm sync -u testacc > 'mdbox:/home/testing/testacc/mdbox:INDEX=/home/testing/testacc/index:CONT > ROL=/home/testing/testacc/mail/control:LAYOUT=index' > > > > Which gives me the expectec result. But I have also an archive > namespace and an alt namespace that is going to be quite a lot

RE: storage format migration for folders

2024-04-05 Thread Marc via dovecot
> > > > > > > > > > > breaking the mail index > > > > > > > > > > > > Tangentially query: is Dveocot smart enough to optimize > mailbox > > > > > renaming > > > > > > to do index renaming (i.e. does not try to copy or recreate > > > indices)? > > > > > > > > > > > > > > > > Dovecot is, if you

storage format migration for folders

2024-04-05 Thread Marc via dovecot
> > > > > > > > > breaking the mail index > > > > > > > > Tangentially query: is Dveocot smart enough to optimize mailbox > > > renaming > > > > to do index renaming (i.e. does not try to copy or recreate > indices)? > > > > > > > > > > Dovecot is, if you use LAYOUT=index. This will use only

RE: Users with enough rope to hang themselves

2024-04-05 Thread Marc via dovecot
> > > breaking the mail index > > > > Tangentially query: is Dveocot smart enough to optimize mailbox > renaming > > to do index renaming (i.e. does not try to copy or recreate indices)? > > > > Dovecot is, if you use LAYOUT=index. This will use only mailbox GUID on > disk, and the folder name