Re: exfat not supported ?
I don’t think exfat is POSIX compliant. A quick search shows As exfat was created for windows, it is not a POSIX compliant filesystemand is missing a number of features that are expected on unix filesystems, such as symlinks, hard links, file locking, case sensitivity, and permissions. Any permissions you see on exfat are derived from mount options, not from the filesystem.Nov 7, 2021 Ted > On Apr 20, 2024, at 7:04 PM, Joan Moreau via dovecot > wrote: > > That resolve the fisrt bug > > but I get now : > > Error: link(/xxx/dovecot.list.index.log, /xxx/dovecot.list.index.log.2) > failed: Operation not permitted > >> On 2024-04-21 02:02, Aki Tuomi via dovecot wrote: >> >> Try setting lock_method = dotlock >> Aki >> On 20/04/2024 15:32 EEST Joan Moreau via dovecot >> wrote: >> I tried and get the following: >> Error: Couldn't create mailbox list lock /xxx/mailboxes.lock: >> file_create_locked(/xxx/mailboxes.lock) failed: >> link(/xxx/mailboxes.locka94f3757318b0b90, /xxx/mailboxes.lock) >> failed: >> Operation not permitted >> On 2024-04-20 17:39, Aki Tuomi via dovecot wrote: >> On 20/04/2024 12:27 EEST Joan Moreau via dovecot >> wrote: >> Hi >> Would placing my storage on a exfat partition work ? If no, >> why ? >> Thank you >> ___ >> dovecot mailing list -- dovecot@dovecot.org >> To unsubscribe send an email to dovecot-le...@dovecot.org >> I can't see any reason why not. As long as it behaves like >> POSIX >> filesystem. >> Aki >> ___ >> 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 >> ___ >> 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 ___ dovecot mailing list -- dovecot@dovecot.org To unsubscribe send an email to dovecot-le...@dovecot.org
Re: Recovering deleted mailbox
I've done so with no issues as long as permissions and ownership are accurate. Ted Hatfield On Wed, 27 Apr 2022, Sean McBride wrote: Hi all, I have a user (coworker) that accidentally deleted a mailbox and all its sub-mailboxes. I use Maildir format storage. I have backups. Is it enough to put the mailbox folder back where it was? I'm talking about the folder that contains 'cur', 'new', 'tmp', 'dovecot-uidlist', etc. Or would this desynchronize or otherwise confuse dovecot? Or is it preferable to use some doveadm command? Or...? Thanks, Sean
Re: dovecot + Procmail -> junk emails
On Mon, 2 Aug 2021, John Stoffel wrote:
"Stephane" == Stephane Magnier writes:
Stephane> Having moved from 'mbox' to 'Maildir', I'm trying to use a
Stephane> way to move a spam email to the Junk folder
Have you looked at 'sieve' and 'pigeonhole' setup? procmail is old
old old and completely unsupported.
Stephane> I declared the junk folder as;
Stephane> namespace inbox {
Stephane> type = private
Stephane> disabled = no
Stephane> ignore_on_failure = no
Stephane> list = yes
Stephane> subscriptions = yes
Stephane> #hidden = no
Stephane> #inbox = yes
Stephane> #prefix = INBOX/
Stephane> mailbox "Drafts" {
Stephane> auto = subscribe
Stephane> special_use = \Drafts
Stephane> }
Stephane> mailbox "Junk" {
Stephane> auto = subscribe
Stephane> autoexpunge = 12 weeks
Stephane> special_use = \Junk
Stephane> }
Stephane> mailbox "Trash" {
Stephane> auto = no
Stephane> autoexpunge = 12 weeks
Stephane> special_use = \Trash
Stephane> }
Stephane> mailbox "Sent" {
Stephane> auto = subscribe
Stephane> special_use = \Sent
Stephane> }
Stephane> and spamassassin, very basic
Stephane> loadplugin Mail::SpamAssassin::Conf
Stephane> required_hits 5
Stephane> required_score 5
Stephane> rewrite_header subject [** SPAM ** ]
Stephane> add_header all Status _YESNO_, score=_SCORE_
required=_REQD_ tests=_TESTS_ autolearn=
Stephane> _AUTOLEARN_ version=_VERSION_
Stephane> spf_timeout 60
Stephane> rewrite_header to [Email could be SPAM ]
Stephane> fold_headers 0
Stephane> #defang_mime 0
Stephane> report_safe 0
Stephane> and Procmail.. basic and I used what I found on the webpage :
Stephane> https://wiki.dovecot.org/procmail
This is probably old and should be removed or replaced. I have
/etc/dovecot/conf.d/90-sieve.conf which looks like this:
plugin {
sieve = ~/.dovecot.sieve
sieve_dir = ~/sieve
sieve_global_dir =
sieve_before = /var/lib/dovecot/sieve/before.d
sieve_after = /etc/dovecot/sieve-after
sieve_extensions = +spamtest +spamtestplus
sieve_spamtest_status_type = score
sieve_spamtest_status_header = X-Spamd-Result: default: [[:alnum:]]+
[(-?[[:digit:]]+\.[[:digit:]]+) / -?[[:digit:]]+\.[[:digit:]]+\]
sieve_spamtest_max_header= X-Spamd-Result: default: [[:alnum:]]+
[-?[[:digit:]]+\.[[:digit:]]+ / (-?[[:digit:]]+\.[[:digit:]]+)\]
}
And I have spamassissin scoring my mails, this script to move them
into 'Junk' as needed:
# more /etc/dovecot/sieve-after/spam-to-folder.sieve
require ["fileinto","mailbox"];
if header :contains "X-Spam-Flag" "YES" {
fileinto :create "Junk";
stop;
}
Cheers,
John
John,
There are still a number of people using procmail. Including me for
instance. Rather than removing the page perhaps updating the article
with a reference to a replacement instead but leaving the procmail
documentation in place.
Ted
Re: Using NFS to extend local email storage
On Sun, 18 Oct 2020, Sven Hartge wrote: On 18.10.20 19:50, Maciej Kokoci?ski wrote: Now, my idea is to set up an NFS volume on the NAS, and configure the cloud-based server as the client. I would like to store only the most recent emails on the main server, and keep the whole data set on the NAS. Doing NFS over the Internet is such a bad idea. Don't do it. Also don't do NFS over a WAN link inside a VPN. The latency will kill you. In addition to that, the flakiness of the on-prem NAS will hard-lock any process accessing or trying to access anything on the NFS share during times where it is not available. This setup would severely degrade not only the performance but also the availability of your mails. Do not do this. In your case I only see the option to either deal with the increased costs, move to a different ISP which is cheaper or move to a hosted mail solution, which may also be cheaper. But jerry-rigging an NFS share on a flaky box over a WAN link is such a bad idea. Please, reconsider. Gr??e, Sven. Sven is correct, NFS over the internet is not a great idea. You might want to look into moving the access from the server to the client. Setup an imap server at the location where you host the NAS and configure the client with a second imap connection where older archived email is stored. Isn't that one of the strengths of the imap protocol. The ability to access multiple imap folders from multiple locations. It's easy to do with standalone clients although I'm not sure how much trouble it would be to hack your webmail software to include a sedondary imap profile. Ted.
Problem with filter forwarded messages when using director proxy
Hey there, I've been able to switch our mailservers over to using director to proxy logins and received email to the backend servers which store email on a shared NFS mount. Before I did this we were having trouble with the indexes running into errors because multiple servers accessing and modifying the dovecot.index files at the same time. I'm still seeing a small amount of this, and tracing it through it appears that when an account uses a filter to forward email to another address within our mail system, it recognises that it is a local email address it is responsible for and saves the message locally despite the fact that it is not the director specified server for the recipient address. As an example, lets say that te...@example.com is currently pointed to the 01 backend server by director, and te...@example.com to 02. If a filter at test1 forwards email to test2, then when an email for test1 comes in the director porxy will direct it to the 01 backend server, and when the message is saved the filter will run to forward it, and the 01 server will recognise that it is also responsible for test2 and so 01 will save the message for test2 rather than 02, as per director. This is causing a smallish number of clashes which I'd like to get cleaned up. I've tried getting the server to send through a relay but if it recognises the account as local it will not use the relay to send the email. Has anyone run into anything like this or have any ideas about how to approach the problem? Thank you Ted easyDNS Technologies
Re: problem in setting up proxy
Hey,
We found the issue in our side, it turns out the problem was on the
loadbalancers and not in dovecot at all. Sorry to have troubled you.
Thank you
Ted
easyDNS Technologies
On 2019-01-23 10:12 a.m., Sami Ketola wrote:
>
>> On 23 Jan 2019, at 16.33, Ted wrote:
>>
>> Hello,
>>
>> Absolutely, thanks, here it is:
>>
>> passdb {
>> args = nopassword=y
>> default_fields = proxy=y host=10.5.10.121
>> driver = static
>> name = static
>> }
> at least change this to:
>
> passdb {
> driver = static
> name = static
> args = nopassword=y proxy=y host=10.5.10.121
> }
>
> but not entirely sure if there is something else.
>
> Sami
Re: problem in setting up proxy
Hello,
Thanks for the advice, I have made that change now but the server is
still doing the same fail with no logs thing it was before.
# 2.2.27 (c0f36b0): /etc/dovecot/dovecot.conf
# Pigeonhole version 0.4.16 (fed8554)
# OS: Linux 4.9.0-8-amd64 x86_64 Debian 9.6
auth_debug = yes
auth_mechanisms = plain login
auth_verbose = yes
disable_plaintext_auth = no
login_greeting = Welcome to easyMail.
mail_debug = yes
mail_location = mbox:~/mail:INBOX=/var/mail/%u
mail_plugins = " mail_log notify"
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 {
args = nopassword=y proxy=y host=10.5.10.121
driver = static
name = static
}
plugin {
sieve = file:~/sieve;active=~/.dovecot.sieve
}
protocols = imap pop3
service auth {
unix_listener auth-master {
mode = 0600
user = vmail
}
}
ssl = no
verbose_proctitle = yes
verbose_ssl = yes
protocol imap {
mail_plugins = " mail_log notify"
}
Anything else you can see I could try?
Thank you
Ted
easyDNS Technologies
On 2019-01-23 10:12 a.m., Sami Ketola wrote:
>
>> On 23 Jan 2019, at 16.33, Ted wrote:
>>
>> Hello,
>>
>> Absolutely, thanks, here it is:
>>
>> passdb {
>> args = nopassword=y
>> default_fields = proxy=y host=10.5.10.121
>> driver = static
>> name = static
>> }
> at least change this to:
>
> passdb {
> driver = static
> name = static
> args = nopassword=y proxy=y host=10.5.10.121
> }
>
> but not entirely sure if there is something else.
>
> Sami
Re: problem in setting up proxy
Hello,
Absolutely, thanks, here it is:
# 2.2.27 (c0f36b0): /etc/dovecot/dovecot.conf
# Pigeonhole version 0.4.16 (fed8554)
# OS: Linux 4.9.0-8-amd64 x86_64 Debian 9.6
auth_debug = yes
auth_mechanisms = plain login
auth_verbose = yes
disable_plaintext_auth = no
login_greeting = Welcome to easyMail.
mail_debug = yes
mail_location = mbox:~/mail:INBOX=/var/mail/%u
mail_plugins = " mail_log notify"
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 {
args = nopassword=y
default_fields = proxy=y host=10.5.10.121
driver = static
name = static
}
plugin {
sieve = file:~/sieve;active=~/.dovecot.sieve
}
protocols = imap pop3
service auth {
unix_listener auth-master {
mode = 0600
user = vmail
}
}
ssl = no
verbose_proctitle = yes
verbose_ssl = yes
protocol imap {
mail_plugins = " mail_log notify"
}
Thank you
Ted
easyDNS Technologies
On 2019-01-23 2:39 a.m., Aki Tuomi wrote:
> Hi!
>
> First of all, can you provide output of 'doveconf -n'? It's much cleaner
> to read and shows what's really there?
>
> Aki
>
> On 22.1.2019 17.57, Ted wrote:
>> Hello,
>>
>> We're having difficulty with our updated cluster of dovecot servers
>> accessing the email storage on the NFS mounts. It seems index files get
>> corrupted when 2 backend mailservers access the same account, and from
>> documentation setting up a director proxy in front of the backup
>> servers. I'm trying to just set up a straight proxy first, which the
>> documents say is the first step, and although I can see the connections
>> coming into the server when I try to login via the proxy, the connection
>> times out and there are no logs from dovecot anywhere saying what
>> happened to the connection.
>>
>> The configs I have set up for this in dovecot are:
>>
>> dovecot.conf
>>
>> # Protocols we want to be serving.
>> protocols = imap pop3
>>
>> #when re-enabling quota enforcement add quota in below:
>> mail_plugins = $mail_plugins mail_log notify
>>
>> protocol imap {
>> # Space separated list of plugins to load (default is global
>> mail_plugins).
>> #when re-enabling quota enforcement add imap_quota in below:
>> mail_plugins = $mail_plugins
>> }
>>
>>
>> # A comma separated list of IPs or hosts where to listen in for
>> connections.
>> # "*" listens in all IPv4 interfaces, "::" listens in all IPv6 interfaces.
>> # If you want to specify non-default ports or anything more complex,
>> # edit conf.d/master.conf.
>> #listen = *, ::
>>
>> # Base directory where to store runtime data.
>> #base_dir = /var/run/dovecot/
>>
>> # Name of this instance. In multi-instance setup doveadm and other commands
>> # can use -i to select which instance is used (an
>> alternative
>> # to -c ). The instance name is also added to Dovecot processes
>> # in ps output.
>> #instance_name = dovecot
>>
>> # Greeting message for clients.
>> login_greeting = Welcome to easyMail.
>>
>> shutdown_clients = yes
>>
>> # Most of the actual configuration gets included below. The filenames are
>> # first sorted by their ASCII value and parsed in that order. The
>> 00-prefixes
>> # in filenames are intended to make it easier to understand the ordering.
>> !include conf.d/*.conf
>>
>> # A config file can also tried to be included without giving an error if
>> # it's not found:
>> !include_try local.conf
>>
>> service auth {
>> unix_listener auth-master {
>> mode = 0600
>> user = vmail
>> }
>> }
>>
>> conf.d/10-auth.conf
>>
>> ##
>> ## Authentication processes
>> ##
>> # Username formatting before it's looked up from databases. You can use
>> # the standard variables here, eg. %Lu would lowercase the username, %n
>> would
>> # drop away the domain if it was given, or "%n-AT-%d" would change the
>> '@' into
>> # "-AT-". This translation is done after auth_username_translation changes.
>> auth_usernam
problem in setting up proxy
alid
values are
# no, plain and sha1. sha1 can be useful for detecting brute force password
# attempts vs. user simply trying the same password over and over again.
# You can also truncate the value to n chars by appending ":n" (e.g.
sha1:6).
#auth_verbose_passwords = no
# Even more verbose logging for debugging purposes. Shows for example SQL
# queries.
auth_debug = yes
# In case of password mismatches, log the passwords and used scheme so the
# problem can be debugged. Enabling this also enables auth_debug.
#auth_debug_passwords = no
# Enable mail process debugging. This can help you figure out why Dovecot
# isn't finding your mails.
mail_debug = yes
# Show protocol level SSL errors.
verbose_ssl = yes
# mail_log plugin provides more event logging for mail processes.
plugin {
# Events to log. Also available: flag_change append
#mail_log_events = delete undelete expunge copy mailbox_delete
mailbox_rename
# Available fields: uid, box, msgid, from, subject, size, vsize, flags
# size and vsize are available only for expunge and copy events.
#mail_log_fields = uid box msgid size
}
I'm basically expecting this to forward the login requests on to
10.5.10.121 when I try to access the email account through the proxy.
When I attempt this I am able to see the connections in a tcp dump, but
dovecot does not log anything about the attempt. I clearly must be
missing something, can you let me know what I need to do or check?
Thank you
Ted
easyDNS Technologies
Re: Problem getting quota-warning script to function.
Hello, Do you mean you're using the configurations I sent as examples and are seeing the quota warning script effectively? I've continued to try changes to get it working but no luck yet. Might it be somehow related to the directories mail is stored in being shared NFS mounts? Thank you Ted easyDNS Technologies On 2018-10-09 09:45 AM, Aki Tuomi wrote: > Hi! > > We have not been able to reproduce this issue yet. > > Aki > > >> On 09 October 2018 at 16:28 Ted wrote: >> >> >> Hello, >> >> I don't suppose there's been any thoughts or progress on this one? Is >> there further information I can provide or anything I could try or check >> on the mailserver? >> >> Thank you >> Ted >> easyDNS Technologies >> >> On 2018-09-24 12:44 PM, Aki Tuomi wrote: >>> Hi! >>> >>> It can take some time for us to look into these... >>> >>> Aki >>> >>>> On 24 September 2018 at 19:38 Ted wrote: >>>> >>>> >>>> Hello, >>>> >>>> I haven't received a reply since I sent my last logs in, so I thought >>>> I'd ask again and update the thread. I had trouble getting the server >>>> to work properly on dovecot 2.3.2 so I rebuilt the server back on >>>> 2.2.27. I've got the quota enforcement itself working, but the warnings >>>> still fail to fire. I've attached logs with mail_debug=yes for the >>>> period from the send which put the quota at 90% all the way until it is >>>> blocking email for being overquota. >>>> >>>> Thank you >>>> Ted >>>> easyDNS Technologies >>>> >>>> On 2018-09-19 12:55 PM, Aki Tuomi wrote: >>>>>> On 19 September 2018 at 19:49 Ted wrote: >>>>>> >>>>>> >>>>>> Hello, >>>>>> >>>>>> Most of the work was done with dovecot 2.2.27 but I just upgraded to >>>>>> 2.3.2 and didn't see any change. Some debug logs are below, is there >>>>>> something specific I could search them for? >>>>>> >>>>> Can you maybe try delivery to an account which should trigger quota >>>>> warning or overquota action with mail_debug=yes? >>>>> >>>>> Aki >>
Re: Problem getting quota-warning script to function.
Hello, I don't suppose there's been any thoughts or progress on this one? Is there further information I can provide or anything I could try or check on the mailserver? Thank you Ted easyDNS Technologies On 2018-09-24 12:44 PM, Aki Tuomi wrote: > Hi! > > It can take some time for us to look into these... > > Aki > >> On 24 September 2018 at 19:38 Ted wrote: >> >> >> Hello, >> >> I haven't received a reply since I sent my last logs in, so I thought >> I'd ask again and update the thread. I had trouble getting the server >> to work properly on dovecot 2.3.2 so I rebuilt the server back on >> 2.2.27. I've got the quota enforcement itself working, but the warnings >> still fail to fire. I've attached logs with mail_debug=yes for the >> period from the send which put the quota at 90% all the way until it is >> blocking email for being overquota. >> >> Thank you >> Ted >> easyDNS Technologies >> >> On 2018-09-19 12:55 PM, Aki Tuomi wrote: >>>> On 19 September 2018 at 19:49 Ted wrote: >>>> >>>> >>>> Hello, >>>> >>>> Most of the work was done with dovecot 2.2.27 but I just upgraded to >>>> 2.3.2 and didn't see any change. Some debug logs are below, is there >>>> something specific I could search them for? >>>> >>> Can you maybe try delivery to an account which should trigger quota warning >>> or overquota action with mail_debug=yes? >>> >>> Aki
Re: Problem getting quota-warning script to function.
Hello, I haven't received a reply since I sent my last logs in, so I thought I'd ask again and update the thread. I had trouble getting the server to work properly on dovecot 2.3.2 so I rebuilt the server back on 2.2.27. I've got the quota enforcement itself working, but the warnings still fail to fire. I've attached logs with mail_debug=yes for the period from the send which put the quota at 90% all the way until it is blocking email for being overquota. Thank you Ted easyDNS Technologies On 2018-09-19 12:55 PM, Aki Tuomi wrote: >> On 19 September 2018 at 19:49 Ted wrote: >> >> >> Hello, >> >> Most of the work was done with dovecot 2.2.27 but I just upgraded to >> 2.3.2 and didn't see any change. Some debug logs are below, is there >> something specific I could search them for? >> > Can you maybe try delivery to an account which should trigger quota warning > or overquota action with mail_debug=yes? > > Aki Sep 24 15:25:07 ezm11-pco dovecot: quota-status(ot...@quailmail.ca): Debug: auth USER input: ot...@quailmail.ca mail=maildir:/svmail/03/quailmail.ca/other/Maildir home=/svmail/03/quailmail.ca/other uid=5000 gid=5000 quota_rule=*:storage=1G Sep 24 15:25:07 ezm11-pco dovecot: quota-status(ot...@quailmail.ca): Debug: Added userdb setting: mail=maildir:/svmail/03/quailmail.ca/other/Maildir Sep 24 15:25:07 ezm11-pco dovecot: quota-status(ot...@quailmail.ca): Debug: Added userdb setting: plugin/quota_rule=*:storage=1G Sep 24 15:25:07 ezm11-pco dovecot: quota-status(ot...@quailmail.ca): Debug: Effective uid=5000, gid=5000, home=/svmail/03/quailmail.ca/other Sep 24 15:25:07 ezm11-pco dovecot: quota-status(ot...@quailmail.ca): Debug: Quota root: name=User quota backend=count args= Sep 24 15:25:07 ezm11-pco dovecot: quota-status(ot...@quailmail.ca): Debug: Quota rule: root=User quota mailbox=* bytes=1073741824 messages=0 Sep 24 15:25:07 ezm11-pco dovecot: quota-status(ot...@quailmail.ca): Debug: Quota warning: bytes=1020054732 (95%) messages=0 reverse=no command=quota-warning 95 ot...@quailmail.ca Sep 24 15:25:07 ezm11-pco dovecot: quota-status(ot...@quailmail.ca): Debug: Quota warning: bytes=966367641 (90%) messages=0 reverse=no command=quota-warning 90 ot...@quailmail.ca Sep 24 15:25:07 ezm11-pco dovecot: quota-status(ot...@quailmail.ca): Debug: Quota warning: bytes=858993459 (80%) messages=0 reverse=no command=quota-warning 80 ot...@quailmail.ca Sep 24 15:25:07 ezm11-pco dovecot: quota-status(ot...@quailmail.ca): Debug: Quota grace: root=User quota bytes=107374182 (10%) Sep 24 15:25:07 ezm11-pco dovecot: quota-status(ot...@quailmail.ca): Debug: Namespace : type=private, prefix=INBOX., sep=., inbox=yes, hidden=no, list=yes, subscriptions=yes location=maildir:/svmail/03/quailmail.ca/other/Maildir Sep 24 15:25:07 ezm11-pco dovecot: quota-status(ot...@quailmail.ca): Debug: maildir++: root=/svmail/03/quailmail.ca/other/Maildir, index=, indexpvt=, control=, inbox=/svmail/03/quailmail.ca/other/Maildir, alt= Sep 24 15:25:07 ezm11-pco dovecot: quota-status(ot...@quailmail.ca): Debug: Namespace : type=private, prefix=, sep=, inbox=no, hidden=yes, list=no, subscriptions=no location=fail::LAYOUT=none Sep 24 15:25:07 ezm11-pco dovecot: quota-status(ot...@quailmail.ca): Debug: none: root=, index=, indexpvt=, control=, inbox=, alt= Sep 24 15:25:07 ezm11-pco dovecot: quota-status(ot...@quailmail.ca): Debug: Namespace INBOX.: Using permissions from /svmail/03/quailmail.ca/other/Maildir: mode=0700 gid=default Sep 24 15:25:07 ezm11-pco dovecot: quota-status(ot...@quailmail.ca): Debug: quota: quota_over_flag check: STORAGE ret=1 value=952777 limit=1048576 Sep 24 15:25:07 ezm11-pco dovecot: quota-status(ot...@quailmail.ca): Debug: quota: quota_over_flag check: MESSAGE ret=0 value=4868 limit=0 Sep 24 15:25:07 ezm11-pco dovecot: quota-status(ot...@quailmail.ca): Debug: quota: quota_over_flag=0((null)) vs currently overquota=0 Sep 24 15:25:08 ezm11-pco amavis[24865]: (24865-03) ESMTP [127.0.0.1]:10024 /var/lib/amavis/tmp/amavis-20180921T213124-24865-QS8PnhKc: -> SIZE=10997938 BODY=7BIT Received: from smtp.easymail.ca ([127.0.0.1]) by localhost (ezm11-pco.easydns.vpn [127.0.0.1]) (amavisd-new, port 10024) with ESMTP for ; Mon, 24 Sep 2018 15:25:08 + (UTC) Sep 24 15:25:08 ezm11-pco amavis[24865]: (24865-03) Checking: setsY-JlPgZ8 [64.68.203.197] -> Sep 24 15:25:24 ezm11-pco dovecot: imap(ot...@quailmail.ca): Connection closed: read(size=5651) failed: Connection reset by peer in=2541 out=11095844 Sep 24 15:25:24 ezm11-pco dovecot: imap(ot...@quailmail.ca): Connection closed: read(size=3383) failed: Connection reset by peer in=4809 out=22100709 Sep 24 15:25:36 ezm11-pco amavis[24865]: (24865-03) spam-tag, -> , No, score=0 required=4 tests=[SPF_PASS=-0.001, TVD_SPACE_RATIO=0.001] autolearn=ham autolearn_force=no Sep 24 15:25:36 ezm11-pco amavis[24865]: (24865-03) setsY-JlPgZ8 FWD f
Re: Problem getting quota-warning script to function.
Quota root: name=User quota backend=count args=
Sep 14 18:11:04 ezm11-pco dovecot: quota-status(ot...@quailmail.ca):
Debug: Quota rule: root=User quota mailbox=* bytes=1073741824 messages=0
Sep 14 18:11:04 ezm11-pco dovecot: quota-status(ot...@quailmail.ca):
Debug: Quota warning: bytes=1020054732 (95%) messages=0 reverse=no
command=quota-warning 95 ot...@quailmail.ca
Sep 14 18:11:04 ezm11-pco dovecot: quota-status(ot...@quailmail.ca):
Debug: Quota warning: bytes=966367641 (90%) messages=0 reverse=no
command=quota-warning 90 ot...@quailmail.ca
Sep 14 18:11:04 ezm11-pco dovecot: quota-status(ot...@quailmail.ca):
Debug: Quota warning: bytes=858993459 (80%) messages=0 reverse=no
command=quota-warning 80 ot...@quailmail.ca
Sep 14 18:11:04 ezm11-pco dovecot: quota-status(ot...@quailmail.ca):
Debug: Quota grace: root=User quota bytes=107374182 (10%)
Sep 14 18:11:04 ezm11-pco dovecot: quota-status(ot...@quailmail.ca):
Debug: Namespace : type=private, prefix=INBOX., sep=., inbox=yes,
hidden=no, list=yes, subscriptions=yes
location=maildir:/svmail/04/quailmail.ca/other/Maildir
Sep 14 18:11:04 ezm11-pco dovecot: quota-status(ot...@quailmail.ca):
Debug: maildir++: root=/svmail/04/quailmail.ca/other/Maildir, index=,
indexpvt=, control=, inbox=/svmail/04/quailmail.ca/other/Maildir, alt=
Sep 14 18:11:04 ezm11-pco dovecot: quota-status(ot...@quailmail.ca):
Debug: Namespace : type=private, prefix=, sep=, inbox=no, hidden=yes,
list=no, subscriptions=no location=fail::LAYOUT=none
Sep 14 18:11:04 ezm11-pco dovecot: quota-status(ot...@quailmail.ca):
Debug: none: root=, index=, indexpvt=, control=, inbox=, alt=
Sep 14 18:11:04 ezm11-pco dovecot: quota-status(ot...@quailmail.ca):
Debug: Namespace INBOX.: Using permissions from
/svmail/04/quailmail.ca/other/Maildir: mode=0700 gid=default
Sep 14 18:11:04 ezm11-pco dovecot: quota-status(ot...@quailmail.ca):
Debug: quota: quota_over_flag check: STORAGE ret=1 value=847105
limit=1048576
Sep 14 18:11:04 ezm11-pco dovecot: quota-status(ot...@quailmail.ca):
Debug: quota: quota_over_flag check: MESSAGE ret=0 value=7578 limit=0
Sep 14 18:11:04 ezm11-pco dovecot: quota-status(ot...@quailmail.ca):
Debug: quota: quota_over_flag=0((null)) vs currently overquota=0
Sep 14 18:11:05 ezm11-pco amavis[1130]: (01130-01) ESMTP
[127.0.0.1]:10024
/var/lib/amavis/tmp/amavis-20180914T181105-01130-c1dnU_QP:
-> SIZE=10997943 BODY=7BIT
Received: from smtp.easymail.ca ([127.0.0.1]) by localhost
(ezm11-pco.easydns.vpn [127.0.0.1]) (amavisd-new, port 10024) with ESMTP
for ; Fri, 14 Sep 2018 18:11:05 + (UTC)
Sep 14 18:11:05 ezm11-pco amavis[1130]: (01130-01) Checking:
MAOKJ8YSvJXH [64.68.203.197] ->
Sep 14 18:11:06 ezm11-pco amavis[1130]: (01130-01) spam-tag,
-> , No, score=0 required=4
tests=[BODY_SINGLE_WORD=0.001, SPF_PASS=-0.001] autolearn=ham
autolearn_force=no
Sep 14 18:11:06 ezm11-pco amavis[1130]: (01130-01) MAOKJ8YSvJXH FWD from
-> , BODY=7BIT 250 2.0.0 from
MTA(smtp:[127.0.0.1]:10025): 250 2.0.0 Ok: queued as 526FA207A9
Sep 14 18:11:06 ezm11-pco dovecot: auth: Debug: master in:
USER#0112#011ot...@quailmail.ca#011service=lmtp
Sep 14 18:11:06 ezm11-pco dovecot: auth-worker(17035): Debug:
sql(ot...@quailmail.ca): SELECT
CONCAT('maildir:/',volume,'/',SUBSTRING_INDEX(email,'@',-1),'/',SUBSTRING_INDEX(email,'@',1),'/Maildir')
AS mail,
CONCAT('/',volume,'/',SUBSTRING_INDEX(email,'@',-1),'/',SUBSTRING_INDEX(email,'@',1))
AS home, 5000 AS uid, 5000 AS gid, concat('*:storage=', volume_limit
,'G') AS quota_rule from easymail_users where email =
'ot...@quailmail.ca' and banned = '0' and active = '1'
Sep 14 18:11:06 ezm11-pco amavis[1130]: (01130-01) Passed CLEAN
{RelayedInbound}, [64.68.203.197]:1101 [64.68.203.197]
-> , Queue-ID: CD8CE2077F, Message-ID:
<0f892fdf-5e81-02bd-1985-240cb2650...@easydns.com>, mail_id:
MAOKJ8YSvJXH, Hits: 0, size: 10997943, queued_as: 526FA207A9, 1241 ms
Sep 14 18:11:06 ezm11-pco dovecot: auth: Debug: userdb out:
USER#0112#011ot...@quailmail.ca#011mail=maildir:/svmail/04/quailmail.ca/other/Maildir#011home=/svmail/04/quailmail.ca/other#011uid=5000#011gid=5000#011quota_rule=*:storage=1G
Sep 14 18:11:06 ezm11-pco dovecot: lmtp(ot...@quailmail.ca): Debug: auth
USER input: ot...@quailmail.ca
mail=maildir:/svmail/04/quailmail.ca/other/Maildir
home=/svmail/04/quailmail.ca/other uid=5000 gid=5000 quota_rule=*:storage=1G
Sep 14 18:11:06 ezm11-pco dovecot: lmtp(ot...@quailmail.ca): Debug:
Added userdb setting: mail=maildir:/svmail/04/quailmail.ca/other/Maildir
Sep 14 18:11:06 ezm11-pco dovecot: lmtp(ot...@quailmail.ca): Debug:
Added userdb setting: plugin/quota_rule=*:storage=1G
Sep 14 18:11:06 ezm11-pco postfix/smtp[17037]: CD8CE2077F:
to=, relay=127.0.0.1[127.0.0.1]:10024, delay=1.8,
delays=0.55/0/0.01/1.2, dsn=2.0.0, status=sent (250 2.0.0 from
MTA(smtp:[127.0.0.1]:10025): 250 2.0.0 Ok: queued as 526FA207A9)
Thank you
Ted
easyDNS Technologies
On 2018-09-19 12:55 PM, Aki Tuomi wrote:
>> On 19 September 2018 at 19:49 Ted wrote:
>>
>>
>> Hello,
>>
>> Most of the work was done with dovecot 2.2.27 but I just upgraded to
>> 2.3.2 and didn't see any change. Some debug logs are below, is there
>> something specific I could search them for?
>>
> Can you maybe try delivery to an account which should trigger quota warning
> or overquota action with mail_debug=yes?
>
> Aki
Re: Problem getting quota-warning script to function.
lt;8301>: Debug: Quota
warning: bytes=2040109465 (95%) messages=0 reverse=no
command=quota-warning 95 bill...@edwardcsmith.ca
Sep 17 23:19:16 ezm11-pco dovecot:
imap(bill...@edwardcsmith.ca)<8301>: Debug: Quota
warning: bytes=1932735283 (90%) messages=0 reverse=no
command=quota-warning 90 bill...@edwardcsmith.ca
Sep 17 23:19:16 ezm11-pco dovecot:
imap(bill...@edwardcsmith.ca)<8301>: Debug: Quota
warning: bytes=1717986918 (80%) messages=0 reverse=no
command=quota-warning 80 bill...@edwardcsmith.ca
Sep 17 23:19:16 ezm11-pco dovecot:
imap(bill...@edwardcsmith.ca)<8301>: Debug: Quota
grace: root=User quota bytes=214748364 (10%)
Sep 17 23:19:16 ezm11-pco dovecot:
imap(bill...@edwardcsmith.ca)<8301>: Debug: Namespace
: type=private, prefix=INBOX., sep=., inbox=yes, hidden=no, list=yes,
subscriptions=yes
location=maildir:/svmail/03/edwardcsmith.ca/billing/Maildir
Sep 17 23:19:16 ezm11-pco dovecot:
imap(bill...@edwardcsmith.ca)<8301>: Debug: maildir++:
root=/svmail/03/edwardcsmith.ca/billing/Maildir, index=, indexpvt=,
control=, inbox=/svmail/03/edwardcsmith.ca/billing/Maildir, alt=
Sep 17 23:19:16 ezm11-pco dovecot:
imap(bill...@edwardcsmith.ca)<8301>: Debug: Namespace
: type=private, prefix=, sep=, inbox=no, hidden=yes, list=no,
subscriptions=no location=fail::LAYOUT=none
Sep 17 23:19:16 ezm11-pco dovecot:
imap(bill...@edwardcsmith.ca)<8301>: Debug: none:
root=, index=, indexpvt=, control=, inbox=, alt=
Sep 17 23:19:16 ezm11-pco dovecot:
imap(bill...@edwardcsmith.ca)<8301>: Debug: quota:
quota_over_flag check: quota_over_script unset - skipping
Sep 17 23:19:16 ezm11-pco dovecot: auth: Debug: client passdb out:
OK#01160#011user=t...@edwardcsmith.ca#011home=/svmail/03/edwardcsmith.ca/ted#011uid=5000#011gid=5000#011quota_rule=*:storage=2G
Sep 17 23:19:16 ezm11-pco dovecot: auth-worker(8300): Debug: Module
loaded: /usr/lib/dovecot/modules/auth/libdriver_mysql.so
Sep 17 23:19:16 ezm11-pco dovecot: auth: Debug: master in:
REQUEST#011770310145#0111045#01160#0117968529039bd9545c6d15e171c19#011session_pid=8302#011request_auth_token
Sep 17 23:19:16 ezm11-pco dovecot: auth-worker(8299): Debug:
sql(t...@edwardcsmith.ca,64.68.203.197,): SELECT
CONCAT('maildir:/',volume,'/',SUBSTRING_INDEX(email,'@',-1),'/',SUBSTRING_INDEX(email,'@',1),'/Maildir')
AS mail,
CONCAT('/',volume,'/',SUBSTRING_INDEX(email,'@',-1),'/',SUBSTRING_INDEX(email,'@',1))
AS home, 5000 AS uid, 5000 AS gid, concat('*:storage=', volume_limit
,'G') AS quota_rule from easymail_users where email =
't...@edwardcsmith.ca' and banned = '0' and active = '1'
Sep 17 23:19:16 ezm11-pco dovecot: auth: Debug: client in:
AUTH#01161#011PLAIN#011service=imap#011session=5f7sZhl2IxRARMvF#011lip=172.17.10.211#011rip=64.68.203.197#011lport=143#011rport=5155#011resp=
Sep 17 23:19:16 ezm11-pco dovecot: auth: Debug: master userdb out:
USER#011770310145#011...@edwardcsmith.ca#011mail=maildir:/svmail/03/edwardcsmith.ca/ted/Maildir#011home=/svmail/03/edwardcsmith.ca/ted#011uid=5000#011gid=5000#011quota_rule=*:storage=2G#011auth_token=21114b3fb366b3868d3dbb5003156728ea5fdeb7
Sep 17 23:19:16 ezm11-pco dovecot:
imap(t...@edwardcsmith.ca)<8302>: Debug: Loading
modules from directory: /usr/lib/dovecot/modules
Sep 17 23:19:16 ezm11-pco dovecot:
imap(t...@edwardcsmith.ca)<8302>: Debug: Module loaded:
/usr/lib/dovecot/modules/lib10_quota_plugin.so
Sep 17 23:19:16 ezm11-pco dovecot:
imap(t...@edwardcsmith.ca)<8302>: Debug: Module loaded:
/usr/lib/dovecot/modules/lib11_imap_quota_plugin.so
Sep 17 23:19:16 ezm11-pco dovecot:
imap(t...@edwardcsmith.ca)<8302>: Debug: Module loaded:
/usr/lib/dovecot/modules/lib15_notify_plugin.so
Sep 17 23:19:16 ezm11-pco dovecot:
imap(t...@edwardcsmith.ca)<8302>: Debug: Module loaded:
/usr/lib/dovecot/modules/lib20_mail_log_plugin.so
Sep 17 23:19:16 ezm11-pco dovecot:
imap(t...@edwardcsmith.ca)<8302>: Debug: Added userdb
setting: mail=maildir:/svmail/03/edwardcsmith.ca/ted/Maildir
Sep 17 23:19:16 ezm11-pco dovecot:
imap(t...@edwardcsmith.ca)<8302>: Debug: Added userdb
setting: plugin/quota_rule=*:storage=2G
Sep 17 23:19:16 ezm11-pco dovecot:
imap(t...@edwardcsmith.ca)<8302>: Debug: Effective
uid=5000, gid=5000, home=/svmail/03/edwardcsmith.ca/ted
Sep 17 23:19:16 ezm11-pco dovecot:
imap(t...@edwardcsmith.ca)<8302>: Debug: Quota root:
name=User quota backend=count args=
Sep 17 23:19:16 ezm11-pco dovecot:
imap(t...@edwardcsmith.ca)<8302>: Debug: Quota rule:
root=User quota mailbox=* bytes=2147483648 messages=0
Sep 17 23:19:16 ezm11-pco dovecot:
imap(t...@edwardcsmith.ca)<8302>: Debug: Quota warning:
bytes=2040109465 (95%) messages=0 reverse=no command=quota-warning 95
t...@edwardcsmith.ca
Sep 17 23:19:16 ezm11-pco dovecot:
imap(t...@edwardcsmith.ca)<8302>: Debug: Quota warning:
by
Problem getting quota-warning script to function.
rning {
user = dovecot
mode = 0666
}
}
##
## Quota backends
##
# Multiple backends are supported:
# dirsize: Find and sum all the files found from mail directory.
# Extremely SLOW with Maildir. It'll eat your CPU and disk I/O.
# dict: Keep quota stored in dictionary (eg. SQL)
# maildir: Maildir++ quota
# fs: Read-only support for filesystem quota
plugin {
#quota = dirsize:User quota
#quota = maildir:User quota
#quota = dict:User quota::proxy::quota
quota = count:User quota
#quota = fs:User quota
}
/usr/local/bin/quota-warning.sh
#!/bin/sh
# warning email for approaching their quota
usage=$1
email=$2
/usr/bin/mailx -r "supp...@easydns.com" -s "Quota Usager Notification"
"${email:?}" < /home/vmail/quota"${usage:?}".txt
echo "$(date) ${usage} : ${email}" >> /var/log/quotatest.log
Thank you
Ted
easyDNS Technologies
Re: [Dovecot] postfix-dovecot-sasl help
On Mon, 13 Dec 2010 17:48:03 + Timo Sirainen wrote: > On 13.12.2010, at 17.41, Ted To wrote: > > > Dec 13 12:36:57 kahlo postfix/smtpd[26253]: warning: SASL > > authentication problem: unable to open Berkeley db /etc/sasldb2: No > > such file or directory Dec 13 12:36:57 kahlo postfix/smtpd[26253]: > > warning: SASL authentication problem: unable to open Berkeley > > db /etc/sasldb2: No such file or directory > > You're using Cyrus SASL there, not Dovecot SASL. Thank you! I don't know how I missed adding that line...
Re: [Dovecot] postfix-dovecot-sasl help
On Mon, 13 Dec 2010 17:15:00 + Timo Sirainen wrote: > On 13.12.2010, at 17.08, Ted To wrote: > > > On Mon, 13 Dec 2010 16:50:27 + > > Timo Sirainen wrote: > > > >> CRAM-MD5 is incompatible with PAM. > >> http://wiki.dovecot.org/Authentication/Mechanisms > > > > After reconfiguring the client to use LOGIN rather than CRAM-MD5, I > > still get the following error: http://pastebin.com/bnhxVajc. > > Set auth_debug_passwords=yes and look at the logs. Maybe they'll show > something helpful (unfortunately PAM is very unhelpful for debugging). Ah -- it is looking for /etc/sasldb2. Does this mean I can't use "passdb passwd-file"? Or is there something wrong with my configuration on the postfix side? Dec 13 12:36:57 kahlo postfix/smtpd[26253]: warning: SASL authentication problem: unable to open Berkeley db /etc/sasldb2: No such file or directory Dec 13 12:36:57 kahlo postfix/smtpd[26253]: warning: SASL authentication problem: unable to open Berkeley db /etc/sasldb2: No such file or directory
Re: [Dovecot] postfix-dovecot-sasl help
On Mon, 13 Dec 2010 16:50:27 + Timo Sirainen wrote: > CRAM-MD5 is incompatible with PAM. > http://wiki.dovecot.org/Authentication/Mechanisms After reconfiguring the client to use LOGIN rather than CRAM-MD5, I still get the following error: http://pastebin.com/bnhxVajc. On Mon, 13 Dec 2010 11:33:41 -0500 Jerry wrote: > Provide output from the postfinger tool. This can be found at > http://ftp.wl0.org/SOURCES/postfinger. # > > If the problem is SASL related, consider including the output from the > saslfinger tool. This can be found at > http://postfix.state-of-mind.de/patrick.koetter/saslfinger/. Thanks -- I'm using dovecot's sasl so saslfinger is not useful but the output from postfinger is: http://pastebin.com/ArWg50Ce.
[Dovecot] postfix-dovecot-sasl help
I'm trying to set up SMTP authentication on my server and am getting an authentication failed error. My client is set up to automatically select authentication method and tries CRAM_MD5. The http://wiki.dovecot.org/HowTo/PostfixAndDovecotSASL suggests "passdb pam" and "userdb passwd" -- is it possible to configure sasl authentication using a dovecot.conf like http://pastebin.com/6JWE5jp1? Thanks in advance, Ted To
