Hello, last time I wrote (June) we resolved the config issues, and I'm happy to report that poprelayd has functioned perfectly since then.
I am in the process of setting up a mail system for my employer. The company is growing quickly and we will soon have different servers handling POP3/maildrops and SMTP, respectively.
Any suggestions on how to get poprelayd to examine the /var/log/maillog on the OTHER machine?
I presume it has something to do with configuring syslogd on one or both hosts, but that's just a wild guess. I'm a syslogd noob. Thanks!
-Cameron
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Check out the syslog documentation; you can get syslogd on the POP3 machine to send the messages to the syslogd on the SMTP server, where that syslogd can then log the messages to a file that poprelayd can read. This is probably done on your system by making the action in syslogd.conf be "@hostname".
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hello, last time I wrote (June) we resolved the config issues, and I'm happy to report that poprelayd has functioned perfectly since then.
I am in the process of setting up a mail system for my employer. The company is growing quickly and we will soon have different servers handling POP3/maildrops and SMTP, respectively.
Any suggestions on how to get poprelayd to examine the /var/log/maillog on the OTHER machine?
I presume it has something to do with configuring syslogd on one or both hosts, but that's just a wild guess. I'm a syslogd noob. Thanks!
-Cameron
Check out the syslog documentation; you can get syslogd on the POP3 machine to send the messages to the syslogd on the SMTP server, where that syslogd can then log the messages to a file that poprelayd can read. This is probably done on your system by making the action in syslogd.conf be "@hostname".