[BlueOnyx:19987] Re: Dovecot Error

Hi, > Thanks Michael. But what happens with all mails when I delete the mbox file? > Will they be deleted too? Yes, that will delete all mails and the mbox file will get recreated when the first new email comes in. Like said: As is the mbox file appears to be corrupted, so it is of dubious use.

[BlueOnyx:19986] Re: Dovecot Error

Thanks Michael. But what happens with all mails when I delete the mbox file? Will they be deleted too? NETgemacht.at Hochfügenerstraße 7 6263 Fügen Socialize me: www.facebook.com/netgemacht Visit me: www.netgemacht.at

[BlueOnyx:19985] Re: Hacker - what to do next

Hi Mitchell, >> APF: > Take out port 22 from apf firewall - ports > And add my static ip's to apf - whitelist Correct. Say your IP is x.x.x.x and your SSH runs on port 22, then you would use this line for whitelisting: d=22:s=x.x.x.x/32 -- With best regards Michael Stauber ___

[BlueOnyx:19984] Re: Error: Package: 2:postfix-2.6.6-6.el6_7.1.x86_64 (sl)

Hi Michael That's done the trick, its now doing a large Yum date which seems to be going ok at present Thank you for the fix Kind regards Richard -Original Message- From: Blueonyx [mailto:blueonyx-boun...@mail.blueonyx.it] On Behalf Of Michael Stauber Sent: 16 August 2016 17:32

[BlueOnyx:19983] Re: Hacker - what to do next

Thank Michael - really appreciate your continued support. >If APF is installed: The SSH GUI management page then gets extended by an APF module and you can lock down SSH access via GeoIP, so that logins only work from certain countries. This is great - I never knew this was there. >Additionally

[BlueOnyx:19982] Re: Dovecot Error

Hi, > Error: Next message unexpectedly corrupted in mbox file mbox at > 838655947 > > I raised the quota for the user. But I still get the same error. It appears that the mbox file of that user is corrupted. The easiest fix would be to go to the users home directory and to delete the mbox file.

[BlueOnyx:19981] Re: Error: Package: 2:postfix-2.6.6-6.el6_7.1.x86_64 (sl)

Hi Richard, > We are getting the following errors when yum update is trying > to run and failing System is a 5308R and was working fin up > until 12th August This is perhaps an install from an older ISO which incorrectly contained both the sendmail and the postfix RPMs. You can fix it this way a

[BlueOnyx:19980] Re: Unable to set IP for a domain

ok working now had to disable IP Address Allocation RC -- /*Richard C. Barker Sr. CEO & President 1-800-510-3139 ProBass Networks Inc. */ www.probassnetworks.net www.probass.net *** DISCLAIMER : - This e

[BlueOnyx:19979] Unable to set IP for a domain

The IP is in the IP Address Allocation tab and has also been added to the VPS on the master node below is the errors from log *The IP address x.x.x.x is not allowed. Please choose another IP address. * *Aug 16 09:44:01 systemd: Started Session 1398846 of user root. Aug 16 09:44:01 systemd: St

[BlueOnyx:19978] Re: Dovecot Error

I raised the quota for the user. But I still get the same error. NETgemacht.at Hochfügenerstraße 7 6263 Fügen Socialize me: www.facebook.com/netgemacht Visit me: www.netgemacht.at Call me:0676/943 6

[BlueOnyx:19976] Re: Dovecot Error

I had the same error and it was the user is over quota RC -- /*Richard C. Barker Sr. CEO & President 1-800-510-3139 ProBass Networks Inc. */ www.probassnetworks.net www.probass.net *** DISCLAIMER : - Thi

[BlueOnyx:19977] Error: Package: 2:postfix-2.6.6-6.el6_7.1.x86_64 (sl)

Hi We are getting the following errors when yum update is trying to run and failing System is a 5308R and was working fin up until 12th August Loaded plugins: blueonyx, security Cleaning repos: BlueOnyx-520XR Solarspeed.net Solarspeed.net-AVSPAM-v6 sl : sl-security Cleaning up E

[BlueOnyx:19975] Dovecot Error

I see following error(s) in my maillog: Aug 16 13:50:26 www dovecot: imap(r.gruber): Error: Next message unexpectedly corrupted in mbox file mbox at 838655947 Aug 16 13:50:26 www dovecot: imap(r.gruber): Panic: file mbox-sync.c: line 152 (mbox_sync_read_next_mail): assertion failed: (sync_ctx->i

[BlueOnyx:19974] Re: Error after PHP update this morning on PHP 5.3

Thanks Michael That did indeed get me back in to the GUI, and everything seems to be working except Now I'm getting this error when access phpMyAdmin A PHP Error was encountered Severity: Warning Message: session_start() [function.session-start]: open(/var/lib/php/session/sess_4ce8a12a4