Le 28/03/2011 22:07, John a écrit :
> On 3/28/2011 8:59 AM, Lima Union wrote:
>> Hi, while looking in the change log for some info about an issue I'm
>> having[1] I found a simple typo in the date specified as shown here:
>>
>> 20200102
>>
>> Workaround: don't report bogus Berkeley DB close err
On Mon, Mar 28, 2011 at 2:43 PM, Jeroen Geilman wrote:
> On 03/28/2011 02:59 PM, Lima Union wrote:
>>
>> [1] postfix/verify[3209]: close database
>> /var/lib/postfix/verify_cache.db: No such file or directory
>>
>
> Are you USING sender or recipient verification ?
>
> If so, does the verify daemon
On 3/28/2011 8:59 AM, Lima Union wrote:
Hi, while looking in the change log for some info about an issue I'm
having[1] I found a simple typo in the date specified as shown here:
20200102
Workaround: don't report bogus Berkeley DB close errors as
fatal errors. All operations befo
Jeroen Geilman:
> On 03/28/2011 02:59 PM, Lima Union wrote:
> > [1] postfix/verify[3209]: close database
> > /var/lib/postfix/verify_cache.db: No such file or directory
>
> Are you USING sender or recipient verification ?
The same bogus error may be reported with the tlsmgr(8) session
cache and w
On 03/28/2011 02:59 PM, Lima Union wrote:
[1] postfix/verify[3209]: close database
/var/lib/postfix/verify_cache.db: No such file or directory
Are you USING sender or recipient verification ?
If so, does the verify daemon run chrooted ?
--
J.
Hi, while looking in the change log for some info about an issue I'm
having[1] I found a simple typo in the date specified as shown here:
20200102
Workaround: don't report bogus Berkeley DB close errors as
fatal errors. All operations before close are already error
checked
