4 messages in net.sourceforge.lists.courier-users[courier-users] Re: SOURCE_ADDRESS fu...
FromSent OnAttachments
Johannes ErdfeltDec 5, 2003 3:47 pm 
Sam VarshavchikDec 5, 2003 4:19 pm 
Johannes ErdfeltDec 5, 2003 4:35 pm 
Mitch (WebCob)Dec 5, 2003 10:22 pm 
Actions with this message:
Paste this link in email or IM:
Paste this link in email or IM:
Atom feed for this thread
Paste this URL into your reader:
Subject:[courier-users] Re: SOURCE_ADDRESS functionalityActions...
From:Sam Varshavchik (mrs@courier-mta.com)
Date:Dec 5, 2003 4:19:41 pm
List:net.sourceforge.lists.courier-users

Johannes Erdfelt writes:

I've seen some requests for a patch similar to this in the past and has helped me.

Unfortunately, my to-be-old ISP had slow network abuse practices and ended up being placed in some blacklists. Thankfully I had another set of IP addresses assigned for the machine in a different address range which wasn't blacklisted.

I developed this patch to add a configuration option which will make courieresmtp bind() to a local IP before connecting to the remote system.

Sam, I've sent this patch in the past, but with no comments and I see

I don't remember. Maybe you did; I just don't recall.

it's still not in 0.44.2. Are you interested in this patch? Should I make some changes? Should I stop sending it?

The problem I see here is one of a slippery-slope. If you start doing this, then people will want to set a different source address based on the destination. I'd prefer do this right from the start, except that I can't think of a clean mechanism to define and implement this rule.

I'll have to think about this some more.