Eclectica Daybreak over Colburne Passage near Sidney, BC, Canada filler
shim shim shim shim
shim Home shim Software shim Avocations shim Services  
shim shim shim shim
Software
shim
shim
Documentation
 SSL Certificates
 OpenBSD RAID
 Self-Check Digits
 Bare Metal Reload
shim
Linux
 popbsmtpd
      Reference
      Installation
      Changelog
      FAQ
      Mailing Lists
      Download
shim
 Postfix
shim
 EnGarde
shim
iSeries
 CPYTOIFSF
 FTP Backup
shim
Windows
shim
shim

popbsmtpd-users

Re: Interesting phenomenom with popbsmtpd/engarde

From: Marcus Redivo (mredivo_at_<censored>)
Date: 2002-12-13 22:18:54


Hello Taylor,

I read through the code, and it turns out that it is an interpretation
problem. Here is the log entry again, with its timestamp, and the
subsequent processing:

> popbsmtpd: INPUT DATA: "Dec 13 02:03:19 puzi spop3[27632]: Login
> user=taylor host=localhost [127.0.0.1] nmsgs=1/1"
> popbsmtpd: Relaying ENABLED (extended) for user taylor at 24.xx.xx.121
> popbsmtpd: Expiry tests: Current time 2002/12/13 02:03:19 (1039762999),
> Cutoff time 2002/12/13 00:03:19 (1039755799)
>
> ^--- note that the cutoff time is EARLIER than the current time?!?

What this is telling us is "I woke up at 02:03:19 to look for expired
logins. Timeout is 120 minutes, so anybody who logged in BEFORE 00:03:19
will have their access revoked."

I read your note, and also took your interpretation of it, so at some
remove in time my decisions while writing that part look odd. The next
time I make a change to the code, I will consider how to clarify this.

In the meantime, everything is working as intended, so you should be good
to go.

Thanks for pointing this out to me, and I will send you a note when the
next version is ready. By then, I should have a mailing list set up as
well.

Cheers,
Marcus Redivo


This archive was generated by hypermail 2.1.6 on 2005-11-05 00:15:05 PST


shim