similar to: dovecot log shows: service=imap ... Error: Temp file, creation to /tmp/dovecot.imap. failed: No such directory

I am using dovecot 2.2 with plesk 12 and I have made no modifications to the dovecot config. Logwatch reports the messages below. The errors don't seem to appear for every imap connect as can be seen from the number of deliveries and successful logins. So what makes dovecot fail sometimes to create the /tmp/dovecot.imap? Dovecot Deliveries: 19 Dovecot IMAP and POP3 Successful Logins: 106

On 07.06.2017 23:42, Lars-S?ren Steck wrote: > Dear list, > > I'm currently facing problems when receiving eMails with attachments, at > least sometimes. > > My mailserver is set up with the tool 'Mailcow', and hence is based on > Dovecot (2.2.22 (fe789d2)) and Postfix. > > Usually, there are no problems with receiving mails. If a mail has an > attachment,

Dear list, I'm currently facing problems when receiving eMails with attachments, at least sometimes. My mailserver is set up with the tool 'Mailcow', and hence is based on Dovecot (2.2.22 (fe789d2)) and Postfix. Usually, there are no problems with receiving mails. If a mail has an attachment, however, it is possible that the following error occurs (extract from /var/log/mail.log):

Hello, We are using dovecot (2.2.10) and it's working great! When I enable chrooting by appending /./ to the homedirs I'm getting errors like this: mail1 dovecot[47074]: imap(user): Error: Temp file creation to /tmp/dovecot.imap.mail1.70079. failed: No such file or directory On the surface everything seems to be working fine and I have not been able to produce the error myself. Any

I just launched a new mailserver that is using dovecot. My previous mailserver used courier-mail. I am expecting better things with this new server, but I was use to some login information in logwatch that I am not seeing now. For example I would get: [IMAPd] Logout stats: ==================== User | Logouts | Downloaded | Mbox Size

I am using dovecot 2.2.27 with plesk 12 and I have made no modifications to the dovecot config. my log file frequently (but not always!) reports errors that /tmp/dovecot.imap could not be created. The errors don't appear for every imap connect but for about 5% to 10% of the time. I already attempted to solve the problem by adding the following line to /etc/dovecot/dovecot.conf but that

After the upgrade to CentOS 5.9, all my CentOS 5 installations report only "Unmatched Entries" in the "yum" section of their daily logwatch mails. It seems the filter script /usr/share/logwatch/scripts/services/yum got broken: --------8<--------8<--------8<--------8<--------8<--------8<--------8< [root at dns01 ~]# /usr/sbin/logwatch --print --service yum

On Mon, September 14, 2015 14:51, James B. Byrne wrote: > The Logwatch imapd service script distributed with CentOS-6 does not > generate anything when I run logwatch --service all on a cyrus-imapd > host. Is this expected behaviour? Is there a separate script for > cyrus-imapd or are their configuration options required to get the > existing script to work. > > I have found

Found an error or two from my logwatch report from yesterday, thought I would share this in hopes this is just first time run of the problem I noticed in the Kernel report section... Also not sure why there's an issue with automount either.... but I guess I could ask on that issue as well. I am not worried about the NAMED error, this is something that happens due to one of the services that

I've recently switched to using spamassassin via a sendmail milter, rather than using procmail to invoke it. This means that I get a number of messages appearing in my maillog, and then being reported by logwatch as unmatched entries. An example of such a messages is: Feb 27 04:33:09 quail sendmail[24780]: p1R4X46P024780[2]: URIBL blacklist\n\t* [URIs: tablettoxicspillsrx.ru]\n\t* 1.5

Below is a cut and past from my log files that are sent to me. This is from the last day that proftpd worked correctly. I'm not sure why proftpd was restarted as the log states: ################### LogWatch 5.2.2 (06/23/04) #################### Processing Initiated: Sun Feb 19 09:02:02 2006 Date Range Processed: yesterday Detail Level of Output: 0 Logfiles

Logwatch file shows last upgrade to the code was 2007. The unmatched entries are killing me in the reports. I figure there must be a newer utility centos has in the repo but I cannot find one. Is logwatch the only one that is included? thanks

Package: logwatch Version: 7.1-2 Severity: normal X-Debbugs-CC: richardaburton at hotmail.com Filing as a new bug, to have it publicly tracked. I hope the X-Debbug-CC works and you get the bug Id to answer to. > I was just wondering if you'd seen this bug (346502), it's filed against > logcheck-database (whatever that is), but it looks it's just another > logwatch

Hi All, I don't know enough about when errors are *really* errors. So I google a lot to read and learn. I have a few things in my Logwatch that I want to make sure I understand 1. smartd **Unmatched Entries** Problem creating device name scan list Device /dev/sda: using '-d sat' for ATA disk behind SAT layer. Device /dev/sdb: using '-d sat' for ATA disk behind SAT layer.

Howdy all, Question for anyone. I have centos 5.x on my server. Everyday I get a logwatch sent to my mailbox. I usually check every couple weeks and this time I got a surprise... Up until may 15th, the watch started with cron begin/ cron end and then went to http begin/end.... May 16th had the selinux (which I have disabled) and dovecot listings above the http begin. Cron was absent.

I updated the machine that I use for a web/email server last night to 5.9, and I have this in the logwatch report this morning: QUOTE: --------------------- Smartd Begin ------------------------ Warnings: Device: /dev/sda [SAT], WARNING: There are known problems with these drives, - 1 Time(s) **Unmatched Entries** smartd 5.42 2011-10-20 r3458 [x86_64-linux-2.6.18-348.el5] (local

Hi list, I have installed ClamAV from rpmforge and followed the excellent CentOS how to on installing amavisd - all has appeared to just work as advertised - thanks to all those involved in getting these instructions together. Come time to upgrade to 5.3 and ClamAV 0.95 (logwatch has been encouraging me to do the ClamAV upgrade for a week or two) All appeared to work fine. However I now notice

It seems there was some kind of attack against dovecot on my server (CentOS-5.5) with a hundred or so logwatch entries like: ========================================= **Unmatched Entries** dovecot-auth: pam_succeed_if(dovecot:auth): error retrieving information about user admin dovecot-auth: pam_succeed_if(dovecot:auth): error retrieving information about user webmaster

Hello, I noticed in my logwatch file I have an error with my rndc key. I could 'play' around with it and may fix it but most likey just hose things up. I think I see the problem but not 100% sure. I think the key file has 3 different names. Here's the error: **Unmatched Entries** /etc/named.conf:23: couldn't find key 'rndckey' for use with command channel

Every day I get emailed Logwatch reports with several entries of the following type. I've tried googling for these entries and found nothing that indicats if these represent any particular problem. We did not have these messages before and nothing really changed other than some RedHat updates. The system generally runs fine (~170 users) with only the occasional authentication glitch.