search for: ungraded

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 With the sieve plugin trying to redirect or send vacation reply I'm getting the following error: Aug 19 13:12:52 goku deliver(joeblow): [ID 619685 mail.info] Module loaded: /use rM/mail-services/dovecot/lib/dovecot/lda/lib90_cmusieve_plugin.so Aug 19 13:12:52 goku deliver(joeblow): [ID 848615 mail.info] mbox:

When ungraded from Ubuntu 11.04 to 11.10, dovecot can't start successfully with lots of errors i.e. "dovecot: doveconf: Warning: ... 'imaps' protocol is no longer necessary, remove it"... At any rate, I want to setup a postfix(MTA)/dovecot(MDA) servers on Ubuntu 11.10, by following the Pos...

I ungraded my Linux Operating system from Ubuntu 16.04 LTS to 8.04 LTS Samba will not start after an upgrade to 18.04. My samba is running as an NT style member server server with smbd nmbd and winbindd all running. None of them will start. It worked this morning. This morning it was running Version 4.3....

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello, I'm testing out dovecot with postfix. I'm running postfix 2.5.2 with dovecot version 1.1.1 with dovecot sieve plugin version 1.1.5. I have everything compiled and working except for the sieve plugin. I'm now trying to test out the sieve plugin and having no luck in getting a simple auto vacation reply to work. Here is my

...ou have Samba up properly, then return to just 127.0.0.1.] --- Now, as noted, this is for an AD setup - which I have no familiarity with, in regards to current Samba, so the above might not apply. But it's worth a try - easy to roll-back if it doesn't fix anything etc. -Greg RSvs> I ungraded my Linux Operating system from Ubuntu 16.04 LTS to 8.04 LTS RSvs> Samba will not start after an upgrade to 18.04. My samba is running as RSvs> an NT style member server server with smbd nmbd and winbindd all RSvs> running. None of them will start. RSvs> It worked this morning. RSvs&...

...h> <format type='unknown'/> </target> </volume> ============================================== It should read =============================================== ... <path>sheepdog:debian.iso</path> ... =============================================== I ungraded the system to Debain testing now running: ================================================ virsh # version Compiled against library: libvirt 1.2.21 Using library: libvirt 1.2.21 Using API: QEMU 1.2.21 Running hypervisor: QEMU 2.4.0 ================================================ The Problem ist...

On Sun, 24 Feb 2019 13:08:07 -0500 Robert Steinmetz <rob at steinmetznet.com> wrote: > Rowland Penny via samba wrote: > On Sat, 23 Feb 2019 19:55:03 -0500 > Robert Steinmetz via samba <samba at lists.samba.org> wrote: > > I ungraded my Linux Operating system from Ubuntu 16.04 LTS to 8.04 LTS > > Samba will not start after an upgrade to 18.04. My samba is running > as an NT style member server server with smbd nmbd and winbindd all > running. None of them will start. > > It worked this morning. > > T...

....0.1.] > > --- > > Now, as noted, this is for an AD setup - which I have no familiarity > with, in regards to current Samba, so the above might not apply. > But it's worth a try - easy to roll-back if it doesn't fix anything etc. > > -Greg > > > *RSvs> I ungraded my Linux Operating system from Ubuntu 16.04 LTS to > 8.04 LTS > > RSvs> Samba will not start after an upgrade to 18.04. My samba is > running as > RSvs> an NT style member server server with smbd nmbd and winbindd all > RSvs> running. None of them will start. > >...

...blem" or attempts to actively exercises the >overflows. I guess you should try the exploit scripts or demos (see the bugtraq >archives and rootshell.com, for example). IMAP 4.1 final has not been attacked >successfully on bugtraq yet. >All the name servers I have control over are ungraded to the latest version of >bind version 8 (the change notification of the secondaries is a worthwhile >feature and the ISC claim that bind v8 works better with lots of domians). >We will do probably need some DNS Sec support time as ISPs so it seemed to be >the way to go. >There a...

...ured the same at all of our sites and we have no problems with it. In the samba log, we see the message 'request_oplock_break failed' frequently. That is the only thing we can find regarding Samba in any of the logs. Things we have tried: Uninstalling and reinstalling Samba Ungraded Linux from 6.2 to 7.0 - No reason, just out of desperation I guess. It didn't help. Uninstalling and reinstalling Postgres - Once again, motivated by desperation To eliminate hardware possibilities we have : Checked resources while a user is connected, they are fine. Replaced...