Author Topic: Connection to storage server failed  (Read 466 times)

Offline CarpCharacin

  • Jr. Member
  • **
  • Posts: 11
Connection to storage server failed
« on: November 17, 2018, 05:43:26 PM »
I tried to follow this guide : https://www.rosehosting.com/blog/how-to-set-up-server-side-email-filtering-with-dovecot-sieve-and-roundcube-on-a-centos-6-vps/ to set up mail ifltering, I already had spamassasin installed.  For the filtering, I just added the filter for the spamassasin spam tag, not the other one, and when it said to run ## chown vmail: -R /etc/dovecot/sieve
## chown vmail:mail /var/log/dovecot-* it just said chown: invalid spec 'vmail'.  I followed the guide after that, but I didn't get to the point where I could enable the RoundCube extension.  Now when I try to log in, it just says connection to storage server failed.  How do I fix this?  It is imperative that I get my email working again ASAP.

Offline JohnDoh

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 2,140
Re: Connection to storage server failed
« Reply #1 on: November 18, 2018, 02:55:57 AM »
you can't just skip errors. is the name of the user which your mail system run as vmail? it sounds like either a permissions error or some other error in your dovecot config is preventing it from starting. check the dovecot logs or may be the syslog.
Roundcube Plugins: Contextmenu, SpamAssassin Prefs, and more…

Offline CarpCharacin

  • Jr. Member
  • **
  • Posts: 11
Re: Connection to storage server failed
« Reply #2 on: November 18, 2018, 03:25:00 AM »
I'm not sure what the name of the user is, I just followed the guide.  I don't know much about setting up mail servers.  How do I check the dovecot logs?

Offline JohnDoh

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 2,140
Re: Connection to storage server failed
« Reply #3 on: November 18, 2018, 04:44:16 AM »
for assistance with dovecot configuration you would probably be better off asking in the dovecot community than here. dovecot logs might be in /var/log/dovecot or may be in syslog. it depends how you have configured dovecot to do the logging. one of these commands might also give some more info "systemctl status dovecot.service" and "journalctl -xe".

it sounds like you are trying to enable sieve filterting on an existing mail setup rather than starting from scratch. so can you got get the user and group information from there? (may be look in the existing configs or check the ownership information on the files which make up your mailbox)
Roundcube Plugins: Contextmenu, SpamAssassin Prefs, and more…

Offline CarpCharacin

  • Jr. Member
  • **
  • Posts: 11
Re: Connection to storage server failed
« Reply #4 on: November 18, 2018, 06:10:30 AM »
Yeah it's on an existing mail setup.  I'll run those commands and post the outputs.  I just really need to get my email working again.

Offline JohnDoh

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 2,140
Re: Connection to storage server failed
« Reply #5 on: November 18, 2018, 08:17:16 AM »
In that case could you not revert the changes you made or restore the previous version of your dovecot config from backup (presuming you have at least confirmed the issue really is that dovecot cannot start with the new config)?
Roundcube Plugins: Contextmenu, SpamAssassin Prefs, and more…

Offline CarpCharacin

  • Jr. Member
  • **
  • Posts: 11
Re: Connection to storage server failed
« Reply #6 on: November 18, 2018, 05:51:28 PM »
I'm not sure, I already followed the other steps in the guide, and I'd like to get the sieve working, since I have been getting like 200 spam emails a day.
Here is the output of systemctl status dovecot.service:
Code: [Select]
● dovecot.service - Dovecot IMAP/POP3 email server
   Loaded: loaded (/usr/lib/systemd/system/dovecot.service; enabled; vendor preset: disabled)
   Active: failed (Result: exit-code) since Sat 2018-11-17 04:33:48 UTC; 1 day 18h ago
  Process: 13942 ExecStart=/usr/sbin/dovecot -F (code=exited, status=89)
  Process: 13936 ExecStartPre=/usr/libexec/dovecot/prestartscript (code=exited, status=0/SUCCESS)
 Main PID: 13942 (code=exited, status=89)

Nov 17 04:33:48 cyprinidae.utahfishkeepers.us systemd[1]: Starting Dovecot IM...
Nov 17 04:33:48 cyprinidae.utahfishkeepers.us systemd[1]: Started Dovecot IMA...
Nov 17 04:33:48 cyprinidae.utahfishkeepers.us dovecot[13942]: Fatal: service(...
Nov 17 04:33:48 cyprinidae.utahfishkeepers.us systemd[1]: dovecot.service: ma...
Nov 17 04:33:48 cyprinidae.utahfishkeepers.us systemd[1]: Unit dovecot.servic...
Nov 17 04:33:48 cyprinidae.utahfishkeepers.us systemd[1]: dovecot.service fai...
Hint: Some lines were ellipsized, use -l to show in full.
and journalctl -xe:
Code: [Select]
Nov 18 22:50:08 cyprinidae.utahfishkeepers.us postfix/smtpd[29474]: fatal: no SASL a
Nov 18 22:50:08 cyprinidae.utahfishkeepers.us postfix/smtpd[29473]: connect from unk
Nov 18 22:50:08 cyprinidae.utahfishkeepers.us postfix/smtpd[29473]: warning: SASL: C
Nov 18 22:50:08 cyprinidae.utahfishkeepers.us postfix/smtpd[29473]: fatal: no SASL a
Nov 18 22:50:09 cyprinidae.utahfishkeepers.us postfix/master[13397]: warning: proces
Nov 18 22:50:09 cyprinidae.utahfishkeepers.us postfix/master[13397]: warning: /usr/l
Nov 18 22:50:09 cyprinidae.utahfishkeepers.us postfix/smtpd[29471]: connect from unk
Nov 18 22:50:09 cyprinidae.utahfishkeepers.us postfix/smtpd[29471]: warning: SASL: C
Nov 18 22:50:09 cyprinidae.utahfishkeepers.us postfix/smtpd[29471]: fatal: no SASL a
Nov 18 22:50:09 cyprinidae.utahfishkeepers.us postfix/master[13397]: warning: proces
Nov 18 22:50:09 cyprinidae.utahfishkeepers.us postfix/master[13397]: warning: proces
Nov 18 22:50:10 cyprinidae.utahfishkeepers.us postfix/master[13397]: warning: proces
Nov 18 22:50:10 cyprinidae.utahfishkeepers.us postfix/smtpd[29472]: connect from unk
Nov 18 22:50:10 cyprinidae.utahfishkeepers.us postfix/smtpd[29472]: warning: SASL: C
Nov 18 22:50:10 cyprinidae.utahfishkeepers.us postfix/smtpd[29472]: fatal: no SASL a
Nov 18 22:50:11 cyprinidae.utahfishkeepers.us dhclient[29495]: DHCPDISCOVER on lan4
Nov 18 22:50:11 cyprinidae.utahfishkeepers.us postfix/master[13397]: warning: proces
Nov 18 22:50:12 cyprinidae.utahfishkeepers.us postfix/smtpd[29492]: connect from unk
Nov 18 22:50:12 cyprinidae.utahfishkeepers.us postfix/smtpd[29492]: warning: SASL: C
Nov 18 22:50:12 cyprinidae.utahfishkeepers.us postfix/smtpd[29492]: fatal: no SASL a
Nov 18 22:50:13 cyprinidae.utahfishkeepers.us postfix/master[13397]: warning: proces
Nov 18 22:50:23 cyprinidae.utahfishkeepers.us dhclient[29495]: DHCPDISCOVER on lan4
Nov 18 22:50:38 cyprinidae.utahfishkeepers.us dhclient[29495]: DHCPDISCOVER on lan4

Offline JohnDoh

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 2,140
Re: Connection to storage server failed
« Reply #7 on: November 20, 2018, 12:46:24 PM »
Sadly other than confirming the dovecot does not start this does not tell us a lot. I think you are going to have to reach out to the dovecot community for help with this since it is alittle outside the scope of this forum. You could also try some the things mentioned here https://wiki2.dovecot.org/WhyDoesItNotWork particually the stuff about logging to see if you can find the error.
Roundcube Plugins: Contextmenu, SpamAssassin Prefs, and more…