Index: [Article Count Order] [Thread]

Date:  Thu, 11 Aug 2005 10:48:43 -0500 (EST)
From:  "Ing. Ernesto =?iso-8859-1?Q?P=E9rez_Est=E9vez?=" <info (at mark) ecualinux.com>
Subject:  [coba-e:02682] Re: corrupt mbox issue  - possible locking      issue between qpopper and imapd?
To:  coba-e (at mark) bluequartz.org
Message-Id:  <33005.200.107.41.116.1123775323.squirrel (at mark) www.ecualinux.com>
In-Reply-To:  <FHEHJDFBKIPALHNNPMAEAEOCCDAA.mon (at mark) rhapsody.com.hk>
References:  <42F9F6F1.3010201 (at mark) ecualinux.com>    <FHEHJDFBKIPALHNNPMAEAEOCCDAA.mon (at mark) rhapsody.com.hk>
X-Mail-Count: 02682

/usr/sbin/poprelayd

regards
ernesto
> hi ernesto
>
> thank you
> i want to know where is scanaddr?
>
> Mon
>
>
> -----Original Message-----
> From: "Ing. Ernesto PñÓez Estñ×ez" [mailto:info (at mark) ecualinux.com]
> Sent: Wednesday, August 10, 2005 8:46 PM
> To: coba-e (at mark) bluequartz.org
> Subject: [coba-e:02673] Re: corrupt mbox issue - possible locking issue
> between qpopper and imapd?
>
>
> for the records, here is the scanaddr I use for dovecot:
> sub scanaddr ($) {
>      my $s = $_[0];
>      my @paddrs;         # Packed IP addresses.
>      my @addrs;          # ASCII addresses.
>
>      if ($s =~ '^(... .. ..:..:..) \S+ (?:pop3|imap)-login: Login: .+
> \[(\d+\.\d+\.\d+\.\d+)\]'){
>          my $authuser = $2;
>          return $authuser;
>      }
>
>      return ();
> }
>
> It is working for me now, I can pop before relay with dovecot using it.
>
> regards
> ernesto
>
> Mon Chan wrote:
>> if disable Qpopper, the POP Authenticated Relaying seem can't work with
>> Dovecot or imap-2002d?
>>
>> Mon
>>
>> -----Original Message-----
>> From: patricko [mailto:patricko (at mark) staff.singnet.com.sg]
>> Sent: Friday, July 29, 2005 10:42 AM
>> To: coba-e (at mark) bluequartz.org
>> Cc: acroft (at mark) cyber-wizard.com
>> Subject: [coba-e:02651] Re: corrupt mbox issue - possible locking issue
>> between qpopper and imapd?
>>
>>
>> Hi,
>>
>>
>> I recommend Dovecot or imap-2002d for your
>> POP3 and IMAP services.
>>
>> In another word, disable Qpopper altogether.
>>
>> By using an all-in-one daemon, it will takes care of
>> the inter-processes locking.
>>
>> Cheers
>> patrick
>>
>>
>>
>>
>>
>>
>>
>>
>> On Thu, 28 Jul 2005 12:34:43 -0500
>> Albert Croft <acroft (at mark) cyber-wizard.com> wrote:
>>
>>
>>>I have recently been encountering issues with several users having their
>>> mbox become corrupt (that is, there is text before the first "From user
>>> date" line, the removal of which normally resolves the issue). We built
>>> a new server this weekend, using CentOS4 and the
>>> BlueQuartz-5100R-2005040901.tgz file, and migrated the users over to it.
>>> The problem followed the users.
>>>
>>>Since the migration, I have had the issue occur at least three (3)
>>> times, two of which being the same user. The only other connections I
>>> had determined between the users experiencing the issue were that each
>>> of them receives large amounts of email, and each uses a BlackBerry
>>> device for checking mail when out of the office. As a result of
>>> examining entries in /var/log/maillog following these incidents (the
>>> entries pertaining to one incident are included at the end of this
>>> message, modified only to conceal the hostnames/IPs of the innocent), it
>>> would appear as if the POP3 (qpopper-4.0.5-1BQ4) and IMAP
>>> (imap-2002d-9BQ2) daemons are not seeing each other's locks or have
>>> incompatible locking mechanisms, or there may be a timing issue with the
>>> creation of said locks. (I have, since the first incident, seen
>>> connections of either type occur first, so I do not believe it is just
>>> the one daemon not understanding the other's lock, but both having
>>> issues seeing each other's locks.)
>>>
>>>Has anyone else encountered this issue before or have suggestions for a
>>> resolution, or can suggest resources I might look to for a possible
>>> resolution?
>>>
>>>Thank you for your time and attention.
>>>
>>>Sincerely,
>>>Albert C.
>>>
>>>
>>>
>>>Log entries:
>>>Jul 25 08:43:46 inhouse68 in.qpopper[16187]: (v4.0.5) POP login by user
>>> "cd" at (c-24-xxx-xxx-xxx.xxxx.xx.comcast.net) 24.xxx.xxx.xxx
>>>Jul 25 08:43:54 inhouse68 imapd[16194]: imap service init from
>>> 206.xxx.xxx.xxx
>>>Jul 25 08:43:54 inhouse68 imapd[16194]: Login user=cd
>>> host=some.ip.at.blackberry.net [206.xxx.xxx.xxx]
>>>Jul 25 08:44:01 inhouse68 imapd[16194]: Logout user=cd
>>> host=some.ip.at.blackberry.net [206.xxx.xxx.xxx]
>>>Jul 25 08:44:59 inhouse68 in.qpopper[16241]: cd at
>>> c-24-xxx-xxx-xxx.xxxx.xx.comcast.net (24.xxx.xxx.xxx): -ERR [SYS/PERM]
>>> Unable to process From lines (envelopes) in
>>> /home/.sites/137/site24/.users/100/cd/mbox; change recognition mode or
>>> check for corrupted mail drop.
>>>Jul 25 08:45:40 inhouse68 in.qpopper[16372]: cd at
>>> c-24-xxx-xxx-xxx.xxxx.xx.comcast.net (24.xxx.xxx.xxx): -ERR [SYS/PERM]
>>> Unable to process From lines (envelopes) in
>>> /home/.sites/137/site24/.users/100/cd/mbox; change recognition mode or
>>> check for corrupted mail drop.
>>>Jul 25 08:51:19 inhouse68 imapd[16706]: Login user=cd
>>> host=some.ip.at.blackberry.net [206.xxx.xxx.xxx]
>>>Jul 25 08:52:13 inhouse68 imapd[16706]: Command stream end of file,
>>> while reading line user=cd host=some.ip.at.blackberry.net
>>> [206.xxx.xxx.xxx]
>>>
>>>
>>>
>>>
>>>
>>
>>
>
>
> --
> Ing. Ernesto PñÓez Estñ×ez
> http://www.ecualinux.com
> (02)3412402 - (09) 9246504
>
>


-- 
http://www.ecualinux.com