Re: Unable to get quotas working

[Noel Butler via dovecot]

On 30/05/2024 20:06, Adam Miller via dovecot wrote:

however now I am having an issue trying to get the quota warning emails 
to work.


Your original post did not show a "service quota-warning" section where 
you tell dovecot what to run, I suggest you fully read everything to do 
with quota on the wiki (the relevant wiki files are also included in 
source packages)


--
Regards,
Noel Butler
___
dovecot mailing list -- dovecot@dovecot.org
To unsubscribe send an email to dovecot-le...@dovecot.org

Re: Unable to get quotas working

[Adam Miller via dovecot]

Thank you!

At the time, I was trying to get the most basic of quotas working which I have 
now successfully accomplished! I am happy report that I also have the warning 
emails working.

Next, my plan is to figure out a way to write custom HTML warning emails using 
the MJML templating engine. My thought was to have a bash script kick off a 
Python script which would grab the HTML email using an MJML template stored in 
a database and then pass back the HTML email it to the bash script to finally 
send it out. I know this might sound confusing and why would anyone want to do 
this, but my end goal is to build an email hosting service so having everything 
branded, secure and functioning well is at the top of the list. Is it possible 
that instead of a bash script for the warning emails to use a Python script 
instead?

I also must investigate load balancing or at the very least, determining the 
best approach to scalability and high availability.

Thank you!

On 6/1/24, 03:18, "Noel Butler via dovecot" mailto:dovecot@dovecot.org>> wrote:


On 30/05/2024 20:06, Adam Miller via dovecot wrote:


> however now I am having an issue trying to get the quota warning emails 
> to work.


Your original post did not show a "service quota-warning" section where 
you tell dovecot what to run, I suggest you fully read everything to do 
with quota on the wiki (the relevant wiki files are also included in 
source packages)


-- 
Regards,
Noel Butler
___
dovecot mailing list -- dovecot@dovecot.org 
To unsubscribe send an email to dovecot-le...@dovecot.org 





___
dovecot mailing list -- dovecot@dovecot.org
To unsubscribe send an email to dovecot-le...@dovecot.org

Re: Unable to get quotas working

[Noel Butler via dovecot]

On 01/06/2024 20:23, Adam Miller via dovecot wrote:


Thank you!

At the time, I was trying to get the most basic of quotas working which 
I have now successfully accomplished! I am happy report that I also 
have the warning emails working.


Excellent.

Is it possible that instead of a bash script for the warning emails to 
use a Python script instead?


Never been a fan of python, too much of a resource hog, even compared to 
perl, but as long as the variables are interpreted correctly, yes it 
should work.


I also must investigate load balancing or at the very least, 
determining the best approach to scalability and high availability.


We've used NFS for years without problems, never used dovecot's director 
service either, however we use hardware load balancers, done right, this 
is simplest and most robust method, add/delete/down-for-update front end 
servers at your will without affecting anything, as for backend, don't 
use junk, I've found EMC storage gear very reliable, but know that 
NetApp is too.


Over the years I've read about and witnessed many businesses with 
multi-day outages using clustered file systems that take out everything 
when they have a hissy fit, so I avoid them at all cost. NFS might be 
simplicity, but that means far fewer things to go wrong, and why some 
very large well known mail providers use it too.


--
Regards,
Noel Butler
___
dovecot mailing list -- dovecot@dovecot.org
To unsubscribe send an email to dovecot-le...@dovecot.org

sasl database

[Jeff P via dovecot]

Hello,

Is there a guide for using a customized SASL database for dovecot?
for example, SQLite.

Thanks in advance.
___
dovecot mailing list -- dovecot@dovecot.org
To unsubscribe send an email to dovecot-le...@dovecot.org

Pigenohole bad commands limits and proposed minor patch

[John Fawcett via dovecot]

Hi

I was looking into Pigeonhole behaviour in the case of managesieve 
receiving invalid input either before or after login. I can see that 
there are hard coded limits after 3 sequential bad commands prior to 
authentication and 20 after authentication.


I was wondering if there is a reason for those values. Sieve is a 
protocol that is used with software and except for the limited use case 
of testing it is not used by people typing manually.


I don't know of a lot of sieve clients. Unfortunately the one I used in 
Thunderbird is no longer maintained, so I only have roundcube. But do 
legitimate sieve clients in general make a lot of mistakes?


An additional doubt about errors that I am seeing is that differently to 
imap and pop3 there doen't appear to be  a dedicated ssl port. I only 
have starttls configured. I do see what look like people trying to 
connect with ssl directly on port 4190, which with my configuration is 
never going to be valid.


I am attaching a very simple proposed patch to make the error limits 
configurable via the following settings in conf.d/20-managesieve.conf 
with defaults as per the existing hard coded ones:


  managesieve_max_command_errors = 20
  managesieve_login_max_command_errors = 3

I have similar doubts about imap error limits but I'll start with sieve 
ones.


John

___
dovecot mailing list -- dovecot@dovecot.org
To unsubscribe send an email to dovecot-le...@dovecot.org

Re: sasl database

[John Fawcett via dovecot]

On 01/06/2024 13:22, Jeff P via dovecot wrote:

Hello,

Is there a guide for using a customized SASL database for dovecot?
for example, SQLite.

Thanks in advance.
___
dovecot mailing list -- dovecot@dovecot.org
To unsubscribe send an email to dovecot-le...@dovecot.org


Hi Jeff

I've no experience with using sqlite with dovecot but there is 
documentation here:


https://doc.dovecot.org/configuration_manual/authentication/sql/#sqlite

The same page also contains configurations for other db servers.

John

___
dovecot mailing list -- dovecot@dovecot.org
To unsubscribe send an email to dovecot-le...@dovecot.org

RE: sasl database

[aki.tuomi via dovecot]

Hi, please see 
https://doc.dovecot.org/configuration_manual/authentication/sql/#authentication-sqlAki
 Original message From: Jeff P via dovecot 
 Date: 6/1/24  14:28  (GMT+02:00) To: dovecot@dovecot.org 
Subject: sasl database Hello,Is there a guide for using a customized SASL 
database for dovecot?for example, SQLite.Thanks in 
advance.___dovecot mailing list -- 
dovecot@dovecot.orgTo unsubscribe send an email to dovecot-le...@dovecot.org
___
dovecot mailing list -- dovecot@dovecot.org
To unsubscribe send an email to dovecot-le...@dovecot.org

problem setting sieve_vacation_send_from_recipient = yes

[schuerbel--- via dovecot]

Hello,


dovecot sieve sends vacation replies with an empty FROM: field by 
default. Sadly my provider rejects such emails.


I tried to change this behavior by adding 
sieve_vacation_send_from_recipient = yes to the plugin section in 
dovecot.conf. But still vacation replies are send with empty FROM: 
fields. Is there any further setting i have to change ?


My Version is dovecot 2.3.16 (7e2e900c1a) on Ubuntu 22.04 .

Here is my setting from dovecot -n :

log_timestamp = "%Y-%m-%d %H:%M:%S "
mail_location = maildir:~/Maildir
mail_privileged_group = mail
managesieve_notify_capability = mailto
managesieve_sieve_capability = fileinto reject envelope 
encoded-character vacation subaddress comparator-i;ascii-numeric 
relational regex imap4flags copy include variables body enotify 
environment mailbox date index ihave duplicate mime foreverypart extracttext

namespace inbox {
  inbox = yes
  location =
  mailbox Drafts {
special_use = \Drafts
  }
  mailbox Junk {
special_use = \Junk
  }
  mailbox Sent {
special_use = \Sent
  }
  mailbox "Sent Messages" {
special_use = \Sent
  }
  mailbox Trash {
special_use = \Trash
  }
  prefix =
}
passdb {
  driver = pam
}
passdb {
  driver = pam
}
plugin {
  sieve = ~/.dovecot.sieve
  sieve_dir = ~/sieve
  sieve_vacation_send_from_recipient = yes
}
protocols = imap sieve
service auth {
  unix_listener /var/spool/postfix/private/dovecot-auth {
group = postfix
mode = 0660
user = postfix
  }
  user = root
}
ssl_cert = ssl_cipher_list = 
ALL:!LOW:!SSLv2:ALL:!aNULL:!ADH:!eNULL:!EXP:RC4+RSA:+HIGH:+MEDIUM

ssl_key = # hidden, use -P to show it
userdb {
  driver = passwd
}
userdb {
  driver = passwd
}
verbose_ssl = yes
protocol imap {
  imap_client_workarounds = delay-newmail
  mail_max_userip_connections = 10
}
protocol pop3 {
  mail_max_userip_connections = 10
  pop3_client_workarounds = outlook-no-nuls oe-ns-eoh
  pop3_uidl_format = %08Xu%08Xv
}
protocol lda {
  deliver_log_format = msgid=%m: %$
  mail_plugins = sieve
  postmaster_address = tor...@garfield.no-work.to
  quota_full_tempfail = yes
  rejection_reason = Your message to <%t> was automatically rejected:%n%r
}


regards
TS
___
dovecot mailing list -- dovecot@dovecot.org
To unsubscribe send an email to dovecot-le...@dovecot.org

Debug: open(/proc/self/io) failed: Permission denied

[se--- via dovecot]

Tried all kinds of user setup, and read what I found on different foras, but 
still get:

"Debug: open(/proc/self/io) failed: Permission denied"

Is anyone able to spot the misconfig? 

Thanks in advance!

This is my dovecot -n:

# 2.3.7.2 (3c910f64b): /etc/dovecot/dovecot.conf
# Pigeonhole version 0.5.7.2 ()
# OS: Linux 5.4.70-050470-generic x86_64 Ubuntu 20.04.6 LTS
# Hostname: host
auth_debug = yes
auth_debug_passwords = yes
auth_mechanisms = plain login
auth_username_format = %Ln
mail_location = maildir:~/Maildir
mail_privileged_group = mail
namespace inbox {
  inbox = yes
  location =
  mailbox Drafts {
auto = create
special_use = \Drafts
  }
  mailbox Junk {
auto = create
special_use = \Junk
  }
  mailbox Sent {
auto = create
special_use = \Sent
  }
  mailbox "Sent Messages" {
special_use = \Sent
  }
  mailbox Trash {
auto = create
special_use = \Trash
  }
  prefix =
}
passdb {
  driver = pam
}
protocols = imap pop3 lmtp imap lmtp pop3
service auth {
  unix_listener /var/spool/postfix/private/auth {
group = postfix
mode = 0660
user = postfix
  }
}
service lmtp {
  unix_listener /var/spool/postfix/private/dovecot-lmtp {
group = postfix
mode = 0600
user = postfix
  }
}
ssl = required
ssl_cert = 

Re: Debug: open(/proc/self/io) failed: Permission denied

[Aki Tuomi via dovecot]

> On 01/06/2024 19:47 EEST se--- via dovecot  wrote:
> 
>  
> Tried all kinds of user setup, and read what I found on different foras, but 
> still get:
> 
> "Debug: open(/proc/self/io) failed: Permission denied"
> 
> Is anyone able to spot the misconfig? 
> 
> Thanks in advance!
> 

Hi!

First of all, that's not an error. You can tell by the "Debug" prefix, errors 
are with "Error" prefix.

If you don't want to see this, add

import_environment = $import_environment PR_SET_DUMPABLE=1

Aki
___
dovecot mailing list -- dovecot@dovecot.org
To unsubscribe send an email to dovecot-le...@dovecot.org

Re: Debug: open(/proc/self/io) failed: Permission denied

[se--- via dovecot]

Worked like a charm. Thanks!
___
dovecot mailing list -- dovecot@dovecot.org
To unsubscribe send an email to dovecot-le...@dovecot.org