Derrick T. Woolworth wrote:
Unfortunately, I'm not that familiar with MS Exchange server. I'm just wondering if it works more like Sendmail where the domain name is irrelevant to the username - so an e-mail sent to the alias [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> will actually be deposited into the [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> account - or if domain must match?
I'm not familiar with it, either. Bowie suggested that you may need to add another address to each of the Exchange users. If that's so, only the Courier host would use those addresses, neither local users nor remote senders should ever see them.
The reason we use Courier as an e-mail gateway is due to the filters that work much better than anything Exchange has to offer - which, again, I don't know Exchange so that might not be correct. Either way, its a nice scenario where the users that want to take advantage of Courier's filtering capabilities create valid accounts on the Courier box. The folks that don't want their e-mail filtered don't need accounts because Courier automatically routes e-mail to the Exchange box, untouched. This is why I'm suggesting one small filter that checks to see if an account is valid - and the ldap idea sounds like a really good one.
I don't think that any of Courier's filtering capabilities are going to fix the problem though. The courierfilter stuff happens after the DATA phase, so it can't reject individual users, and the localmailfilter stuff only works if the users are valid local accounts. You might be able to hook in with the alias-filteracct setting, but it's hard to say without knowing more about *how* Courier's been configured to route mail.
In any case, an alias database which redirects only valid accounts is probably the least amount of work, and the most reliable of solutions.
What I currently have works "ok" - but maillogs roll and the logic to prevent reparsing large logs seems a bit daunting as well.
Keep it simple: only parse what you read while watching the end of the file for appended data. Make sure that whatever rotates your logs (logrotate?) notifies your parser when it rolls logs. It should be a simple matter of adding a "kill -HUP <pid>" to the logrotate postrotate script for the maillog file.
Forcing syslogd to pipe its output to a program that reads stdin and processes the logs and writes to the same /var/log/maillog seems a lot easier -
It won't be. If your application fails for any reason, you're going to lose logs entirely. In order for log rotation to work reliably, you're still going to have to modify your logrotate configuration, and you're still going to have to make sure that your program handles HUP signals properly.
but then that's just my opinion - but this way I'm sure not to miss anything and surely its more real-time.
There's no reason for that to be true.
Thanks for the response, for sure...
No problem. Good luck! ------------------------------------------------------- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642 _______________________________________________ courier-users mailing list [email protected] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
