On Jan 18, 2011 5:20 PM, "Ski Kacoroski" <kacoro...@gmail.com> wrote:
>
> My problem is that I have a very badly written application that (1) have
> broken authentication and (2) basically require an open relay to send as
> they make the To and From addresses the same. I really do not want to
> open up port 25 to all internal users as a relay ( I have it open now to
> just a few server networks for some black boxes I am stuck with). I
> would like to set up another port (e.g. 2525) and have it work as a open
> relay for all my internal addresses as this will be harder for the
> kiddies to find and exploit. Is there anyway to have port 25 open and
> locked down by the mynetworks parameter, but have another port open and
> not locked down by the my networks parameter?
You can; what hasn't been mentioned so far is that you can also have the
smtpd_{sender,recipient}_restrictions list treat, for example, the one
specific source IP as an "allow" for traffic on port 25.
Just inject the appropriate permit into that, or even add the host IP to
"mynetworks" to have that automatically trust it outbound.
Regards,
Daniel
--
Puppet Labs Developer – http://puppetlabs.com
Daniel Pittman <dan...@rimspace.net>
Contact me via gtalk, email, or phone: +1 (503) 893-2285
Sent from a mobile device; please forgive brevity and typos.
_______________________________________________
Tech mailing list
Tech@lists.lopsa.org
https://lists.lopsa.org/cgi-bin/mailman/listinfo/tech
This list provided by the League of Professional System Administrators
http://lopsa.org/
