Where are defined IPs in qmail?.

There is a patch for qmail-send that lets you bind the outgoing qmail-remote to a specific IP on the server.  www.qmail.org has a variety of patches/feature you might want to explore.
As ravenpl said, the process often binds to the primary IP on the system.

The above responses refer to QMail using a specific interface. In addition, you may want to look at the following:
http://forum.qmailrocks.org/archive/index.php/t-1753.html

However, your question could also be interpreted as a question about how QMail determines the address to send mail TO -- in which case, QMail works the same as any other MTA: it uses DNS to query for the MX server of the domain of the recipient.

Step-by-step: say you're sending a message to me (TO: dan@example.com)
 - QMail will first check to see if IT is a server for example.com (in /var/qmail/control the locals and virtualhosts files)
 - QMail will next check to see if it has a hard-coded send-to address for that domain (smtproutes)
 - QMail will lastly check DNS for the MX record of the domain (/etc/resolv.conf)

Something to keep in mind -- once a path is identified, QMail stops looking for other possible routes (e.g. if QMail thinks it is a local domain, it will never query DNS for the MX server).

I hope this fills in any holes the prior answers may have left....

Dan
IT4SOHO

How I do to know my version of qmail?

Thanks

It is likel version 1.0.3 with patches.

The IPs on which qmail listens for incoming POP adn SMTP connection is part of the run scripts if you are using tcpserver (daemontools/ucspi-tcp) /service/qmail-*/run

My scenario:

1 real NIC 1Public IP (eth0), and a Virtual Interface and a Second Public IP (eth0:1).

But, the headers always are showing, that Qmail it's sending by the first public IP.

Thanks

The sending part is qmail-send/qmail-remote and there is a patch that lets you define to which IP the qmail-remote will bind.
www.qmail.org look for qmail-remote patches.

when qmail-remote is started it binds to an available IP.
What is the issue you are trying to fix?

Hello arnold,

I'm looking for an alternative to mi first ip, that's rated as "poor" because of SPAM.

You can simply use iptables to switch all outgoing smtp to the second IP like

iptables -t nat -A POSTROUTING -p tcp -s firstIp --dport smtp -j SNAT --to-source secondaryIp

but what You really should, is cleaning IP's poor name :)

Actually it should be "-A OUTPUT" if run on the versy same host as qmail lives.

Applying the qmail-remote patch will allow you through a /var/qmail/control file to control what IP qmail-remote will use when sending outgoing messages.
If you have not address the reason your IP was rated as "poor" within a short period of time your other IP will face the same faith. I'm with ravenpl on this one.  You have a limited number of public IPs or you are behind a router/firewall and changing between private IPs on the backend has no effect on what source IP is seen when your server connects to anywhere.
Depending on how your ISP allocated IPs to you, your entire segment might be already rated "poor". I.e. if within the DNS zones for the IP segments your ISP identifies/netmasks.

Hello,

I was rated, "poor ip", because my server was compromised. A bad boy , was running dm.cgi (Dark Mailer), but this was resolved ya.

It's possible to distribute the sending of mail between the two interfaces?. By example, X domains by interface eth0 and anothers by eth0:1..

Have you gone through the steps to get your server delisted from the poor IP list?

The do what you want you would need to have two instances of qmail on your system with the qmail-remote patch.  You would then have to setup an smtproute between the two to distribute the outgoing emails based on destination domains.
Another option you might want to look at is using the example ravenpl provided for iptables and use it to randomize the outgoing IP mapping.

Yes, my server its delisted...

ravenpl;

Would this do the same result?

$Iptables -t nat -A POSTROUTING -p tcp dport 25 -j SNAT to-source new-ip