[email protected] wrote: > Hi, > I'll be asking many questions through out my > implementation phase of the ASSP, please bare with me ;-)
You're gonna wake us all from hybernation. ;-| > In my test setup, i have a sepearte box running ASSP and > created a new domain on my SMTP server (eg mydomain.com). Sorry to be anal, please try to use example.com/.net/.org domains for examples. They're especially created for that, http://www.ietf.org/rfc/rfc1034.txt mydomain.com in fact exists. > The filter setup for this domain (mydomain.com) is > Internet - > ASSP - > SMTP server -> user ... no outbound > filtering yet. Outbound filtering is less important... but not totally unnecessary. But if you have configured email submission properly, i.e. smtp authentication using encryption on port 587 (and maybe port 465 for broken clients) then you should be fine for the most part. > I cretaed the MX record for that domain to point to the > ASSP box - (mydomin.com MX 10 assp.box.com) and so > far so good in feltering inbound emails for mydomain.com. > My question is what will be the DNS setup for the PTR > reverse lookup records , should it point to my SMTP server > or the ASSP server ? It should point to the server that sends the email. Since the receiving server might check for a reverse dns and refuse delivery (happens rarely though). Since assp is a proxy as far as the receiving end is concerned the server that sends it is the smtp server. In fact it's possible you don't even use assp for outgoing but use the smtp server directly. The way I have it configured I let outgoing email route from the smtp server through assp to enable whitelisting, then it routes back to the smtp server which sends it out. > For sending outgoing mail and reading mail via POP, users > of mydomain.com will connect directly to the SMTP server, > does that mean we still have to create DNS (A) records to > point to the SMTP server and only keep the (MX) record to > point to the ASSP box ? Yes, unless you want your users to remember an IP address, which technically speaking is not a problem at all. I assume you have an entry for assp.example.com to resolve it to an IP address. It might be a good idea to have an MTA running on your assp box. ASSP then submits incoming email to that local MTA. This MTA then takes care of getting it delivered to your smtp server. The benefit of this is that if your main smtp server goes down but your asspo server is still up people sending email to you will not notice, since assp doesn't have to refuse delivery but happily submits it to the local MTA which queues it until the main smtp server is back up. This is very easy to set up. Just tell assp to route email to the localhost, whatever port, then the MTA on localhost (and just localhost, 127.0.0.1) is told to listen to that port and route all email to the main smtp server. I use port 24, which is designated for "priv-mail" so it kind of fits. Greetings, Jeroen ------------------------------------------------------------------------------ Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA -OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise -Strategies to boost innovation and cut costs with open source participation -Receive a $600 discount off the registration fee with the source code: SFAD http://p.sf.net/sfu/XcvMzF8H _______________________________________________ Assp-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/assp-user
