Re: unexpected database entry

	Message: 2
	Date: Sat, 10 Mar 2007 06:51:54 -0600
	From: "Steve Torpey @ Home" <[email protected]>
	Subject: Re: [Greylist-users] unexpected database entry
	To: "Greylisting Users and Developers Discussion"
		<[email protected]>

	It is intended.  I think the explanation in the code says it all.

	    # Here we do a special update to end the life of this record, if the
	sender is the null sender
	    #   (Spammers send from this a lot, and it should only be used for
	bounces.  This
	    #   Makes sure that only one (or a couple, small race) of these gets by
	per delay.
	    if ($mail_from eq "<>") {
	      # Only update the lifetime of records if they are AUTO, wouldn't want
	to do wildcard records
	      my $rows = $dbh->do("UPDATE relaytofrom SET record_expires = NOW() "
	        . " WHERE id = $rowid AND origin_type = 'AUTO'") or goto DB_FAILURE;
	      print "  Mail is from null-sender.  Updated it to end its life.\n" if
	($verbose and $rows > 0);
	    }

Ok, good explanation.  Thanks. 



	----- Original Message ----- 
	From: "Philip Goisman" <[email protected]>
	To: <[email protected]>
	Sent: Friday, March 09, 2007 5:06 PM
	Subject: [Greylist-users] unexpected database entry


	> Hi,
	>
	> New user here.
	>
	> So far I've been very happy with relaydelay.  It works as
	> advertised in the whitepaper.
	>
	> Today, a user sent me two examples of where his address had been
	> forged - nothing unusual there.  The unexpected part is what happened
	> in the database as follows:
	>
	> --------+--------------+---------------+-------------+--------------------
	-+---------------------+
	> | 2175569 | 193.24.33.93 | <>        | <[email protected]> |
	2007-03-09 11:46:25 | 2007-03-09 11:53:20 |             2 |            1 |
	0 | AUTO        | 2007-03-09 10:48:25 | 2007-03-09 11:53:21 |
	>
	+---------+--------------+-----------+-------------------------------+------
	---------------+---------------------+---------------+--------------+-------
	--------+-------------+---------------------+---------------------+
	>
	> --------+--------------+---------------+-------------+--------------------
	-+---------------------+
	> | 2175549 | 160.45.24.23 | <>        | <[email protected]> |
	2007-03-09 11:44:18 | 2007-03-09 11:54:19 |             2 |            1 |
	0 | AUTO        | 2007-03-09 10:46:18 | 2007-03-09 11:54:19 |
	>
	+---------+--------------+-----------+-------------------------------+------
	---------------+---------------------+---------------+--------------+-------
	--------+-------------+---------------------+---------------------+
	>
	> In both cases above the record was blocked for the one hour period.  After
	that
	> it was passed, to a_user.  However, the "record_expires" did not get
	updated.
	>
	> Below is a recent response which did get updated:
	>
	> -----------+---------------------+---------------+--------------+---------
	------+-------------+---------------------+---------------------+
	> | 2153832 | 209.189.198.108 | <[email protected]>
	| <[email protected]> | 2007-03-07 10:11:55 | 2007-04-12 11:10:40
	|             6 |            2 |             0 | AUTO        | 2007-03-07
	09:13:55 | 2007-03-07 11:10:40 |
	> | 2153618 | 209.189.198.108 |
	<[email protected]> |
	<[email protected]> | 2007-03-07 09:48:45 | 2007-04-12 11:10:57 |
	5 |            2 |             0 | AUTO        | 2007-03-07 08:50:45 |
	2007-03-07 11:10:57 |
	>
	+---------+-----------------+-----------------------------------------------
	--+-------------------------------+---------------------+-------------------
	--+---------------+--------------+---------------+-------------+------------
	---------+---------------------+
	>
	> Is the unexpected database entry something I need to worry about or fix?
	>
	> Using relaydelay-0.04 with patch.
	>
	> Regards,
	>
	> Philip
	> _______________________________________________
	> Greylist-users mailing list
	> [email protected]
	> http://lists.puremagic.com/cgi-bin/mailman/listinfo/greylist-users