|
Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com |
From: Edgar DÃaz Orellana (eorellan
fulltimehosting.net)
Date: Sun Jul 01 2007 - 19:26:46 CDT
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Hi again.
This is an example of connection tracking in my mta Server.
Jul 1 20:21:13: ACCEPT smtp firewall(eth0_222) -> 65.54.244.200 'via_NET_220' (out: eth0 200.27.132.222:46065 -> 65.54.244.200:25 TCP flags: ****S* len:60 ttl:64) │
│Jul 1 20:21:14: ACCEPT smtp firewall(eth0_222) -> 65.54.244.104 'via_NET_219' (out: eth0 200.27.132.222:44428 -> 65.54.244.104:25 TCP flags: ****S* len:60 ttl:64) │
│Jul 1 20:21:15: ACCEPT smtp firewall(eth0_222) -> 209.85.199.27 'via_NET_219' (out: eth0 200.27.132.222:38101 -> 209.85.199.27:25 TCP flags: ****S* len:60 ttl:64) │
│Jul 1 20:21:16: ACCEPT smtp firewall(eth0_222) -> 65.54.244.168 'via_NET_220' (out: eth0 200.27.132.222:34979 -> 65.54.244.168:25 TCP flags: ****S* len:60 ttl:64) │
│Jul 1 20:21:17: ACCEPT smtp firewall(eth0_222) -> 65.54.244.72 'via_NET_219' (out: eth0 200.27.132.222:46726 -> 65.54.244.72:25 TCP flags: ****S* len:60 ttl:64) │
│Jul 1 20:21:18: ACCEPT smtp firewall(eth0_222) -> 65.54.244.232 'via_NET_220' (out: eth0 200.27.132.222:51861 -> 65.54.244.232:25 TCP flags: ****S* len:60 ttl:64) │
│Jul 1 20:21:19: ACCEPT smtp firewall(eth0_222) -> 65.54.244.104 'via_NET_219' (out: eth0 200.27.132.222:44438 -> 65.54.244.104:25 TCP flags: ****S* len:60 ttl:64) │
│Jul 1 20:21:20: ACCEPT smtp firewall(eth0_222) -> 65.54.245.72 'via_NET_219' (out: eth0 200.27.132.222:57015 -> 65.54.245.72:25 TCP flags: ****S* len:60 ttl:64) │
│Jul 1 20:21:22: ACCEPT smtp firewall(eth0_222) -> 65.54.244.168 'via_NET_219' (out: eth0 200.27.132.222:34987 -> 65.54.244.168:25 TCP flags: ****S* len:60 ttl:64) │
│Jul 1 20:21:23: ACCEPT smtp firewall(eth0_222) -> 209.85.199.114 'via_NET_219' (out: eth0 200.27.132.222:47934 -> 209.85.199.114:25 TCP flags: ****S* len:60 ttl:64) │
│Jul 1 20:21:23: ACCEPT smtp firewall(eth0_222) -> 65.54.244.72 'via_NET_220' (out: eth0 200.27.132.222:46734 -> 65.54.244.72:25 TCP flags: ****S* len:60 ttl:64) │
│Jul 1 20:21:24: ACCEPT smtp firewall(eth0_222) -> 209.85.199.114 'via_NET_219' (out: eth0 200.27.132.222:47936 -> 209.85.199.114:25 TCP flags: ****S* len:60 ttl:64) │
│Jul 1 20:21:25: ACCEPT smtp firewall(eth0_222) -> 65.54.245.104 'via_NET_220' (out: eth0 200.27.132.222:34181 -> 65.54.245.104:25 TCP flags: ****S* len:60 ttl:64) │
│Jul 1 20:21:26: ACCEPT smtp firewall(eth0_222) -> 209.191.118.103 'via_NET_219' (out: eth0 200.27.132.222:46156 -> 209.191.118.103:25 TCP flags: ****S* len:60 ttl:64) │
│Jul 1 20:21:27: ACCEPT smtp firewall(eth0_222) -> 209.191.88.239 'via_NET_219' (out: eth0 200.27.132.222:35107 -> 209.191.88.239:25 TCP flags: ****S* len:60 ttl:64) │
│Jul 1 20:21:30: ACCEPT smtp firewall(eth0_222) -> 192.118.82.244 'via_NET_219' (out: eth0 200.27.132.222:39068 -> 192.118.82.244:25 TCP flags: ****S* len:60 ttl:64) │
│Jul 1 20:21:33: ACCEPT smtp firewall(eth0_222) -> 192.118.82.244 'via_NET_219' (out: eth0 200.27.132.222:39068 -> 192.118.82.244:25 TCP flags: ****S* len:60 ttl:64) │
│Jul 1 20:21:39: ACCEPT smtp firewall(eth0_222) -> 192.118.82.244 'via_NET_219' (out: eth0 200.27.132.222:39068 -> 192.118.82.244:25 TCP flags: ****S* len:60 ttl:64) │
│Jul 1 20:21:51: ACCEPT smtp firewall(eth0_222) -> 192.118.82.244 'via_NET_219' (out: eth0 200.27.132.222:39068 -> 192.118.82.244:25 TCP flags: ****S* len:60 ttl:64) │
│Jul 1 20:22:00: ACCEPT smtp firewall(eth0_222) -> 192.118.82.144 'via_NET_219' (out: eth0 200.27.132.222:56230 -> 192.118.82.144:25 TCP flags: ****S* len:60 ttl:64) │
│Jul 1 20:23:16: ACCEPT smtp firewall(eth0_222) -> 209.85.199.27 'via_NET_219' (out: eth0 200.27.132.222:38161 -> 209.85.199.27:25 TCP flags: ****S* len:60 ttl:64) │
If you see the outgoing ip address always is the same 200.27.132.222
Some other clue ?
Thanks
-----Mensaje original-----
De: owner-postfix-userspostfix.org [mailto:owner-postfix-userspostfix.org] En nombre de Edgar DÃaz Orellana
Enviado el: Domingo, 01 de Julio de 2007 19:06
Para: postfix-userspostfix.org
Asunto: RE: RV: Problem to Load-Balance Outgoing SMTP traffic with postfix.
I'm trying to do that, but nothing's change always the outgoing ip is the
200.27.132.222, and nothing i can do to change that.
Some clue?
edgar
-----Mensaje original-----
De: owner-postfix-userspostfix.org [mailto:owner-postfix-userspostfix.org]
En nombre de mouss
Enviado el: Domingo, 01 de Julio de 2007 18:58
CC: postfix-userspostfix.org
Asunto: Re: RV: Problem to Load-Balance Outgoing SMTP traffic with postfix.
Edgar DÃaz Orellana wrote:
> Hi everyone.
>
> I have some sites hosted in this Server some of them have 2000 email
> accounts, then i try to make some load balance for outgoing email traffic
> because all the time, because the amount of email accounts i have in this
> Server, some mayor email hosting providers like Hotmail, gmail, yahoo and
> others, think i'm a spammer, then i think the best way to change this
> situation, is make a load balance on the outgoing email traffic, the thing
> is all outgoing traffic still goes by the eth0:222 and no balance is
doing,
> and I really need the balance.
>
> Some of yours have some clue or idea to make postfix use all of the public
> ip addresses to send the outgoing mail.
>
> BTW, if need more info or other config files, please ask.
>
IP routing to remote server is done by the kernel, and it is generally
based on destination IP. your kernel or IP filter may have functionality
to allow you you to use different IPs/interfaces.
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]