Hi folks, I guess I've got a toughie here...

I know, that qmail without the bind-interface patch will use the first
available ip address, and I've read the various threads about that
topic, that's why I gave my system the ip address I want qmail to use
(208.75.190.146) as the first one:

<code>
[myf...@mail /]# ifconfig
eth0      Link encap:Ethernet  HWaddr 00:17:31:27:35:2B
          inet addr:208.75.190.146  Bcast:208.75.190.151  Mask:255.255.255.248
          inet6 addr: fe80::217:31ff:fe27:352b/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:8870 errors:0 dropped:0 overruns:0 frame:0
          TX packets:9205 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:1546614 (1.4 MiB)  TX bytes:2919831 (2.7 MiB)
          Interrupt:209 Base address:0x6800

eth0:1    Link encap:Ethernet  HWaddr 00:17:31:27:35:2B
          inet addr:208.75.190.147  Bcast:208.75.190.151  Mask:255.255.255.248
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          Interrupt:209 Base address:0x6800

eth0:2    Link encap:Ethernet  HWaddr 00:17:31:27:35:2B
          inet addr:208.75.190.148  Bcast:208.75.190.151  Mask:255.255.255.248
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          Interrupt:209 Base address:0x6800

eth0:3    Link encap:Ethernet  HWaddr 00:17:31:27:35:2B
          inet addr:208.75.190.149  Bcast:208.75.190.151  Mask:255.255.255.248
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          Interrupt:209 Base address:0x6800

eth0:4    Link encap:Ethernet  HWaddr 00:17:31:27:35:2B
          inet addr:208.75.190.150  Bcast:208.75.190.151  Mask:255.255.255.248
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          Interrupt:209 Base address:0x6800

eth0:5    Link encap:Ethernet  HWaddr 00:17:31:27:35:2B
          inet addr:76.76.101.194  Bcast:76.76.101.199  Mask:255.255.255.248
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          Interrupt:209 Base address:0x6800

eth0:6    Link encap:Ethernet  HWaddr 00:17:31:27:35:2B
          inet addr:76.76.101.195  Bcast:76.76.101.199  Mask:255.255.255.248
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          Interrupt:209 Base address:0x6800

eth0:7    Link encap:Ethernet  HWaddr 00:17:31:27:35:2B
          inet addr:76.76.101.196  Bcast:76.76.101.199  Mask:255.255.255.248
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          Interrupt:209 Base address:0x6800

eth0:8    Link encap:Ethernet  HWaddr 00:17:31:27:35:2B
          inet addr:76.76.101.197  Bcast:76.76.101.199  Mask:255.255.255.248
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          Interrupt:209 Base address:0x6800

eth0:9    Link encap:Ethernet  HWaddr 00:17:31:27:35:2B
          inet addr:76.76.101.198  Bcast:76.76.101.199  Mask:255.255.255.248
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          Interrupt:209 Base address:0x6800

lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:1204 errors:0 dropped:0 overruns:0 frame:0
          TX packets:1204 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:397117 (387.8 KiB)  TX bytes:397117 (387.8 KiB)
</code>

Now here's the funny part...
When I send an email through squirrelmail and look at the headers, it looks 
like qmail actually for some reason uses the address of eth0:5 (76.76.101.194), 
which used to be the server's first emailaddress.

<code>
Return-Path: <[email protected]>
X-Flags: 0000
Delivered-To: GMX delivery to [email protected]
Received: (qmail invoked by alias); 21 Apr 2010 20:40:26 -0000
Received: from mail.protec-enterprises.com (EHLO
mail.protec-enterprises.com) [76.76.101.194] by mx0.gmx.net (mx086) with
SMTP; 21 Apr 2010 22:40:26 +0200
Received: (qmail 2766 invoked by uid 507); 21 Apr 2010 20:40:24 -0000
Comment: DomainKeys? See http://antispam.yahoo.com/domainkeys
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=private;
d=protec-enterprises.com;
b=rFj8b5x0dqpgbhIt4f5sSGjRYuc8eUMnXUSvmzcI1nCh3kx4/cU5KkZ9Bg1cCQzZ;
Received: from unknown (HELO mail.protec-enterprises.com) (127.0.0.1) by
mail.protec-enterprises.com with SMTP; 21 Apr 2010 20:40:24 -0000
Received: from 74.179.139.58 (SquirrelMail authenticated user
[email protected]) by mail.protec-enterprises.com with HTTP; Wed, 21
Apr 2010 16:40:24 -0400
Message-ID:
<be33579fe54b19515f431a4f9c678070.squir...@www.protec-enterprises.com>
Date: Wed, 21 Apr 2010 16:40:24 -0400
Subject: mal schauen, ob d was geht
From: [email protected]
To: [email protected]
User-Agent: SquirrelMail/1.4.20-1.3.17
MIME-Version: 1.0
Content-Type: text/plain;charset=iso-8859-1
Content-Transfer-Encoding: 8bit
X-Priority: 3 (Normal)
Importance: Normal
</code>


---------------------------------------------------------------------------------
Qmailtoaster is sponsored by Vickers Consulting Group 
(www.vickersconsulting.com)
    Vickers Consulting Group offers Qmailtoaster support and installations.
      If you need professional help with your setup, contact them today!
---------------------------------------------------------------------------------
     Please visit qmailtoaster.com for the latest news, updates, and packages.
     
      To unsubscribe, e-mail: [email protected]
     For additional commands, e-mail: [email protected]


Reply via email to