I think I need a better understanding of relayPort. Is relayPort a port that ASSP listens on?
> the outgoing email > sent out from the mailserver, instead, flows to the ASSP "relayport" > allowing ASSP to do auto whitelisting and to check the message, ASSP in > this case, proxies the connection to the smarthost... are you saying that, if relayPort is set to 26, then ASSP is listening on port 26 for outgoing mail from postfix, will check the messages, and then proxy them to port 26 on another IP address? Is that IP address relayHost? Please explain how relayPort works. - Jason On Sep 13, 2013, at 8:03 AM, Grayhat <[email protected]> wrote: >> >> Outgoing: mail client -> postfix(587) -> ASSP(10587) -> >> postfix(10026) -> internet > >> Incoming: Internet -> postfix(25) >> -> ASSP(10025) -> postfix(10026) -> dovecot -> mail client > > well.. it can be configured this way, but such a config will forbid you > from using some of the ASSP features (no IP checking, no > greylisting... and then some); see, the usual setup would be something > like this > > Incoming: > > internet -> ASSP -> MailServer > > OutGoing: > > MailServer -> ASSP -> SmartHost -> Internet > > basically, incoming email (from the internet) hits the frontend ASSP > listening on 25/tcp, the latter in turn, plays its magic *and* acts as > a proxy toward the mailserver which may be listening on 25 (on another > host or interface) or on whatever alternative port; the outgoing email > sent out from the mailserver, instead, flows to the ASSP "relayport" > allowing ASSP to do auto whitelisting and to check the message, ASSP in > this case, proxies the connection to the smarthost which is an SMTP > server listening on the same or on another machine, the latter picks up > the message and routes it to destination; all the above config may be > setup using a single machine (possibly with multiple interfaces and/or > IP addresses) or spread over a number of different boxes > > What I'm trying to say is that, while the kind of config you are asking > for could work (see ISPIP in ASSP), it partially defeats the whole > purpose of having ASSP on your pipeline; see... with your config, the > incoming email would be received by the frontend server (postfix) which > may (possibly) implement some filtering and reject some emails, next, > the ones skipped through would be handled over to ASSP, the latter > won't then be able to "reject" messages, since its processing will be > "off line" (and we DON'T WANT to generate bounces) this not only means > that your frontend will be quite busy accepting stuff which ASSP may > then discard, but also that an incoming email may be accepted by your > frontend and then "disappear" if ASSP flags it as "spam" and eats it... > and the sender won't even know what happened since there won't be any > SMTP session error > > > > > > > ------------------------------------------------------------------------------ > How ServiceNow helps IT people transform IT departments: > 1. Consolidate legacy IT systems to a single system of record for IT > 2. Standardize and globalize service processes across IT > 3. Implement zero-touch automation to replace manual, redundant tasks > http://pubads.g.doubleclick.net/gampad/clk?id=51271111&iu=/4140/ostg.clktrk > _______________________________________________ > Assp-user mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/assp-user ------------------------------------------------------------------------------ How ServiceNow helps IT people transform IT departments: 1. Consolidate legacy IT systems to a single system of record for IT 2. Standardize and globalize service processes across IT 3. Implement zero-touch automation to replace manual, redundant tasks http://pubads.g.doubleclick.net/gampad/clk?id=51271111&iu=/4140/ostg.clktrk _______________________________________________ Assp-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/assp-user
