Why are you issuing
Code:
postal -a sender-file 172.nnn.NNN.nnn user-list-filename
at all?
Closely read the error message Postal gave you, it tells you what it needs:
Usage: postal [-m maximum-message-size] [-M minimum-message-size] [-t threads]
[-c messages-per-connection] [-r messages-per-minute] [-a]
[-b [no]netscape] [-p port] [-[z|Z] debug-file]
[-s ssl-percentage]
[-l local-address]
[-f sender-file]
smtp-server user-list-filename
So,
Code:
postal -f /path/to/sender-file ip.address.of.smtp.server /path/to/user-list
is the correct syntax.
I have to warn you though, you're spinning your wheels here. Your real problem isn't going to be raw throughput of your server, your real problem is going to be the vast majority of the internet absolutely refusing your traffic after a couple of times you send out an "e-blast". Without A LOT of specialized knowledge about bulk mail distribution, you're going to end up on every one of the private blacklists (Time Warner, AT&T, Comcast, MSN, etc) immediately, and most likely you'll end up on the public ones (SpamCop, SORBS, Spamhaus) almost as quickly. Blacklists aside, you're not going to get the kind of performance Postal would lead you to expect, because the mailservers on the other end are going to tarpit you, greylist you, and otherwise generally discourage what you're trying to do.
If you really want to have a snowball's chance in Miami of making your venture successful, forget about Postal and instead spend the time and effort in learning how to get whitelisted as a legitimate bulk mail provider with all the big carriers, and how to CLEAN CLEAN CLEAN your userlist. Otherwise you're just going to waste EVERYBODY's time, effort, and money - your clients', your own, and that of the target mailservers that don't want to talk to you.
Bookmarks