Sandy Drobic wrote:
Have a look at the subject of this thread. Many readers of this list
probably deleted the thread immediately after seeing the subject. (^-^)
Oops.
It didn't matter though, at least one person didn't, and helped root out
the source of the problem.
Regards,
Graham
--
sm
Graham Leggett wrote:
You would probably have received much more helpful answers if you had
asked about a soure ip address instead of the source port.
Looking back, I did ask about a source IP address...?
Have a look at the subject of this thread. Many readers of this list probably
deleted
Sandy Drobic wrote:
inet_interfaces = $myhostname
That parameter sets the ips for LISTENING to SMTP connections.
Correct, and according to the docs at
http://www.postfix.org/postconf.5.html, when a single IP address is
specified, that single IP address is used as the source IP address.
Graham Leggett wrote:
Hi all,
I have a machine that is both a postfix mailserver, and a NAT router for
a number of machines behind the box.
Because traffic from machines behind the box can cause the mailserver's
IP to be blacklisted, the mailserver machine has two IP addresses, one
for the
* Graham Leggett <[EMAIL PROTECTED]>:
> Hi all,
>
> I have a machine that is both a postfix mailserver, and a NAT router for
> a number of machines behind the box.
>
> Because traffic from machines behind the box can cause the mailserver's
> IP to be blacklisted, the mailserver machine has two
Aaron Wolfe wrote:
Why can your end users "access an outgoing port"? You are not
addressing this problem at it's source. Police your outbound traffic.
If its from an end user and it isn't bound for port 80 or 443, why are
you allowing the traffic to leave your network?
Because that is thr
On Wed, Aug 6, 2008 at 7:57 PM, Graham Leggett <[EMAIL PROTECTED]> wrote:
> Aaron Wolfe wrote:
>
> Blocking outbound SMTP traffic from sources other than your mail server
>> will prevent you from being blacklisted, plain and simple, unless of course
>> you are sending spam from your mail server.
Aaron Wolfe wrote:
Blocking outbound SMTP traffic from sources other than your mail server
will prevent you from being blacklisted, plain and simple, unless of
course you are sending spam from your mail server.
It's not that simple.
Blocking outbound SMTP traffic keeps you off 99% of blackl
Graham Leggett:
[ Charset ISO-8859-1 unsupported, converting... ]
> Hi all,
>
> I have a machine that is both a postfix mailserver, and a NAT router for
> a number of machines behind the box.
>
> Because traffic from machines behind the box can cause the mailserver's
> IP to be blacklisted, the
On Wed, Aug 6, 2008 at 7:12 PM, Graham Leggett <[EMAIL PROTECTED]> wrote:
> Aaron Wolfe wrote:
>
> If your network is doing things to get itself blacklisted, fix the
>> problem! Filter outbound SMTP, cleanup your network clients, whatever.
>>
>
> Been there, done that, way ahead of you.
>
> You
Aaron Wolfe wrote:
This doesn't prove Postfiix is using the wrong interface. It simply
means the traffic is seen by the upstream server as coming from the
wrong interface. It is much more likely that your NAT config is wrong
and is SNATing the mail traffic to the same address that it SNATs
Aaron Wolfe wrote:
If your network is doing things to get itself blacklisted, fix the
problem! Filter outbound SMTP, cleanup your network clients, whatever.
Been there, done that, way ahead of you.
You may not be aware of this, but while filtering outbound SMTP stops
outgoing spam, it does
On Wed, Aug 6, 2008 at 6:48 PM, Graham Leggett <[EMAIL PROTECTED]> wrote:
> Aaron Wolfe wrote:
>
> What makes you think postfix is choosing the wrong interface?
>>
>
> The Received line added by the upstream mailserver receiving the test
> messages from this box clearly shows that it received the
On Wed, Aug 6, 2008 at 6:23 PM, Graham Leggett <[EMAIL PROTECTED]> wrote:
> Graham Leggett wrote:
>
> Because traffic from machines behind the box can cause the mailserver's IP
>> to be blacklisted, the mailserver machine has two IP addresses, one for the
>> mailserver, and one for NAT.
>>
>
> Ju
Aaron Wolfe wrote:
What makes you think postfix is choosing the wrong interface?
The Received line added by the upstream mailserver receiving the test
messages from this box clearly shows that it received the email from the
second (NAT) public IP, instead of the primary public IP of the mail
On Wed, Aug 6, 2008 at 6:16 PM, Graham Leggett <[EMAIL PROTECTED]> wrote:
> Hi all,
>
> I have a machine that is both a postfix mailserver, and a NAT router for a
> number of machines behind the box.
>
> Because traffic from machines behind the box can cause the mailserver's IP
> to be blacklisted
Graham Leggett wrote:
Because traffic from machines behind the box can cause the mailserver's
IP to be blacklisted, the mailserver machine has two IP addresses, one
for the mailserver, and one for NAT.
Just to be clear - the box has two public routeable IPs on the same
interface.
The first
Hi all,
I have a machine that is both a postfix mailserver, and a NAT router for
a number of machines behind the box.
Because traffic from machines behind the box can cause the mailserver's
IP to be blacklisted, the mailserver machine has two IP addresses, one
for the mailserver, and one for
18 matches
Mail list logo
