Mike Cardwell wrote:
> > Can you give an example please, because I don't get exactly how you > think this could happen... 'Could happen' ?? We've done it for *years* with a python module as a regular service for a CMS. Acts like a remote-controlled MUA, not the normal webmail client, as it uses non-local smtp, pop, imap resources. Lynx / lynx-ssl text-mode browser is another way - one you can try for yourself really easily. lynx http(s)://<your remote webmail account URI> There are others. As said, restricting *Exim* as to destinations is not hard. Preventing general misbehaviour originating on your own server that might get your IP blacklisted is a little more difficult. IPFW / IPF / iptables can help. Preventing users from sending mail entirely, or otherwise restricting them to a sub-set of destinations is a *lot* harder if you need to support a variety of services on the same box. Bill -- ## List details at http://www.exim.org/mailman/listinfo/exim-users ## Exim details at http://www.exim.org/ ## Please use the Wiki with this list - http://www.exim.org/eximwiki/
