Open kiratin opened 3 years ago
hey @kiratin! The following information would be helpful for debugging:
apt
(besides what miab installs during setup/updates)?Hi @fspoettel !
Regards
As mentioned in the setup guide, MiaB does not support systems where other software has been installed and/or modified. It increases time required for triaging issues beyond a threshold that can be actively supported.
That being said, we may be able to isolate the issue:
/tmp
look like?/etc/dovecot/*
or create a /etc/dovecot/local.conf
?chrooting
dovecot?It would be great if you could run doveconf -a
and paste the output here.
a quick google turned up a thread on the dovecot mailing list that describes your problem. the issue was never resolved as far as I can tell.
Hi @fspoettel
Sorry for my late reply.
I am attaching the output of doveconf -a as a text file.
Regards doveconf.txt
Hm the doveconf output actually looks OK - assuming that chroot
settings are not overwritten in the internal user db which is rather unlikely in your case.
Can you check permissions on the following dirs:
/tmp
/tmp/systemd-private-${id}-dovecot.service-${...}
which should have a child /tmp
owner should be root
root
and permissions drwxrwxrwt
(777) for all of these. is that the case for you?
I had changed the permissions of the /tmp folder to 777. However I am not sure if /tmp had such a folder. I don't think it did.
By the way, I am writing in past tense as I have moved the Miab to a new server. And I should say, now it works perfectly and it was quite straightforward to move the data from the old server.
Great to hear that miab is now working for you! 🙌
Let's close this issue then as we can't reproduce it anymore? If it pops up again for you or someone else, we can always reopen and take it from here.
Hi,
Following are the logs from /var/logs/mail.log file right after sending an email from my Gmail account to an account managed by MiaB. The /tmp folder exists and writable. I would appreciate if somebody comes up with a fix to the problem.
Regards.
`Nov 24 06:14:56 box postfix/smtpd[18832]: connect from mail-ed1-x533.google.com[2a00:1450:4864:20::533]
Nov 24 06:14:56 box postfix/smtpd[18832]: warning: restriction `reject_authenticated_sender_login_mismatch' ignored: no SASL support
Nov 24 06:14:56 box postgrey[1160]: action=pass, reason=client whitelist, client_name=mail-ed1-x533.google.com, client_address=2A00:1450:4864:20:0:0:0:533/128, sender=MYEMAIL@gmail.com, recipient=MY_Miab@ACCOUNT.com
Nov 24 06:14:57 box postfix/smtpd[18832]: 004183F21D: client=mail-ed1-x533.google.com[2a00:1450:4864:20::533]
Nov 24 06:14:57 box postfix/cleanup[18834]: 004183F21D: message-id=00e401d6c229$1fa62c40$5ef284c0$@gmail.com
Nov 24 06:14:57 box opendkim[24515]: 004183F21D: s=20161025 d=gmail.com SSL
Nov 24 06:14:57 box opendmarc[899]: implicit authentication service: BOX.MYDOMAIN.COM
Nov 24 06:14:57 box opendmarc[899]: 004183F21D: gmail.com pass
Nov 24 06:14:57 box postfix/qmgr[1754]: 004183F21D: from=MYEMAIL@gmail.com, size=617933, nrcpt=1 (queue active)
Nov 24 06:14:57 box postfix/smtpd[18832]: disconnect from mail-ed1-x533.google.com[2a00:1450:4864:20::533] ehlo=2 starttls=1 mail=1 rcpt=1 data=1 quit=1 commands=7
Nov 24 06:14:57 lmtp(18836): Info: Connect from 127.0.0.1
Nov 24 06:14:57 box spampd[15945]: processing message 00e401d6c229$1fa62c40$5ef284c0$@gmail.com for MY_Miab@ACCOUNT.com
Nov 24 06:14:59 box spampd[15945]: clean message 00e401d6c229$1fa62c40$5ef284c0$@gmail.com (1.40/5.00) from MYEMAIL@gmail.com for MY_Miab@ACCOUNT.com in 2.55s, 618150 bytes.
Nov 24 06:14:59 lmtp(18836): Error: Temp file creation to /tmp/dovecot.lmtp. failed: No such file or directory
Nov 24 06:14:59 lmtp(18836): Info: Disconnect from 127.0.0.1: Temporary internal failure (in DATA)
Nov 24 06:14:59 box spampd[15945]: WARNING!! Error in process_request eval block: /usr/sbin/spampd: write error: Connection reset by peer
Nov 24 06:14:59 box postfix/lmtp[18835]: 004183F21D: to=MY_Miab@ACCOUNT.com, relay=127.0.0.1[127.0.0.1]:10025, delay=2.9, delays=0.19/0.01/0.01/2.7, dsn=4.4.2, status=deferred (lost connection with 127.0.0.1[127.0.0.1] while sending end of data -- message may be sent more than once)`