[Greylist-users] Time to resend a message

Matthias Haeker mhaeker at its-h.de
Tue Jul 5 05:41:59 PDT 2005

Hi Ken thanks for u time

> > must i resend **within** the 300sec or earlyest after
> the 300sec.
> The basic idea of greylisting is that the sending site
> should queue up 
> messages on a temporary error (the 450 error code),
> and retry 
> periodically for some amount of time, where the delay
> between tries and 
> the amount of time before the sender finally gives up
> should be 
> "reasonable".  What "reasonable" means varies, of course,
> but usually a 
> site will retry anywhere from every 15 minutes to once
> every few hours, 
> and will keep trying for at least 3-4 days, maybe a
> week.

The Problem i had was maybe the crontab default on my FreeeBSD inst.

0/30    0       *       *       *       root	sendmail -q

what i changed to 

*/10	*	*	*	*	root	sendmail -q

one our or longer will hurt the bussines

> However, for legitimate mail, this does introduce a
> delay.  (There's a 
> lot more to it, where typically you keep track of who's
> tried to send 
> mail from what addresses before, and if the sending
> mailer does retry 
> the mail, then in the future, at least for a while,
> you accept the mail 
> without delay.)

the receiving side testet his configuration and some blocked some not

but the reason for declearing it spam where that i have to use a forwarder

this results in a header like this on the receiving server.

 Return-Path: <xxx at tpm.de>
Received-SPF: none (its-h.de: domain of xxx at tpm.de does not designate permitted sender hosts)
Received: from tpm.de (tpm.de [])
	by its-h.de (8.13.4/8.13.4) with ESMTP id j619kopi080034
	for <mhaeker at its-h.de>; Fri, 1 Jul 2005 11:46:50 +0200 (CEST)
	(envelope-from khodl at tpm.de)
Received: from TPM.local (tpm.de [])
	by tpm.de (8.13.4/8.13.4) with ESMTP id j619klKj080024
	for <mhaeker at its-h.de>; Fri, 1 Jul 2005 11:46:48 +0200 (CEST)
	(envelope-from xxx at tpm.de)
To: mhaeker at its-h.de
From: xxx at tpm.de

local.client > local.smtp > tunnel >domain.smtp > world

there where different reasons to send email in this way ............


> You don't say whether the mail is actually getting through,
> in the end. 
>   But if your site and the site using greylisting are
> configured 
> reasonably normally, it should be nothing worse than
> delaying the 
> initial messages between parties (specifically, SMTP
> envelope 
> addresses) at your two sites who haven't talked before
> (at least, 
> recently).

it didnt we had to send the from the receiver requestet offer per fax

> There are some mail handling techniques that can cause
> problems when a 
> site is using greylisting, though:

there are a lot problems coused by non international rfc standard ANTISPAM systems 
to send a genuine email for international bussines purpose today

how much i have to learn more to send a simple email ????

> In the worst case, you can try to contact the postmaster
> at the site 
> you're having trouble with, and see if either they're
> doing something 
> wrong, or they think you're doing something wrong, or
> whatever else 
> might be amiss, and you can work together to fix it.

the companys i am the admin from do a incoming / outgoing 100.000 email a year to all the world 

there is not only greylisting, 

> I hope this helps....
> Ken

yes, your answer clears it little  up for me 


Matthias Haeker

mhaeker at its-h.de

More information about the Greylist-users mailing list