G
gwider
Guest
Hello All!
Since the upgrade to Pleask 8.6 Qmail is misbehaving slightly.
Qmail used to use the standard IP address eth0 to send email.
Qmail is now using a secondary IP address eth0:1 instead which is creating bad SFP problems.
server:/var/qmail/control # ifconfig (real addresses have been x-ed out)
eth0 Link encap:Ethernet HWaddr 00:E0:81:5C:67:6F
inet addr:xx.xxx.xx.xxx Bcast:xx.xxx.xx.xxx Mask:255.255.255.255
UP BROADCAST NOTRAILERS RUNNING MULTICAST MTU:1500 Metric:1
RX packets:63499060 errors:0 dropped:0 overruns:0 frame:0
TX packets:90868963 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:8881697321 (8470.2 Mb) TX bytes:110897975310 (105760.5 Mb)
Interrupt:19
eth0:1 Link encap:Ethernet HWaddr 00:E0:81:5C:67:6F
inet addr:xx.xxx.xx.xx Bcast:0.0.0.0 Mask:255.255.255.255
UP BROADCAST NOTRAILERS RUNNING MULTICAST MTU:1500 Metric:1
Interrupt:19
eth0:2 Link encap:Ethernet HWaddr 00:E0:81:5C:67:6F
inet addr:xx.xxx.xx.xxx Bcast:0.0.0.0 Mask:255.255.255.255
UP BROADCAST NOTRAILERS RUNNING MULTICAST MTU:1500 Metric:1
Interrupt:19
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:1599521 errors:0 dropped:0 overruns:0 frame:0
TX packets:1599521 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:237341994 (226.3 Mb) TX bytes:237341994 (226.3 Mb)
I did try the following approach http://forum.swsoft.com/showthread.php?t=47946&highlight=outgoingip creating an /var/qmail/control/outgoingip file, but this didn't help. I presume this will only work with an additonal Qmail patch which I'd like to avoid.
Can anybody suggest a method how to fix this problem or to convince Qmail to use the standard IP address again?
Thanks for your responses!
Since the upgrade to Pleask 8.6 Qmail is misbehaving slightly.
Qmail used to use the standard IP address eth0 to send email.
Qmail is now using a secondary IP address eth0:1 instead which is creating bad SFP problems.
server:/var/qmail/control # ifconfig (real addresses have been x-ed out)
eth0 Link encap:Ethernet HWaddr 00:E0:81:5C:67:6F
inet addr:xx.xxx.xx.xxx Bcast:xx.xxx.xx.xxx Mask:255.255.255.255
UP BROADCAST NOTRAILERS RUNNING MULTICAST MTU:1500 Metric:1
RX packets:63499060 errors:0 dropped:0 overruns:0 frame:0
TX packets:90868963 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:8881697321 (8470.2 Mb) TX bytes:110897975310 (105760.5 Mb)
Interrupt:19
eth0:1 Link encap:Ethernet HWaddr 00:E0:81:5C:67:6F
inet addr:xx.xxx.xx.xx Bcast:0.0.0.0 Mask:255.255.255.255
UP BROADCAST NOTRAILERS RUNNING MULTICAST MTU:1500 Metric:1
Interrupt:19
eth0:2 Link encap:Ethernet HWaddr 00:E0:81:5C:67:6F
inet addr:xx.xxx.xx.xxx Bcast:0.0.0.0 Mask:255.255.255.255
UP BROADCAST NOTRAILERS RUNNING MULTICAST MTU:1500 Metric:1
Interrupt:19
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:1599521 errors:0 dropped:0 overruns:0 frame:0
TX packets:1599521 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:237341994 (226.3 Mb) TX bytes:237341994 (226.3 Mb)
I did try the following approach http://forum.swsoft.com/showthread.php?t=47946&highlight=outgoingip creating an /var/qmail/control/outgoingip file, but this didn't help. I presume this will only work with an additonal Qmail patch which I'd like to avoid.
Can anybody suggest a method how to fix this problem or to convince Qmail to use the standard IP address again?
Thanks for your responses!