![]() ![]() I wonder if it's related to me adding the prefixes "INBOX.Junk", to keep compatibility with cronjobs and other stuff. it's been there even before the migration to this mailserver. That's not very nice of Dovecot, is it? Worst case scenario it should just deliver to Inbox and possibly an extra email explaining that the Junk folder could not be created.Īnd the thing is that the Junk folder DOES exist. Apologies for the delay.Ĭonclusion: When dovecot is not able to create the Junk folder, mail is bounced with 451 4.2.0 I didn't receive an email with your comments above. If you have any idea which could explain why your dovecot wasn't able to create the Junk directory, please let me know. In order to identify the root of this bug, could you give the following informations: (in reply to end of DATA command))Ĭonclusion: When dovecot is not able to create the Junk folder, mail is bounced with 451 4.2.0 Further investigations May 11 11:47:49 mail dovecot: Error: sieve: Execution of script /usr/lib/dovecot/sieve-global/before/60-spam.sieve was aborted due to temporary failure May 11 11:47:49 mail dovecot: Error: sieve: msgid=: **failed to store into mailbox 'Junk': Internal error occurred.** Refer to server log for more information. Refer to server log for more information. May 11 11:47:49 mail dovecot: Error: Mailbox Junk: Failed to autocreate mailbox: Internal error occurred. May 11 11:47:49 mail dovecot: Error: Couldn't create mailbox list lock /var/mail/otherdomain.tld/quotauser/mailboxes.lock: file_create_locked(/var/mail/otherdomain.tld/quotauser/mailboxes.lock) failed: safe_mkstemp(/var/mail/otherdomain.tld/quotauser/mailboxes.lock) failed: Permission denied # Seen dovecot-sieve is always enabled, setting `maildir_stat_dirs = yes` permits May 10 09:50:41 server postfix/anvil: statistics: max cache size 2 at May 10 cat /etc/dovecot/conf.d/nf | grep stat_dirs May 10 09:50:41 server postfix/anvil: statistics: max connection count 1 for (smtpd:) at May 10 09:42:21 May 10 09:50:41 server postfix/anvil: statistics: max connection rate 1/60s for (smtpd:) at May 10 09:42:21 May 11 03:30:27 server postfix/scache: statistics: max simultaneous domains=1 addresses=1 connection=8 May 11 03:30:27 server postfix/scache: statistics: domain lookup hits=3 miss=8 success=27% May 11 03:30:27 server postfix/scache: statistics: start interval May 11 03:27:06 Where can I see/change this configuration? This mailserver is purely for one Business/Purpose, so making "global" changes like these "should be ok" (doesn't affect other people) - but really appreciate your tips. I actually had SPAMASSASSIN_SPAM_TO_INBOX=1,īut I'm adding MOVE_SPAM_TO_JUNK=0 now too. ![]() I'm glad a simple restart accommodated this, but unfortunately my hands are tied as I cannot know what exactly HAPPENED. ![]() (in reply to end of DATA command))ĭoes this mean no one could send emails and were getting bounces? Looking at the "mail.log" / "mail.warn", I don't see any obvious error at the time it stopped responding, but I do see loads of these since: "mail.err" only had loads of errors of "60-spam.sieve" not being able to create the "Junk" folder. Do you think this could have been an IP ban? The cron that connects has all correct passwords. The fail2ban.log seems to be cleared on restart, so I can't see it it was an IP ban. The problem got fixed when I restarted Docker service, when I woke up.Īfter that, I tried to look at the logs. Installed this mailserver a few days ago, and has been working well enough.Īt an apparently "random" time last night (3:24 am GMT), the mailserver stopped working for no apparent reason.īy "stopped working", I mean that IMAP connections were all timing out and no emails were being received (and possibly not sent too).Ĭan't connect to 192.168.0.10,993: Connection timed out (errflg=2) ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |