KLaM Postmaster пишет:
Artem Bokhan:
Hi, can someone give me a hint how to randomly spread outgoing smtp
traffic over pool of ip-addresses
==
Why do you want to do this?
What problem are you trying to solve?
JLA
The main reason that some systems have too high limits, so legitimate mail i
On Thu, 2009-02-19 at 14:35 -0500, Victor Duchovni wrote:
> On Thu, Feb 19, 2009 at 02:20:39PM -0500, Wietse Venema wrote:
>
> > /etc/postfix/main.cf
> > check_recipient_access pcre:/etc/postfix/random.pcre
> >
> > /etc/postfix/random.pcre
> > /^(.)(.*)/ FILTER smtp$1:$1$2
>
> Rege
2009/2/19 Bokhan Artem :
>>> smtp1 unix - - n - 100 smtp -o
>>> smtp_helo_name=smtpout1.do -o smtp_bind_address=1.1.1.1
>>> smtp2 unix - - n - 100 smtp -o
>>> smtp_helo_name=smtpout2.do -o smtp_bind_address=2.2.2.2
>>>
>>>
>
>
Artem Bokhan:
Hi, can someone give me a hint how to randomly spread outgoing smtp
traffic over pool of ip-addresses
==
Why do you want to do this?
What problem are you trying to solve?
JLA
Peter Blair пишет:
True enough-- but that won't help your HELO matching up with the
reverse of the IP that its bound to.
2009/2/19 Bokhan Artem :
Peter Blair пишет:
Well, you could place a slim smtp proxy between postfix and the
Internet.
It's easier to write a small tcp server for tcp_table
True enough-- but that won't help your HELO matching up with the
reverse of the IP that its bound to.
2009/2/19 Bokhan Artem :
> Peter Blair пишет:
>>
>> Well, you could place a slim smtp proxy between postfix and the
>> Internet.
>
> It's easier to write a small tcp server for tcp_table which wil
Peter Blair пишет:
Well, you could place a slim smtp proxy between postfix and the
Internet.
It's easier to write a small tcp server for tcp_table which will randomize
transport :)
smtp1 unix - - n - 100 smtp -o
smtp_helo_name=smtpout1.do -o smtp_bind_a
Wietse Venema пишет:
Bokhan Artem:
Now you are probably going to tell me that you actually have a
different problem again.
Yes :) The same message (or rcpt) will be always sent from the same address :)
Anyway, thanks, Wietse.
Wietse
On Thu, Feb 19, 2009 at 3:15 PM, Bokhan Artem wrote:
> Peter Blair пишет:
>>
>> It's easier to do with a src-nat within network gear.
>
> I understand, I just wanted to know if there is an intelligence way to bind
> every ip address its own helo.
Well, you could place a slim smtp proxy between po
Peter Blair пишет:
It's easier to do with a src-nat within network gear.
I understand, I just wanted to know if there is an intelligence way to bind
every ip address its own helo.
But let me tell
you that this is referred to as "snowshoeing" as it expands your IP
footprint, and is seen in t
It's easier to do with a src-nat within network gear. But let me tell
you that this is referred to as "snowshoeing" as it expands your IP
footprint, and is seen in the deliverability world as a slimy thing to
do.
People do it to mitigate the effects of their IP addresses being
blacklisted. But t
On Thu, Feb 19, 2009 at 02:20:39PM -0500, Wietse Venema wrote:
> /etc/postfix/main.cf
> check_recipient_access pcre:/etc/postfix/random.pcre
>
> /etc/postfix/random.pcre
> /^(.)(.*)/FILTER smtp$1:$1$2
Regexp recipient lookups are keyed by the full user address, and the
character-
Bokhan Artem:
> Wietse Venema ?:
> > Bokhan Artem:
> >> Wietse Venema ?:
> >>> Artem Bokhan:
> Hi, can someone give me a hint how to randomly spread outgoing smtp
> traffic over pool of ip-addresses?
> >>> Use network address translation, to map the source IP
> >>> address+port
Wietse Venema пишет:
Bokhan Artem:
Wietse Venema ?:
Artem Bokhan:
Hi, can someone give me a hint how to randomly spread outgoing smtp
traffic over pool of ip-addresses?
Use network address translation, to map the source IP
address+port across a range of IP addresses.
Bokhan Artem:
I wa
Bokhan Artem:
> Wietse Venema ?:
> > Artem Bokhan:
> >> Hi, can someone give me a hint how to randomly spread outgoing smtp
> >> traffic over pool of ip-addresses?
> >
> > Use network address translation, to map the source IP
> > address+port across a range of IP addresses.
Bokhan Artem:
>
Joseph Mays пишет:
I want to have different helo's also, replacing helo with firewall is
not very good idea...
We do this with a foundry switch. The ip for smtp.win.net is actually on
the foundry switch, and the switch forwards connections to a cluster of
machines on the back end.
Looks l
I want to have different helo's also, replacing helo with firewall is not
very good idea...
We do this with a foundry switch. The ip for smtp.win.net is actually on the
foundry switch, and the switch forwards connections to a cluster of machines
on the back end.
Wietse Venema пишет:
Artem Bokhan:
Hi, can someone give me a hint how to randomly spread outgoing smtp
traffic over pool of ip-addresses?
Use network address translation, to map the source IP
address+port across a range of IP addresses.
Wietse
I want to have different helo's also,
Artem Bokhan:
> Hi, can someone give me a hint how to randomly spread outgoing smtp
> traffic over pool of ip-addresses?
Use network address translation, to map the source IP
address+port across a range of IP addresses.
Wietse
Hi, can someone give me a hint how to randomly spread outgoing smtp
traffic over pool of ip-addresses?
As I understand it's necessary to create several transports and use
transport tables, but I do not see a way how to make lookups truly random.
smtp1 unix - - n -
20 matches
Mail list logo
