[tech] marblefish

[Grahame Bowland]

On 27/2/06 10:54 PM, "James Andrewartha" <trs80 at ucc.gu.uwa.edu.au> wrote:

> On Mon, 27 Feb 2006, David Adam wrote:
> 
>> On Mon, 27 Feb 2006, James Andrewartha wrote:
>>> Mainly because I want to reject invalid users at rcpt.to time. There will
>>> be a local SMTP server as a secondary MX that will then deliver via your
>>> method if the tunnel goes down at any point.
>> 
>> Incidentally, how are we going to do that? Mount /home/mail and run LDAP
>> over the tunnel?
> 
> I assume you mean rejecting at rcpt.to time - we're going to pipe port 25
> straight to mooneye so it can do the rejecting and mail delivering. Doing
> some rejecting on marblefish would probably be possible with some cronned
> rsync scripts to bring across aliases and the list of users.

I guess your way is better than trying to make the remote box hook into our
authentication system directly (LDAP or whatever) in that if the UCC is down
our mail won't bounce with "user unknown" errors :-)

So, the remote box will be primary MX. Remember not to put any of the
secondaries inside UWA, for fear of creating the mail loop;
  * primary is down; mail gets sent to secondary (through asclepius)
  * secondary within UWA tries to connect to primary, gets asclepius, sends
the mail
  * asclepius looks at the mail, tries to contact primary. Fails, gets the
UWA secondary, delivers the message there.
  * repeat..

I might be stating the obvious, but definitely worth mentioning out of
paranoia :-)

Of course, using antivirus.uwa.edu.au itself as a secondary should be fine.
It'll just cost for traffic!