Re: [courier-users] What config option controls -access=

2016-01-02 Thread Sam Varshavchik

Mark Constable writes:


On 01/01/16 23:39, Sam Varshavchik wrote:
>> /usr/lib/courier/sbin/imapd references $IMAPACCESSFILE
>
> Right. Looks like a packaging bug. The imapd configuration file
>  should be setting IMAPACCESSFILE.

Thanks Sam and Gordon, I'm actually helping the guy putting some 0.75
*buntu packages together, up from 0.73, and I could not find any
reference to what the -access= arg should be for IMAP. It's only when
I did a "which makeimapaccess" after Gordons message that the penny
dropped. No doubt it works the same as smtpaccess. Could be handy.


The stock imapd configuration file references IMAPACCESSFILE, and so does  
the startup script. If installed from source, everything should be working  
correctly.


The missing piece is the need to run the sysconftool script when installing  
an updated package. When this change landed, this would've correctly added  
the IMAPACCESSFILE setting into the existing config file.




pgpnF6TFRthRo.pgp
Description: PGP signature
--
___
courier-users mailing list
courier-users@lists.sourceforge.net
Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users


Re: [courier-users] What config option controls -access=

2016-01-02 Thread Gordon Messmer
On 01/01/2016 07:48 PM, Mark Constable wrote:
> I'm actually helping the guy putting some 0.75
> *buntu packages together

... while we're talking about it, why is he re-writing the init script, 
anyway?  It seems to me that most of the problems that Debian and Ubuntu 
users have with Courier are packaging bugs.  I think it'd be easier to 
help them if the package maintainer provided Courier with minimal or no 
changes, and addressed any issues that they have with the scripts 
upstream (here).

--
___
courier-users mailing list
courier-users@lists.sourceforge.net
Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users


Re: [courier-users] What config option controls -access=

2016-01-02 Thread Gordon Messmer
On 01/01/2016 07:48 PM, Mark Constable wrote:
> These new 0.75 deb packages for "wily" (15.10) are proving ornery
> because the packager has changed uid:gid from the previous "daemon"
> user that Debian has used for a decade to the more common "courier"
> user (in line with Archlinux and maybe RH/Centos). IMAP is working
> okay but I'm seeing strange behavior with esmtpd.

Yeah, switching UIDs is not to be taken lightly.  It will probably break 
working installations, and I tend to think that sort of thing drives 
users away.

If the maintainer is intent on this, you'll need to include a 
post-install script that fixes the uid and gid of everything that the 
various pieces of courier have created, including files in /etc/courier, 
/usr/lib/courier, and /var/spool/courier, or whatever layout is used on 
Debian.

And for what it's worth, the rpm packages use "daemon" unless there's a 
courier user present in the build environment.  If you use mock (and you 
should), that means that "daemon" is the standard user.

--
___
courier-users mailing list
courier-users@lists.sourceforge.net
Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users


Re: [courier-users] What config option controls -access=

2016-01-01 Thread Mark Constable
On 01/01/16 23:39, Sam Varshavchik wrote:
>> /usr/lib/courier/sbin/imapd references $IMAPACCESSFILE
>
> Right. Looks like a packaging bug. The imapd configuration file
>  should be setting IMAPACCESSFILE.

Thanks Sam and Gordon, I'm actually helping the guy putting some 0.75
*buntu packages together, up from 0.73, and I could not find any
reference to what the -access= arg should be for IMAP. It's only when
I did a "which makeimapaccess" after Gordons message that the penny
dropped. No doubt it works the same as smtpaccess. Could be handy.

These new 0.75 deb packages for "wily" (15.10) are proving ornery
because the packager has changed uid:gid from the previous "daemon"
user that Debian has used for a decade to the more common "courier"
user (in line with Archlinux and maybe RH/Centos). IMAP is working
okay but I'm seeing strange behavior with esmtpd.

I'll announce the packages here when they pass muster.

--
___
courier-users mailing list
courier-users@lists.sourceforge.net
Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users


Re: [courier-users] What config option controls -access=

2016-01-01 Thread Sam Varshavchik

Gordon Messmer writes:


On 12/31/2015 10:01 PM, Mark Constable wrote:
> My /etc/courier/imapd file has ACCESSFILE=/etc/courier/smtpaccess and yet
> these 2 daemon instance below show -access=.dat.
>
> Where do I set whatever affects the -access argument?

/usr/lib/courier/sbin/imapd references $IMAPACCESSFILE


Right. Looks like a packaging bug. The imapd configuration file should be  
setting IMAPACCESSFILE.




pgpUGRz5lqj7o.pgp
Description: PGP signature
--
___
courier-users mailing list
courier-users@lists.sourceforge.net
Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users


Re: [courier-users] What config option controls -access=

2016-01-01 Thread Gordon Messmer
On 12/31/2015 10:01 PM, Mark Constable wrote:
> My /etc/courier/imapd file has ACCESSFILE=/etc/courier/smtpaccess and yet
> these 2 daemon instance below show -access=.dat.
>
> Where do I set whatever affects the -access argument?

/usr/lib/courier/sbin/imapd references $IMAPACCESSFILE

--
___
courier-users mailing list
courier-users@lists.sourceforge.net
Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users