similar to: Bug#363336: logcheck-database: incomplete regexp for popa3d log message

Hello, I tried to migrate from popa3d to dovecot but I couldn't manage with 'pop3_reuse_xuidl = yes' option. First of all it turned out that the feature is not supported in dovecot for Fedora Core 4 (dovecot-0.99.14-4.fc4). So I downloaded latest stable release of Dovecot but it didn't have this option included too. Then I compiled the newest alpha version (dovecot 1.0.alpha4)

Hello, I'm sure there is no good answer to my question, but it doesn't take much to ask, so I will. I am about to migrate my current Dovecot IMAP + Popa3d mailbox server to Maildir. I need to keep both protocols (IMAP and POP3) and will be switching to Dovecot on both. The question is simple - is there any way to keep POP3 UIDs through migration, so people won't get duplicates

Package: logcheck Version: 1.2.43a Severity: wishlist The conf file currently says # Should the hostname of the generated mails be fully qualified? FQDN=1 I suggest rewording that to # Should the hostname in the subject of the generated mails be fully qualified? FQDN=1 The current wording led me to believe that the sender, and perhaps recipient (if otherwise unqualified) of the emails generated

Hi, I am using Winbind & NSS/PAM on Debian Linux, joined to a Windows 2000 AD Domain, to provide email (SMTP/POP3) based on Windows username and password. I have two Windows 2000 Servers for domain controllers, DC1 and DC2. Over the weekend DC2 had a CPU fan fail and it overheated and crashed. Once DC2 failed, PAM Winbind stopped working and my users could no longer log into their

Hello all, We have put Dovecot 2.1.4 on several of our production servers (CentOS, on Dell R710, with 20GB memory, dual CPU Quad-core). We have a single instance of Dovecot running and currently have several instances of Popa3d. When there are significant amount of popping from 2 mailboxes that dovecot that is popping from (500+ msgs in the mailboxes), the popping of the messages causes the

Hello all, I hope someone can help me, I have been testing out Dovecot to switch from popa3d which I use at the moment. When I get several users connecting and disconnection multiple times, the Dovecot process with command Auth uses 50-90% of the CPU for the period which they are connecting. I am wondering if there is something that I may have misconfigured, or if there is something that I can

Hi! I'm having some problem with our setup. I have a linux server authenticating from a win2k3 domain controller via winbind and pam. When i try to log in I receive the following error messages: Jul 3 10:26:10 zeusz pam_winbind[20375]: user 'tamas' granted access Jul 3 10:26:10 zeusz pam_winbind[20375]: user 'tamas' OK Jul 3 10:26:10 zeusz pam_winbind[20375]: user

This is my first post to this list. The domain names etc have been changed slightly in the examples below, but you should get the idea. For a long time now (since 3.0.2a?), I have been using the samba 3.0.x series at one of our client sites. The Linux server is joined to a Win2k3 Active Directory. All users are created in the ADS, and the Linux server is able to authenticate them, etc. I

hello hpa, here my birthday submission :) please pull: git pull git://git.debian.org/users/maks/klibc.git maks Sam fixed a longstanding x86_32 build bug, thus it seems a good time to flush the queue of the piled up patches, the shortlog tells it: Aurelien Jarno (1): [klibc] sh4: syscalls fixes Benjamin Cama (1): [klibc] fstype: btrfs size endianness fix Mike Waychison (2):

Package: logcheck Version: 1.2.43a Severity: minor /etc/logcheck/ignore.d.server/ntp contains: ^\w{3} [ :0-9]{11} [._[:alnum:]-]+ ntpd\[[0-9]+\]: adjusting local clock by [.0-9]+s$ However, this will not match negative corrections such as: System Events =-=-=-=-=-=-= Mar 5 01:44:55 billchase ntpd[6171]: adjusting local clock by -0.190112s Mar 5 01:55:20 billchase ntpd[6171]: adjusting local

Package: logcheck Version: 1.2.43a Severity: normal -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I have messages like these in my logs: Apr 27 10:05:49 localhost smartd[9357]: Device: /dev/hda, SMART Prefailure Attribute: 1 Raw_Read_Error_Rate changed from 58 to 57 Apr 27 10:05:49 localhost smartd[9357]: Device: /dev/hda, SMART Usage Attribute: 195 Hardware_ECC_Recovered changed from 58 to 57

Package: logcheck-database Version: 1.3.13 Severity: normal The rule for SSH ignoring "Bad protocol version identification" assumes there are no single quotes inside the version string ('[^']'). I am however getting mails including those lines: Mar 25 22:57:04 Debian-60-squeeze-64-minimal sshd[12144]: Bad protocol version identification

Package: logcheck Version: 1.2.43a Severity: normal -- System Information: Debian Release: testing/unstable APT prefers testing APT policy: (900, 'testing'), (800, 'unstable') Architecture: i386 (i586) Kernel: Linux 2.6.10 Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 Versions of packages logcheck depends on: ii adduser 3.77 Add and remove

Package: logcheck-database Version: 1.3.8 Severity: wishlist HI, can you please create a rule/some rules for amavis(d-new). I get for every mail this mesage: May 25 19:55:40 data amavis[9603]: (09603-15) Passed CLEAN, [::1] [213.165.64.22] <xxx at yyy.zz> -> \ <aaa at localhost>, Message-ID: <20100525175015.29677page1 at mx002.bbb.ccc>, mail_id: MM7upJv6se1Z, \ Hits:

Package: logcheck-database Version: 1.3.13 Severity: normal Tags: patch After upgrading to debian squeeze I get several messages a day in the form of: Jul 2 15:05:15 hostname spamd[21286]: spamd: handled cleanup of child pid [28609] due to SIGCHLD: exit 0 This is due to an update in spamd, that makes the message more detailed (includes exit code)[1]. Therefore messages including exit code 0

Just a quick question or maybe a suggestion, is there a gem/plugin that will convert ruby regexp to javascript regexp? Thanks -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to rubyonrails-talk-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org To unsubscribe from this group, send email to

Package: logcheck-database Version: 1.2.43a Severity: minor Since last weekend's upgrade of logcheck-database from 1.2.42 to 1.2.43a, logcheck stopped ignoring routine SpamAssassin messages of the form Feb 20 21:36:16 tux64 spamd[4665]: spamd: checking message <20060220190721.0E0B41C5207 at llwb563.servidoresdns.net> for amu:7286 Could you please edit the second pattern in

Hi! When the 1.0 release is planed?

I would look at using serveral machine splitting up the load using one 4 port card in each. > -----Original Message----- > From: asterisk-users-bounces@lists.digium.com > [mailto:asterisk-users-bounces@lists.digium.com] On Behalf Of > janvb@caselaboratories.com > Sent: Tuesday, January 10, 2006 6:03 AM > To: Asterisk Users Mailing List - Non-Commercial Discussion >

I notice in recent commits that a number of these have been added: /\[(\d+)\]/.freeze I thought that Regexps are immutable. Furthermore, Regexp literals don''t generate a new object each time they are encountered: irb(main):001:0> 3.times { puts /\d+/.object_id } -605707646 -605707646 -605707646 => 3 irb(main):002:0> Unlike strings: irb(main):002:0> 3.times { puts