In our previous episode (Tuesday, 05-Mar-2013), Ashley Aitken said: > Hi Mike (et al.), > > Thank you for your very helpful post Mike. > > On 06/03/2013, at 12:31 PM, Mike Friedman <[email protected]> wrote: >> >> By default, greylisting is turned on. That's the issue you're having. This >> delays email being delivered to reduce spam. Spammers will rarely if ever >> retry a send., If it fails, they give up after one. But a properly >> configured server will try again after a given interval. >> >> This explains how to turn if off. Be careful though because it can >> accidentally get turned on. Apple's server admin doesn't respect hand edited >> configuration files very well. >> >> http://labs.hoffmanlabs.com/node/1755 > > After posting, I became aware also that I was confusing real-time > blacklisting with greylisting. I have used real-time blacklisting in the > past as well but I believe I turned it off for some reason. > > From what I read it sounds like a good thing to have greylisting - IIRC it > did reduce my spam significantly, apparently because spammers don't retry > bounced emails - so I will leave it on.
Be careful. If not setup correctly, you *will* lose legitimate mail. For example, when I set up greylisting I had to exclude amazon.com and just about every bank on the planet because either they resent mail from different servers (amazon) ior they never sent mail ever (most banks). >> To answer your questions in order. >> >> 1. Your internet domain should be one of the domains that you receive mail >> for such as : blahblah.com. > > I am sorry to be pedantic (because postfix is ;-) but do you really mean any > domain? I receive mail for a handful of domains? How will it be used? E.g. > I don't want email replying from one domain for another. Any domain that is reachable and has rDNS setup. > As I mention, I current have this as "local" which has seemed to work fine, > since I guess it is a (local) domain from which the server receives email > for. Can I leave this as that? Without knowing your network topology, it is impossible to say. >> 2. The host name is the public host name of the system (your MX record will >> tell you what this should be). mail.blahblah.com would be a common one for >> the domain in #1. > > By public host name I guess you mean FQDN? > > I have set this as the public host name of the server (which is the MX > record) mail.mydomain.com but then I seem to remember emails replying with > addresses like [email protected], which didn't look very good. > > I currently have this as "mydomain.com" and it seems to work ok (maybe). Can > I leave this as that? Sorry, again just trying to be clear. You will run into problems sending mail if your mailserver's FQDN doesn’t match the name it gives when it connects to outbound servers. If you relay via your ISP, this doesn't matter. > 1. Include server's domain as local host alias > Checked on. > > What does that actually mean? I can't parse that sentence (fragment)? > > I currently have all sorts of things in here, e.g. mail.mydomain1.com, > mydomain1.com, <public host name>, mail.mydomain2.com, mydomain2.com … These are all names that the mailserver will treat as local. > 2. Enable virtual hosting > Checked on. > > What does this actually do? In Mail setup? no idea. Does OSXS support webmail? -- NO ONE WANTS TO HEAR FROM MY ARMPITS Bart chalkboard Ep. 3F01 _______________________________________________ MacOSX-admin mailing list [email protected] http://www.omnigroup.com/mailman/listinfo/macosx-admin
