Re: 110/995 syslogging: BUG found
Both of the following worked in the sense that they did not cause qpopper to complain: set log-login = "(v%0) POP login by user \"%1\" at (%2) %3" set log-login = '(v%0) SSL POP login by user "%1" at (%2) %3' However the backslashes appear in the syslog output for the first one: POP login by user \"joeblow\" at (calcite.colby.edu) 137.146.210.50 [pop_log.c:244] which is not what I want. The second one does the Right Thing. Jeff Earickson Colby College On Thu, 28 Apr 2005, Joseph S D Yao wrote: Date: Thu, 28 Apr 2005 12:26:41 -0400 From: Joseph S D Yao <[EMAIL PROTECTED]> To: Jeff A. Earickson <[EMAIL PROTECTED]> Cc: Subscribers of Qpopper Subject: Re: 110/995 syslogging: BUG found On Thu, Apr 28, 2005 at 10:18:48AM -0400, Jeff A. Earickson wrote: ... BUG: The syntax in the config files as destributed is wrong. The last line says: # set log-login= "(v%0) POP login by user /"%1/" at (%2) %3" If you uncomment this line, then qpopper will barf with the following complaint in syslog: Expected comment or end of line; found "%" at line 710 of config file /opt/maild/qpop-110.config [pop_config.c:1554] and the POP connection will fail. It looks like file globbing/quote interpretation is getting in the way. I got rid of this problem by changing the line to: set log-login= '(v%0) POP login by user "%1" at (%2) %3' ... Did you try changing the forward slashes to backslashes? I'm not saying this WILL work, but I find the forward slashes puzzling. -- Joe Yao --- This message is not an official statement of OSIS Center policies.
Re: 110/995 syslogging: BUG found
On Thu, Apr 28, 2005 at 10:18:48AM -0400, Jeff A. Earickson wrote: ... > BUG: The syntax in the config files as destributed is wrong. The > last line says: > > # set log-login= "(v%0) POP login by user /"%1/" at (%2) %3" > > If you uncomment this line, then qpopper will barf with the following > complaint in syslog: > > Expected comment or end of line; found "%" at line 710 of config file > /opt/maild/qpop-110.config [pop_config.c:1554] > > and the POP connection will fail. > > It looks like file globbing/quote interpretation is getting in the way. > I got rid of this problem by changing the line to: > > set log-login= '(v%0) POP login by user "%1" at (%2) %3' ... Did you try changing the forward slashes to backslashes? I'm not saying this WILL work, but I find the forward slashes puzzling. -- Joe Yao --- This message is not an official statement of OSIS Center policies.
110/995 syslogging: BUG found
Gang, A tip of the hat to David Champion for giving me a clue on how to implement "POP login by user..." for port 110 and "SSL POP login by user..." for port 995. The trick is to use different config files for the two entries in inetd.conf, which I was already doing: pop3 stream tcp nowait root /usr/sbin/tcpd \ /opt/maild/popper -S -f /opt/maild/qpop-110.config pop3s stream tcp nowait root /usr/sbin/tcpd \ /opt/maild/popper -S -l 2 -f /opt/maild/qpop-995.config Then for the qpop-995.config file, uncomment and modify the "set log-login" setting at the bottom of the file to do what I wanted. BUG: The syntax in the config files as destributed is wrong. The last line says: # set log-login= "(v%0) POP login by user /"%1/" at (%2) %3" If you uncomment this line, then qpopper will barf with the following complaint in syslog: Expected comment or end of line; found "%" at line 710 of config file /opt/maild/qpop-110.config [pop_config.c:1554] and the POP connection will fail. It looks like file globbing/quote interpretation is getting in the way. I got rid of this problem by changing the line to: set log-login= '(v%0) POP login by user "%1" at (%2) %3' With single quotes, this config option works just fine. Please confirm this behavior on your system. Jeff Earickson Colby College
