It does appear additional work is needed to make it go out the correct interface. I only tested with IP aliases (eth0:2, eth0:3), where the default route is out eth0. To reproduce:
# ifconfig dummy0 10.10.0.1 netmask 255.255.255.255 # iptables -I OUTPUT -o dummy0 -j LOG --log-prefix "dummy0-out: " # echo test | ./src/msmtp -f test@localhost --source-host=10.10.0.1 --host=gmail.com --port=25 [email protected] You will see traffic from source 10.10.0.1 via tcpdump, but iptables will not be blocking any traffic. --G H ----- Original Message ----- From: Matus UHLAR - fantomas <[email protected]> To: [email protected] Cc: Sent: Wednesday, March 11, 2015 3:04 PM Subject: Re: [msmtp-users] PATCH: bind to source IP how will people care about outgoing interface is their business. Yes, it's not always so easy as it seems, however it's easy doable with source-routing and binding local outgoing IP is the easiest way for msmtp (and other programs) to help with that. so, while binding to source IP will not cause packets to go from different interface by itself, it's needed for it to be done. ------------------------------------------------------------------------------ Dive into the World of Parallel Programming The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net/ _______________________________________________ msmtp-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/msmtp-users
