> On Sun, Apr 03, 2011 at 10:39:58PM -0700, email builder wrote: > > I'm wondering if it's possible to configure a smtpd process in > > master.cf to send messages to the outside on a secondary network > > interface. > > Of course not; smtpd(8) is the SMTP daemon, the server. It receives > mail; it does not send it. Sending is done by smtp(8), the SMTP > client.
Sorry for mucking up terminology. Indeed, I goofed that one. > > It seems to be possible to make a smtpd process listen on a given > > interface (IP address) by specifying the IP address on the front of > > the configuration line like so (where "bbb.bbb.bbb.bbb" is an IP > > address affixed to a secondary network interface): > > > > bbb.bbb.bbb.bbb:smtps inet n - n - - smtpd > > Right. > > > But when sending mail, it still seems to go out on the machine's > > primary network interface. > > Also right as per above. OVERVIEW.html might be of interest. > > > Help much appreciated. > > See postconf.5.html#smtp_bind_address for the setting which controls > smtp(8)'s selection of IP address. Google this mailing list for that, > and you will find many examples. > > See postconf.5.html#transport_maps (and transport.5.html for the > syntax thereof) for the basic means to override default selections of > outgoing mail transport. OK, thank you very much for the pointer to smtp_bind_address. That's what I need, but I'm stumbling at the transport map. I already have outgoing mail segregated how I want it when it exits my content filtering (ready to be sent out). So ideally, the content filter (actually the specialized smtpd process that accepts mail from the content filter) could hand off to a specific smtp process that has the needed smtp_bind_address. But from what I can tell, I can't control that -- the transport map seems to be the only gateway for choosing the outgoing smtp process. I'd prefer not to maintain more than one transport map, so is there *any other way* for a smtpd process to indicate which smtp process to use? I guess since transport_maps accepts more than one map, for each segregated mail group (smtpd process that accepts mail from my content filter), I can point to BOTH my normal transport map (same for everybody) AND a simple (single entry (which is a wildcard pointing to the desired smtp process)) map that is specific to each group. I'm supposing that'd work. Since the additional map will contain just a single, wildcard entry, is there any map type that is more simple/faster than a file-based table? Stepping back, is there a better way to control choice of outgoing smtp process without relying on transport_maps? > In your example, you mentioned smtps, port 465. Be aware that Postfix > has no native implementation of TLS "wrappermode" for the SMTP > client. A workaround using stunnel(1) can be found in the > TLS_README.html document.
