similar to: odd entry in /var/log/messages

OK, let me try this again. . . . I'm a newbie to dovecot and a little bit less of a newbie to linux. I am in the process of moving my server from RH9 to FC2. The only obstacle remaining is my email. I run dovecot (v0.99.14) POP3 and sendmail (8.12.11-4.6) with Mozilla (1.4.2 and others), Thunderbird (1.0.2) and Netscape (7.1 on PC's, etc) mail clients - mostly PC's (W2K, WXP).

I'm a newbie to dovecot and a little bit less of a newbit to linux. I am in the process of moving my server from RH9 to FC2. The only obstacle remaining is my email. I run sendmail with netscape mail clients - mostly PC's. They all can read their mail but none of the users can send. Depending on the state of the dovecot.conf file, I get the following: Mar 28 16:04:14 corvette

OK. Why does saslauth ship on CentOS4 with a saslpasswd application that creates a db called /etc/sasldb and a sasldblistusers application that will look nowhere else while the sendmail that ships with it looks for /etc/sasldb2??? Where is this getting set? sendmail[25343]: unable to open Berkeley db /etc/sasldb2: No such file or directory Regards, Jim -- *** e-mail is not a secure channel

since updating to 5.9 a little while ago I find a load of these in /var/log/messages, which I've not seen before: Jan 17 22:17:18 fcshome ntpd[4680]: sendto(216.230.228.211) (fd=22): Invalid argument Jan 17 22:17:20 fcshome ntpd[4680]: sendto(199.4.29.166) (fd=22): Invalid argument Jan 17 22:17:31 fcshome ntpd[4680]: sendto(129.70.132.37) (fd=22): Invalid argument Jan 17 22:34:22 fcshome

Just discovered these messages in /var/log/messages, while looking at the USB problem I just posted about, separately. Apr 27 20:23:16 fcshome kernel: NVRM: API mismatch: the client has the version 331.67, but Apr 27 20:23:16 fcshome kernel: NVRM: this kernel module has the version 331.49. Please Apr 27 20:23:16 fcshome kernel: NVRM: make sure that this kernel module and all NVIDIA driver Apr 27

I've looked thru all the stuff at sendmail.org (or whatever its name is now, they seem to have gone corporate...) and don't see anything relating to this: I get a series of log entries in /var/log/maillog, once or twice a day at various times--not 12 or 24 hours apart. not always the identical series either. here's the latest one: Oct 27 21:28:55 fcshome sendmail[7939]: starting

Hi I configured my postfix that i can access the file /etc/sasl2/sasldb2 and authorize the users how are added in this database. My smtpd.conf looks like this: mech_list: PLAIN LOGIN pwcheck_method: auxprop auxprop_plugin: sasldb My saslauthd is not running. And when i telnet to port 25 i can authorize my self like this: telnet localhost 25 Trying 127.0.0.1... Connected to localhost. Escape

Hi guys, I am trying to migrate my NT 4 users to samba and these are the steps that I used for installing samba. BerkeleyDB ../dist/configure --prefix=/usr make make install MIT Kerberos ./configure --prefix=/usr make make install make check OpenSSL ./config --openssldir=/usr make make install Cyrus SASL cd cyrus-sasl-2.1.19 ./configure --prefix=/usr

Hello, I'm having trouble to get saslauthd running on a centos-5.3. I can't autheticate via testsaslauthd. Here's what I do using a fresh /etc/sasldb2: 1) start saslauthd in debug mode: saslauthd -d -a shadow -O /usr/lib64/sasl2/smtpd.conf -r -l 2) saslpasswd2 -c -a mail -u mail testuser 3) testsaslauthd -u testomat -p <mypassword> -s smtp -r mail shell output of

I'm getting these messages during boot: error: failure reading sector 0xfc from 'hd4' error: failure reading sector 0xe0 from 'hd4' error: failure reading sector 0x0 from 'hd4' error: failure reading sector 0xfc from 'hd5' error: failure reading sector 0xe0 from 'hd5' error: failure reading sector 0x0 from 'hd5' they pop up soon after the Grub

Dear list, I have been struggling to get working a PDC using Samba with LDAP backend, in a fresh Debian Sarge install. 1. SeMachineAccountPrivilege I'm reading IDEALX's Linux Samba-OpenLDAP Howto as guidance. In my last attempt, everything appeared to be fine until the very end, the Integration test, when I added an admin user, got it on the "Domain Admin" and then tried to

Hi, Do you know if sieve implementation on cyrus-imapd package is working correctly ? When trying to connect to timsieved at localhost with sieveshell I'm getting the following error: $ sieveshell --user=al --authname=cyrus localhost connecting to localhost unable to connect to server at /usr/bin/sieveshell line 169 The configuration on /etc/cyrus.conf is by defult. Port 2000 is listening

Occasionally and without any action on my part, I get a popup saying I need to authenticate in order to read others' actions. I have no clue what this is for, so I always reject them. Anyone got a clue? Image attached. -- ---- Fred Smith -- fredex at fcshome.stoneham.ma.us ----------------------------- But God demonstrates his own love for us in this:

On Thu, Aug 1, 2019 at 8:53 PM Fred Smith <fredex at fcshome.stoneham.ma.us> wrote: > .... reveals that of all the source addresses trying to poke at 48825, > there are 193 unique addresses. Either this indicates a heck of a lot > of sites having at my firewall, or that some few sites are all spoofing > their addresses. I can sort of understand people whaling away at ports >

On Fri, Aug 02, 2019 at 02:38:05PM -0400, Jon LaBadie wrote: > On Fri, Aug 02, 2019 at 10:19:49AM -0400, mark wrote: > > Fred Smith wrote: > > > On Fri, Aug 02, 2019 at 09:28:23AM -0400, mark wrote: > > <MVNCH> > > > One thing I don't understand is how/why the firewall is DROPping so > > > many attempts on port 25 when it in fact has a port

On Mon, Jun 20, 2016 at 05:02:32PM -0400, m.roth at 5-cent.us wrote: > Fred Smith wrote: > > On Mon, Jun 20, 2016 at 04:13:35PM -0400, m.roth at 5-cent.us wrote: > >> Fred Smith wrote: > >> > On Mon, Jun 20, 2016 at 02:59:29PM -0400, Jon LaBadie wrote: > >> >> On Mon, Jun 20, 2016 at 08:58:54AM -0400, Fred Smith wrote: > >> >> > On

Description of problem: I try to build a libvirt package for the IPFire project (http://www.ipfire.org/). Without sasl libvirt build fine but with sasl libvirt fails to build with the following message: CC rpc/libvirt_net_rpc_la-virnetsaslcontext.lo In file included from rpc/virnetsaslcontext.h:25, from rpc/virnetsaslcontext.c:26: /usr/include/sasl/sasl.h:230: error:

hi all! back in Aug several of you assisted me in solving a problem where one of my drives had dropped out of (or been kicked out of) the raid1 array. something vaguely similar appears to have happened just a few mins ago, upon rebooting after a small update. I received four emails like this, one for /dev/md0, one for /dev/md1, one for /dev/md125 and one for /dev/md126: Subject: DegradedArray

Hi, I'm running Samba 3.0 on a Solaris 9 server. If you look at the output of top you'll see that that nmbd process is killing this machine: I've restarted Samba numerous times, and each time the load goes down immediately and when I restart it the load goes up and nmbd starts to take up all the processor time. load averages: 21.18, 19.61, 24.65 11:04:20 210 processes: 187

Every now and then I get an alert like this one. I have no clue what this "rear" subsystem is, or why madam would be trying to write to its log file. Can anyone enlighten me? thanks in advance! ------------------------- SELinux is preventing /usr/sbin/mdadm from write access on the file /var/log/rear/rear-fcshome.log.lockless. ***** Plugin restorecon (93.9 confidence) suggests