Yahoo Groups archive

Milter-greylist

Index last updated: 2026-04-28 23:32 UTC

Thread

Possible feature request?

Possible feature request?

2005-01-31 by Thomas Cameron

Howdy all -

I am not a developer, but I imagine this would take quite a bit of work to 
make happen.  I don't know how feasible it is.

I wonder if it would be possible to automatically whitelist someone to whome 
I sent e-mail.  In other words, if there is a recent message from me to 
jowblow@..., when a response comes in from jowblow@... 
milter-greylist would whitelist it and pass it along without delaying it.

Is this something that could be done?

Thomas

Re: [milter-greylist] Possible feature request?

2005-01-31 by Jack L. Stone

At 10:11 AM 1.31.2005 -0600, Thomas Cameron wrote:
>
>Howdy all -
>
>I am not a developer, but I imagine this would take quite a bit of work to 
>make happen.  I don't know how feasible it is.
>
>I wonder if it would be possible to automatically whitelist someone to whome 
>I sent e-mail.  In other words, if there is a recent message from me to 
>jowblow@..., when a response comes in from jowblow@... 
>milter-greylist would whitelist it and pass it along without delaying it.
>
>Is this something that could be done?
>
>Thomas 
>

I'm no code man either, but I would think that is a good idea if the IP was
somehow matched to the domain. Otherwise, we would be exposed to forgery
again.... I would think.



Happy trails,
Jack L. Stone

System Admin
Sage-american

Re: [milter-greylist] Possible feature request?

2005-01-31 by Thomas Cameron

----- Original Message ----- 
Show quoted textHide quoted text
From: "Jack L. Stone" <jacks@...>
To: <milter-greylist@yahoogroups.com>; <milter-greylist@yahoogroups.com>
Sent: Monday, January 31, 2005 10:53 AM
Subject: Re: [milter-greylist] Possible feature request?


>
> At 10:11 AM 1.31.2005 -0600, Thomas Cameron wrote:
>>
>>Howdy all -
>>
>>I am not a developer, but I imagine this would take quite a bit of work to
>>make happen.  I don't know how feasible it is.
>>
>>I wonder if it would be possible to automatically whitelist someone to 
>>whome
>>I sent e-mail.  In other words, if there is a recent message from me to
>>jowblow@..., when a response comes in from jowblow@...
>>milter-greylist would whitelist it and pass it along without delaying it.
>>
>>Is this something that could be done?
>>
>>Thomas
>>
>
> I'm no code man either, but I would think that is a good idea if the IP 
> was
> somehow matched to the domain. Otherwise, we would be exposed to forgery
> again.... I would think.
>
>
>
> Happy trails,
> Jack L. Stone

I was thinking that maybe the milter could take a quick peek in the maillog 
and see if the "In-Reply-To" header pointed to a real e-mail sent from this 
server and this sender...  That's how I (as a mere mortal) would start to 
think.

Thanks!
TC

Re: [milter-greylist] Possible feature request?

2005-01-31 by manu@netbsd.org

Jack L. Stone <jacks@...> wrote:

> I'm no code man either, but I would think that is a good idea if the IP was
> somehow matched to the domain. Otherwise, we would be exposed to forgery
> again.... I would think.

Yes, this is the problem:  

When I see an outgoing e-mail, I could decide to whitelist (recipient's
MX IP, recipient e-mail, sender e-mail), so that the reply doesn't have
to suffer greylisting.

But the recipient's MX IP does not have to be the sender IP for the
reply. I many situations, it's not the same IP. 

-- 
Emmanuel Dreyfus
http://hcpnet.free.fr/pubz
manu@...

Re: [milter-greylist] Possible feature request?

2005-02-01 by Thomas Cameron

----- Original Message ----- 
Show quoted textHide quoted text
From: <manu@...>
To: <milter-greylist@yahoogroups.com>
Sent: Monday, January 31, 2005 1:12 PM
Subject: Re: [milter-greylist] Possible feature request?


>
> Jack L. Stone <jacks@...> wrote:
>
>> I'm no code man either, but I would think that is a good idea if the IP 
>> was
>> somehow matched to the domain. Otherwise, we would be exposed to forgery
>> again.... I would think.
>
> Yes, this is the problem:
>
> When I see an outgoing e-mail, I could decide to whitelist (recipient's
> MX IP, recipient e-mail, sender e-mail), so that the reply doesn't have
> to suffer greylisting.
>
> But the recipient's MX IP does not have to be the sender IP for the
> reply. I many situations, it's not the same IP.

So would it be too dangerous to allow the e-mail address through without the 
MX ip address?  Kind of like a temporary "from user@..." entry in 
greylist.conf?

Thomas

Re: [milter-greylist] Possible feature request?

2005-02-01 by manu@netbsd.org

Thomas Cameron <thomas.cameron@...> wrote:

> So would it be too dangerous to allow the e-mail address through without the
> MX ip address?  Kind of like a temporary "from user@..." entry in
> greylist.conf?

That would make sense as an optional feature, although that would not be
easy to do. We'd have to add some wildcard IP flag in the greylist
database. It could turn into a * into the dump.

Then the trick is to detect that you see a mail with a sender listed as
a recipient that has greylisting enabled. 

Anyone is interested by contributing this?

-- 
Emmanuel Dreyfus
http://hcpnet.free.fr/pubz
manu@...

Re: [milter-greylist] Possible feature request?

2005-02-02 by Matthias Scheler

On Mon, Jan 31, 2005 at 10:11:17AM -0600, Thomas Cameron wrote:
> I wonder if it would be possible to automatically whitelist someone to whome 
> I sent e-mail.  In other words, if there is a recent message from me to 
> jowblow@..., when a response comes in from jowblow@... 
> milter-greylist would whitelist it and pass it along without delaying it.

I wonder if this is a good idea. I get lots of virus infected e-mail which
abuse the e-mail address of a friend a sender. If Milter Greylist would
have whitelisted his address because I've sent e-mail to him I would
get those viruses again.

	Kind regards

-- 
Matthias Scheler                                  http://scheler.de/~matthias/

Move to quarantaine

This moves the raw source file on disk only. The archive index is not changed automatically, so you still need to run a manual refresh afterward.