Not sure if this is related to anything else, but I’ve found a wrinkle in the SMTP configuration that might be of interest. Over the weekend I replaced my old Linksys wireless router with an Apple Airport Extreme. After that point, the server began rejecting email we send from POP3/SMTP clients like Thunderbird based on the relay restrictions that had been in place. Even though we authenticate with the server for POP3 download before sending mail out via SMTP, the server still appears to see that the mail is coming not from the end user workstation, but from 192.168.1.1, the Airport Extreme. This appears to be a change in behavior about port forwarding, since the Linksys handled things differently.
But that’s all largely irrelevant.
What IS relevant is that modifying the SMTP restrictions to specifically add a group containing all valid mail users didn’t get the desired effect, since it appears to only check against Notes names, not SMTP addresses (joe.blow@mydomain.com). However, in the documentation, there’s an option that in that field that governs who’s permitted to send out SMTP mail to the world, you can instead specify internet email addresses rather than Notes names or groups.
DOING SO BLOWS UP SMTP!
I tried it several times in a row, and if that field contained SMTP addresses, SMTP would crash the service at startup. NSD kicks in, the whole show dies. Every time.
Remove the SMTP addresses from the restriction field, everything works fine (though we still can’t send mail out).
Anyone else seen this one?
Turtle