Re: ssmtp man page (Was: Re: sending email from cygwin)
On Sun, Jul 18, 2004 at 01:43:18PM +0100, Dave Korn wrote: Another possible place to mention the Cygwin-specific READMEs is in the man cygwin page. :-) Another possibility would be for the very last dialog in setup.exe, the one that says download/install complete, to also say in very big letters For Cygwin-specific documentation, see /usr/share/doc/Cygwin. It could maybe even have a tickbox to automatically open that window in explorer... I think this is a subset of something that's already in the setup.exe wishlist: http://sources.redhat.com/cgi-bin/cvsweb.cgi/setup/README?cvsroot=cygwin-appsrev=2 So, PGA, I'm sure. cgf -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: ssmtp man page (Was: Re: sending email from cygwin) gold star
On Fri, Jul 16, 2004 at 09:53:44PM -0400, Igor Pechtchanski wrote: On Fri, 16 Jul 2004, Christopher Faylor wrote: On Fri, Jul 16, 2004 at 02:25:32PM -0700, Yitzchak Scott-Thoennes wrote: I'm partial to: cygcheck -l ssmtp|fgrep README|xargs less myself. Works for other packages, too. Hey, nice use of tools. Can we get a gold star here for a clever use of utilities? This is something that I'll be using myself in the future. cgf You sure can. Just for the archives, though (not to downplay the original achievement), this will also display any other READMEs contained in the package. Intentional. If you only want the Cygwin-specific one, this incantation might be more appropriate: cygcheck -l ssmtp|grep doc/Cygwin/.*README|xargs less -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
RE: ssmtp man page (Was: Re: sending email from Cygwin)
-Original Message- From: cygwin-owner On Behalf Of Igor Pechtchanski Sent: 16 July 2004 20:12 This is a usability issue. It's hard enough to teach people to type: man command-name teaching them to type: more /usr/share/doc/Cygwin/ssmtp-0.x.y/README.ssmtp-0.x.y Don't make it overly complicated. `less /usr/share/doc/Cygwin/ssmtp*' is enough. And telling people that /usr/share/doc/Cygwin contains Cygwin specific README files isn't that hard, really. Corinna Yep, nice choice of words here. *Telling* them is definitely not hard. Getting them to do it before sending questions to the list is. :-) Actually, there's an interesting point in this thread. Would it be a good idea to have a reference to the Cygwin-specific README in the manpages for every Cygwin package that has one (say, in the SEE ALSO section)? Another possible place to mention the Cygwin-specific READMEs is in the man cygwin page. :-) Another possibility would be for the very last dialog in setup.exe, the one that says download/install complete, to also say in very big letters For Cygwin-specific documentation, see /usr/share/doc/Cygwin. It could maybe even have a tickbox to automatically open that window in explorer... cheers, DaveK -- Can't think of a witty .sigline today -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
RE: ssmtp man page (Was: Re: sending email from Cygwin)
[EMAIL PROTECTED] wrote: (= Dave K, I believe) Another possibility would be for the very last dialog in setup.exe, the one that says download/install complete, to also say in very big letters For Cygwin-specific documentation, see /usr/share/doc/Cygwin. It could maybe even have a tickbox to automatically open that window in explorer... I spell it out: THIS IS IRONIC, not personal agression; Oohh, Heaven forbid - THAT would be too easy to see! NOT in line with WJM. /Hannu E K Nevalainen, B.Sc. EE - 59+16.37'N, 17+12.60'E --72-- ** mailing list preference; please keep replies on list ** -- printf(LocalTime: UTC+%02d\n,(DST)? 2:1); -- --END OF MESSAGE-- -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
RE: ssmtp man page (Was: Re: sending email from Cygwin)
At 10:51 AM 7/18/2004, you wrote: [EMAIL PROTECTED] wrote: (= Dave K, I believe) Another possibility would be for the very last dialog in setup.exe, the one that says download/install complete, to also say in very big letters For Cygwin-specific documentation, see /usr/share/doc/Cygwin. It could maybe even have a tickbox to automatically open that window in explorer... I spell it out: THIS IS IRONIC, not personal agression; Oohh, Heaven forbid - THAT would be too easy to see! NOT in line with WJM. Good point. With this in mind, let's just remove the dialog from setup that says download/install complete. ;-) -- Larry Hall http://www.rfk.com RFK Partners, Inc. (508) 893-9779 - RFK Office 838 Washington Street (508) 893-9889 - FAX Holliston, MA 01746 -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
RE: ssmtp man page (Was: Re: sending email from Cygwin)
-Original Message- From: cygwin-owner On Behalf Of Larry Hall Sent: 18 July 2004 18:13 At 10:51 AM 7/18/2004, you wrote: [EMAIL PROTECTED] wrote: (= Dave K, I believe) Another possibility would be for the very last dialog in setup.exe, the one that says download/install complete, to also say in very big letters For Cygwin-specific documentation, see /usr/share/doc/Cygwin. It could maybe even have a tickbox to automatically open that window in explorer... I spell it out: THIS IS IRONIC, not personal agression; Oohh, Heaven forbid - THAT would be too easy to see! NOT in line with WJM. Good point. With this in mind, let's just remove the dialog from setup that says download/install complete. ;-) I've had an even better idea! Let's change the font in the package chooser to white on a white background and make everyone *guess* what they're installing! cheers, DaveK -- Can't think of a witty .sigline today -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: ssmtp man page (Was: Re: sending email from Cygwin)
On Jul 16 12:01, [EMAIL PROTECTED] wrote: On 15 Jul, Corinna Vinschen wrote: Incidentally is it appropriate to include Cygwin-port-specific information in a man page? Well, from a user perspective it might be cool, but IMHO the original man page shouldn't be changed, unless it's a change which should be send upstream anyway. We have the Cygwin specific documentation in /usr/share/doc/Cygwin (resp. /usr/doc/Cygwin in earlier releases) for a long time now. It should be not too hard to ask users to look there for Cygwin specific docs. Corinna Can you think of a way of incorporating the material in the man page that would be palatable upstream? How do you think people would feel about a section PORTABILITY or NOTES or even WINDOWS or CYGWIN? I have no idea. That's something you would have to ask the upstream maintainer. But the first question is if the Cygwin maintainer likes the idea. The above question is relevant to a patch for the ssmtp man page. If ssmtp uses ssmtp-config on most platforms it works on, then I can just write a patch that includes both fixes. ssmtp-config is a Cygwin specific script. This is a usability issue. It's hard enough to teach people to type: man command-name teaching them to type: more /usr/share/doc/Cygwin/ssmtp-0.x.y/README.ssmtp-0.x.y Don't make it overly complicated. `less /usr/share/doc/Cygwin/ssmtp*' is enough. And telling people that /usr/share/doc/Cygwin contains Cygwin specific README files isn't that hard, really. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Co-Project Leader mailto:[EMAIL PROTECTED] Red Hat, Inc. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: ssmtp man page (Was: Re: sending email from Cygwin)
On Fri, 16 Jul 2004, Corinna Vinschen wrote: On Jul 16 12:01, luke.kendallSPLATcisra.canon.com.au wrote: On 15 Jul, Corinna Vinschen wrote: Incidentally is it appropriate to include Cygwin-port-specific information in a man page? Well, from a user perspective it might be cool, but IMHO the original man page shouldn't be changed, unless it's a change which should be send upstream anyway. We have the Cygwin specific documentation in /usr/share/doc/Cygwin (resp. /usr/doc/Cygwin in earlier releases) for a long time now. It should be not too hard to ask users to look there for Cygwin specific docs. Corinna Can you think of a way of incorporating the material in the man page that would be palatable upstream? How do you think people would feel about a section PORTABILITY or NOTES or even WINDOWS or CYGWIN? I have no idea. That's something you would have to ask the upstream maintainer. But the first question is if the Cygwin maintainer likes the idea. The above question is relevant to a patch for the ssmtp man page. If ssmtp uses ssmtp-config on most platforms it works on, then I can just write a patch that includes both fixes. ssmtp-config is a Cygwin specific script. This is a usability issue. It's hard enough to teach people to type: man command-name teaching them to type: more /usr/share/doc/Cygwin/ssmtp-0.x.y/README.ssmtp-0.x.y Don't make it overly complicated. `less /usr/share/doc/Cygwin/ssmtp*' is enough. And telling people that /usr/share/doc/Cygwin contains Cygwin specific README files isn't that hard, really. Corinna Yep, nice choice of words here. *Telling* them is definitely not hard. Getting them to do it before sending questions to the list is. :-) Actually, there's an interesting point in this thread. Would it be a good idea to have a reference to the Cygwin-specific README in the manpages for every Cygwin package that has one (say, in the SEE ALSO section)? I know that most maintainers prefer the upstream manpages in their pristine state, and don't like making the Cygwin-specific patches larger, but this might actually save some bandwidth on the list. Another possible place to mention the Cygwin-specific READMEs is in the man cygwin page. :-) Perhaps this is more appropriate for cygwin-apps now... Igor -- http://cs.nyu.edu/~pechtcha/ |\ _,,,---,,_[EMAIL PROTECTED] ZZZzz /,`.-'`'-. ;-;;,_[EMAIL PROTECTED] |,4- ) )-,_. ,\ ( `'-' Igor Pechtchanski, Ph.D. '---''(_/--' `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-. Meow! I have since come to realize that being between your mentor and his route to the bathroom is a major career booster. -- Patrick Naughton -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: ssmtp man page (Was: Re: sending email from Cygwin)
On Fri, Jul 16, 2004 at 12:01:03PM +1000, luke.kendall wrote: This is a usability issue. It's hard enough to teach people to type: man command-name teaching them to type: more /usr/share/doc/Cygwin/ssmtp-0.x.y/README.ssmtp-0.x.y I'm partial to: cygcheck -l ssmtp|fgrep README|xargs less myself. Works for other packages, too. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: ssmtp man page (Was: Re: sending email from cygwin) gold star
On Fri, Jul 16, 2004 at 02:25:32PM -0700, Yitzchak Scott-Thoennes wrote: On Fri, Jul 16, 2004 at 12:01:03PM +1000, luke.kendall wrote: This is a usability issue. It's hard enough to teach people to type: man command-name teaching them to type: more /usr/share/doc/Cygwin/ssmtp-0.x.y/README.ssmtp-0.x.y I'm partial to: cygcheck -l ssmtp|fgrep README|xargs less myself. Works for other packages, too. Hey, nice use of tools. Can we get a gold star here for a clever use of utilities? This is something that I'll be using myself in the future. cgf -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: ssmtp man page (Was: Re: sending email from cygwin) gold star
On Fri, 16 Jul 2004, Christopher Faylor wrote: On Fri, Jul 16, 2004 at 02:25:32PM -0700, Yitzchak Scott-Thoennes wrote: On Fri, Jul 16, 2004 at 12:01:03PM +1000, luke.kendall wrote: This is a usability issue. It's hard enough to teach people to type: man command-name teaching them to type: more /usr/share/doc/Cygwin/ssmtp-0.x.y/README.ssmtp-0.x.y I'm partial to: cygcheck -l ssmtp|fgrep README|xargs less myself. Works for other packages, too. Hey, nice use of tools. Can we get a gold star here for a clever use of utilities? This is something that I'll be using myself in the future. cgf You sure can. Just for the archives, though (not to downplay the original achievement), this will also display any other READMEs contained in the package. If you only want the Cygwin-specific one, this incantation might be more appropriate: cygcheck -l ssmtp|grep doc/Cygwin/.*README|xargs less HTH, Igor -- http://cs.nyu.edu/~pechtcha/ |\ _,,,---,,_[EMAIL PROTECTED] ZZZzz /,`.-'`'-. ;-;;,_[EMAIL PROTECTED] |,4- ) )-,_. ,\ ( `'-' Igor Pechtchanski, Ph.D. '---''(_/--' `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-. Meow! I have since come to realize that being between your mentor and his route to the bathroom is a major career booster. -- Patrick Naughton -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: ssmtp man page (Was: Re: sending email from cygwin) gold star
On Fri, Jul 16, 2004 at 09:53:44PM -0400, Igor Pechtchanski wrote: On Fri, 16 Jul 2004, Christopher Faylor wrote: On Fri, Jul 16, 2004 at 02:25:32PM -0700, Yitzchak Scott-Thoennes wrote: On Fri, Jul 16, 2004 at 12:01:03PM +1000, luke.kendall wrote: This is a usability issue. It's hard enough to teach people to type: man command-name teaching them to type: more /usr/share/doc/Cygwin/ssmtp-0.x.y/README.ssmtp-0.x.y I'm partial to: cygcheck -l ssmtp|fgrep README|xargs less myself. Works for other packages, too. Hey, nice use of tools. Can we get a gold star here for a clever use of utilities? This is something that I'll be using myself in the future. You sure can. Just for the archives, though (not to downplay the original achievement), this will also display any other READMEs contained in the package. If you only want the Cygwin-specific one, this incantation might be more appropriate: cygcheck -l ssmtp|grep doc/Cygwin/.*README|xargs less Thanks for the clarification. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: /usr/share/doc/Cygwin (Was Re: sending email from Cygwin)
On Jul 15 10:01, you wrote: On 14 Jul, Igor Pechtchanski wrote: Yep, that would be a very good idea. In particular, it should point out that the information in the READMEs in /usr/share/doc/Cygwin takes precedence over that in the package READMEs and manpages. Maybe even an FAQ entry like I've followed directions in the README / man page / info file to the letter, and still can't get the package to work - what gives? (put in this form, it *is* rather frequently asked). :-) Can I also suggest that the FAQ's section called Where can I get more information? / Where's the documentation? would be an excellent place to mention that all the per-package readme files are collected together in /usr/share/doc/Cygwin? That would be where I'd look first to try to discover the info. Sounds good to me. Joshua, would you mind to pump up the FAQ with an entry like this? Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Co-Project Leader mailto:[EMAIL PROTECTED] Red Hat, Inc. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: sending email from Cygwin
On 14 Jul, Pierre A. Humblet wrote: At 12:02 PM 7/15/2004 +1000, [EMAIL PROTECTED] wrote: On 14 Jul, Pierre A. Humblet wrote: Thanks for the feedback. The problem is that the exim startup code thinks that you are a privileged user (see privileged 1 above). It does that by checking that you have the Create Token privilege (you have not answered my question about having given yourself unusual privileges). However you are not in the admins group (544), so you can't setuid after all. So that the main user of the machine is able to install software, they are given admin privileges. So, I have admin privileges. I can find out more details about what that precisely means by asking our Windows sysadmin people, if it would help? You don't seem to have the admin privilege, at least not in the usual sense of being in the Administrators group. You are not even a PowerUser. Strange. I am, you know. If I call up User Accounts, I see myself listed in the group Administrators, and I certainly have the ability to install and unistall software. $ id uid=11021(luke) gid=10513(Domain Users) groups=12919(adaytum),10513(Domain Users),13876(MS_VisualStudio),15155(RitaTS),13761(ZoneAlarm) Actually another explanation is that your /etc/group file is incomplete. You don't seem to be in any local group... Are the lines produced by mkgroup -l in /etc/group? If not, do mkgroup -l /etc/group and try exim -c again. Check also that uid 18 (system) is in /etc/passwd. Else do mkpasswd -l /etc/passwd You're right about the mkgroup -l: : /home/luke ; grep -i admin /etc/group Domain Admins:S-1-5-21-5706737-76180391-208020174-512:10512: Enterprise Admins:S-1-5-21-5706737-76180391-208020174-519:10519: Schema Admins:S-1-5-21-5706737-76180391-208020174-518:10518: sysadmin:S-1-5-21-5706737-76180391-208020174-3984:13984: : /home/luke ; mkgroup -l root:S-1-5-32-544:0: SYSTEM:S-1-5-18:18: None:S-1-5-21-1694720459-1161744426-439199626-513:513: Administrators:S-1-5-32-544:544: Backup Operators:S-1-5-32-551:551: Guests:S-1-5-32-546:546: Network Configuration Operators:S-1-5-32-556:556: Power Users:S-1-5-32-547:547: Remote Desktop Users:S-1-5-32-555:555: Replicator:S-1-5-32-552:552: Users:S-1-5-32-545:545: Debugger Users:S-1-5-21-1694720459-1161744426-439199626-1003:1003: HelpServicesGroup:S-1-5-21-1694720459-1161744426-439199626-1001:1001: : /home/luke ; mkgroup -l /etc/group : /home/luke ; grep -i system /etc/passwd SYSTEM:*:18:544:,S-1-5-18:: By the way, exim-config should give you warnings if those files are incomplete. Did you ever run it? No. I never saw any mention of it in the man page, nor during setup, nor when I ran exim manually, sorry. The question I was asking is whether you have the Create Token privilege. You can check that from the Users control panel, or with the editrights cygwin tool. I am on WinME, so I can't give you step by step instructions on how to do that. If I look at Control Panel - User Accounts - Advanced - Advanced User Management - Local Users and Groups, I don't appear in the list of Users there. Odd? I'm unsure if I'm looking in the right place. Does this help? : : /home/luke ; editrights -u luke -l -v editrights version 1.01: a cygwin application to edit user rights on a Windows NT system. Copyright Chris Rodgers editrights-at-bulk.rodgers.org.uk, Sep, 2003. All rights reserved. See LICENCE for further details. Listing rights for luke: Done! If your Windows sysadmin people give you that privilege, I think they should reconsider their policies. There are excellent reasons for allowing all our users for having these permissions - I can explain in more detail later, if you are unconvinced. (We are an unusual company.) luke -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: sending email from Cygwin
On 15 Jul, To: Pierre A. Humblet wrote: : /home/luke ; mkgroup -l /etc/group Incidentally, after doing that I see: : /home/luke ; exim -oi luke /tmp/smff3624 2004-07-15 17:56:06 Exim configuration file /etc/exim.conf has the wrong owner, group, or mode : /home/luke ; ls -l /etc/exim.conf -rwx--+ 1 luke Domain U22025 Aug 29 2002 /etc/exim.conf But probably I'd need to run exim-config to have a serious chance of success? luke -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: sending email from Cygwin
On Jul 15 01:39, Robert R Schneck wrote: Pierre A. Humblet wrote: Luke Kendall wrote: or that it creates a symlink to sendmail. exim doesn't. That symlink is created by the cygwin specific exim-config script under explicit user control. That avoids possible conflicts with postinstall scripts. Hmmm. So perhaps the appropriate new behavior for ssmtp is to do the same thing, asking the user whether to create such a link in the ssmtp-config. I think so. Anyone else advise otherwise? That's a good point. Yes, I guess ssmtp-config should do that, the same way as the exim-config script (perhaps you can just use Pierre's code. Would that be ok, Pierre?). I've prepared a cron package for upload with a postinstall script which doesn't create the /usr/bin/sendmail symlink anymore. I'll upload it as soon as Robert has prepared a new ssmtp package for upload. I've also added a few words to /usr/share/doc/Cygwin/cron.README about the dependency to /usr/bin/sendmail :-) Incidentally is it appropriate to include Cygwin-port-specific information in a man page? Well, from a user perspective it might be cool, but IMHO the original man page shouldn't be changed, unless it's a change which should be send upstream anyway. We have the Cygwin specific documentation in /usr/share/doc/Cygwin (resp. /usr/doc/Cygwin in earlier releases) for a long time now. It should be not too hard to ask users to look there for Cygwin specific docs. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Co-Project Leader mailto:[EMAIL PROTECTED] Red Hat, Inc. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: sending email from Cygwin
On Jul 15 17:57, [EMAIL PROTECTED] wrote: On 15 Jul, To: Pierre A. Humblet wrote: : /home/luke ; mkgroup -l /etc/group Incidentally, after doing that I see: : /home/luke ; exim -oi luke /tmp/smff3624 2004-07-15 17:56:06 Exim configuration file /etc/exim.conf has the wrong owner, group, or mode : /home/luke ; ls -l /etc/exim.conf -rwx--+ 1 luke Domain U22025 Aug 29 2002 /etc/exim.conf But probably I'd need to run exim-config to have a serious chance of success? Sounds like a good plan. Really, the Cygwin specific docs in /usr/share/doc/Cygwin are no secret ;-) Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Co-Project Leader mailto:[EMAIL PROTECTED] Red Hat, Inc. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
RE: sending email from Cygwin
Robert R Schneck wrote on Thursday, July 15, 2004 3:39 AM: Pierre A. Humblet wrote: Luke Kendall wrote: or that it creates a symlink to sendmail. exim doesn't. That symlink is created by the cygwin specific exim-config script under explicit user control. That avoids possible conflicts with postinstall scripts. Hmmm. So perhaps the appropriate new behavior for ssmtp is to do the same thing, asking the user whether to create such a link in the ssmtp-config. I think so. Anyone else advise otherwise? This is how other distos begin to deal with this problem (Gentoo already switched too): http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/mail-changingmta.html#AEN30548 -- Jörg -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: sending email from Cygwin
At 05:57 PM 7/15/2004 +1000, [EMAIL PROTECTED] wrote: On 15 Jul, To: Pierre A. Humblet wrote: : /home/luke ; mkgroup -l /etc/group Incidentally, after doing that I see: : /home/luke ; exim -oi luke /tmp/smff3624 2004-07-15 17:56:06 Exim configuration file /etc/exim.conf has the wrong owner, group, or mode : /home/luke ; ls -l /etc/exim.conf -rwx--+ 1 luke Domain U22025 Aug 29 2002 /etc/exim.conf That should have been set correctly by the postinstall script. The incomplete /etc/group prevented success. But probably I'd need to run exim-config to have a serious chance of success? It's only required if you operate a mail server, but in this case it will set the permissions correctly. The reason why you don't see the rights (previous e-mail in thread) is most likely that you get them indirectly through membership in a group. If you are curious about that, the User control panel is your best bet. Pierre -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: sending email from Cygwin
At 10:18 AM 7/15/2004 +0200, Corinna Vinschen wrote: On Jul 15 01:39, Robert R Schneck wrote: Pierre A. Humblet wrote: Luke Kendall wrote: or that it creates a symlink to sendmail. exim doesn't. That symlink is created by the cygwin specific exim-config script under explicit user control. That avoids possible conflicts with postinstall scripts. Hmmm. So perhaps the appropriate new behavior for ssmtp is to do the same thing, asking the user whether to create such a link in the ssmtp-config. I think so. Anyone else advise otherwise? That's a good point. Yes, I guess ssmtp-config should do that, the same way as the exim-config script (perhaps you can just use Pierre's code. Would that be ok, Pierre?). Sure. Let me know if you improve it. Pierre -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: /usr/share/doc/Cygwin (Was Re: sending email from Cygwin)
On Thu, 15 Jul 2004 09:47:39 +0200, Corinna Vinschen wrote: Can I also suggest that the FAQ's section called Where can I get more information? / Where's the documentation? would be an excellent place to mention that all the per-package readme files are collected together in /usr/share/doc/Cygwin? That would be where I'd look first to try to discover the info. Sounds good to me. Joshua, would you mind to pump up the FAQ with an entry like this? Yep, that needs updating. I'll get on it. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: sending email from Cygwin
On 15 Jul, Pierre A. Humblet wrote: : /home/luke ; exim -oi luke /tmp/smff3624 2004-07-15 17:56:06 Exim configuration file /etc/exim.conf has the wrong owner, group, or mode : /home/luke ; ls -l /etc/exim.conf -rwx--+ 1 luke Domain U22025 Aug 29 2002 /etc/exim.conf That should have been set correctly by the postinstall script. The incomplete /etc/group prevented success. So mkgroup -l needed to be added to /etc/group. But setup doesn't do this - which may be fair enough? But the consequence is that after exim is installed, it won't work: there's more work to do. That may be fair enough. The missing piece of information for me was that exim-config needs to be run before you can use exim. (Perhaps exim-config even checks for the mkpasswd -l step to have been done?) Anyway, I think that's basically fair enough. It would be nice if exim *itself* reported that running exim-config might be a good idea. (Is exim-config used on other platforms besides cygwin?) But probably I'd need to run exim-config to have a serious chance of success? It's only required if you operate a mail server, but in this case it will set the permissions correctly. The reason why you don't see the rights (previous e-mail in thread) is most likely that you get them indirectly through membership in a group. That's true. If you are curious about that, the User control panel is your best bet. Yep, if you look at that you can see which group (Administrators, Power Users, or Restricted Users) you're in. editrights won't tell you that, as far as I can see. Thanks for all the info and help, luke -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
ssmtp man page (Was: Re: sending email from Cygwin)
On 15 Jul, Corinna Vinschen wrote: Incidentally is it appropriate to include Cygwin-port-specific information in a man page? Well, from a user perspective it might be cool, but IMHO the original man page shouldn't be changed, unless it's a change which should be send upstream anyway. We have the Cygwin specific documentation in /usr/share/doc/Cygwin (resp. /usr/doc/Cygwin in earlier releases) for a long time now. It should be not too hard to ask users to look there for Cygwin specific docs. Corinna Can you think of a way of incorporating the material in the man page that would be palatable upstream? How do you think people would feel about a section PORTABILITY or NOTES or even WINDOWS or CYGWIN? The above question is relevant to a patch for the ssmtp man page. If ssmtp uses ssmtp-config on most platforms it works on, then I can just write a patch that includes both fixes. If not, I can just fix one thing: the mention of /usr/lib/sendmail instead of /usr/sbin/sendmail. (I'm told that the latter is the standard location to find sendmail, these days). This is a usability issue. It's hard enough to teach people to type: man command-name teaching them to type: more /usr/share/doc/Cygwin/ssmtp-0.x.y/README.ssmtp-0.x.y is even less likely. (With the consequence that users pester developers with questions, developers get irritated, users get annoyed, and the developers efforts don't get used.) luke -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: sending email from Cygwin
On Fri, Jul 16, 2004 at 11:24:01AM +1000, luke kendal at cisra.canon.com.au wrote: On 15 Jul, Pierre A. Humblet wrote: : /home/luke ; exim -oi luke /tmp/smff3624 2004-07-15 17:56:06 Exim configuration file /etc/exim.conf has the wrong owner, group, or mode : /home/luke ; ls -l /etc/exim.conf -rwx--+ 1 luke Domain U22025 Aug 29 2002 /etc/exim.conf That should have been set correctly by the postinstall script. The incomplete /etc/group prevented success. So mkgroup -l needed to be added to /etc/group. But setup doesn't do this - which may be fair enough? It does, in postinstall/passwd-grp.sh In your case it looks like somebody ran mkgroup -d and overwrote /etc/group instead of appending to it (or running mkgroup -l -d). No such mistake was made for /etc/passwd But the consequence is that after exim is installed, it won't work: there's more work to do. That may be fair enough. This list would have even more traffic in that was the case... The missing piece of information for me was that exim-config needs to be run before you can use exim. (Perhaps exim-config even checks for the mkpasswd -l step to have been done?) How can we best insure that people know about and run XXX-config? exim-config does check that the important groups/ids are present. It would have detected your problem. There is little traffic about exim on this list (well, this thread is an exception), partially because I add features to exim-config as issues arise. Anyway, I think that's basically fair enough. It would be nice if exim *itself* reported that running exim-config might be a good idea. (Is exim-config used on other platforms besides cygwin?) It's not used on other platforms, AFAIK. As you have noticed in your 2nd try, exim won't run if a few conditions are not satisfied. Verifying those is basically what exim-config does. You don't even need that to send e-mail, at least if the postinstall ran OK. But probably I'd need to run exim-config to have a serious chance of success? It's only required if you operate a mail server, but in this case it will set the permissions correctly. The reason why you don't see the rights (previous e-mail in thread) is most likely that you get them indirectly through membership in a group. That's true. If you are curious about that, the User control panel is your best bet. Yep, if you look at that you can see which group (Administrators, Power Users, or Restricted Users) you're in. editrights won't tell you that, as far as I can see. The User control panel will also show the privileges (rights) that those groups have. You could also see what groups you are in by using id, and then using editrights to find the privileges of those groups. Not sure if it can report that. Thanks for all the info and help, You are welcome. Pierre -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: sending email from Cygwin
At 12:47 AM 7/14/2004, you wrote: Larry Hall [EMAIL PROTECTED] wrote: At 10:16 PM 7/13/2004, you wrote: [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: I appear to have both exim and ssmtp installed; but I see that /usr/sbin/sendmail is a symlink to /usr/bin/ssmtp. Fair enough, if interesting. In fact, the ssmtp package does not create the sendmail symlink. As far as I can tell, no Cygwin package sets up such a symlink. Actually, I can vouch for exim setting up such a symlink. But presumably not to ssmtp. Correct. The symlink created points to exim. Also, it appears that the cron package will create a link to ssmtp if one doesn't exist, even if ssmtp is not installed. Sorry for the misinformation. Maybe the cron package readme should mention how to configure ssmtp (or maybe it does already). No, it doesn't. This does raise a question about whether the cron package should list ssmtp as a dependency though. -- Larry Hall http://www.rfk.com RFK Partners, Inc. (508) 893-9779 - RFK Office 838 Washington Street (508) 893-9889 - FAX Holliston, MA 01746 -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: sending email from Cygwin
On Jul 14 10:31, Larry Hall wrote: At 12:47 AM 7/14/2004, you wrote: Larry Hall [EMAIL PROTECTED] wrote: At 10:16 PM 7/13/2004, you wrote: [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: I appear to have both exim and ssmtp installed; but I see that /usr/sbin/sendmail is a symlink to /usr/bin/ssmtp. Fair enough, if interesting. In fact, the ssmtp package does not create the sendmail symlink. As far as I can tell, no Cygwin package sets up such a symlink. Actually, I can vouch for exim setting up such a symlink. But presumably not to ssmtp. Correct. The symlink created points to exim. Also, it appears that the cron package will create a link to ssmtp if one doesn't exist, even if ssmtp is not installed. Sorry for the misinformation. Maybe the cron package readme should mention how to configure ssmtp (or maybe it does already). No, it doesn't. This does raise a question about whether the cron package should list ssmtp as a dependency though. The cron postinstall script sets up a symlink to ssmtp if /usr/sbin/sendmail doesn't already exist. I don't think cron should contain a dependency to ssmtp though. It would be the same as to have a dependency to exim. And why should cron.README contain hints about how to set up ssmtp? That's the job for the ssmtp README, isn't it? Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Co-Project Leader mailto:[EMAIL PROTECTED] Red Hat, Inc. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: sending email from Cygwin
At 11:07 AM 7/14/2004, you wrote: On Jul 14 10:31, Larry Hall wrote: At 12:47 AM 7/14/2004, you wrote: Larry Hall [EMAIL PROTECTED] wrote: At 10:16 PM 7/13/2004, you wrote: [EMAIL PROTECTED] xxx wrote: I appear to have both exim and ssmtp installed; but I see that /usr/sbin/sendmail is a symlink to /usr/bin/ssmtp. Fair enough, if interesting. In fact, the ssmtp package does not create the sendmail symlink. As far as I can tell, no Cygwin package sets up such a symlink. Actually, I can vouch for exim setting up such a symlink. But presumably not to ssmtp. Correct. The symlink created points to exim. Also, it appears that the cron package will create a link to ssmtp if one doesn't exist, even if ssmtp is not installed. Sorry for the misinformation. Maybe the cron package readme should mention how to configure ssmtp (or maybe it does already). No, it doesn't. This does raise a question about whether the cron package should list ssmtp as a dependency though. The cron postinstall script sets up a symlink to ssmtp if /usr/sbin/sendmail doesn't already exist. I don't think cron should contain a dependency to ssmtp though. It would be the same as to have a dependency to exim. Well, I brought it up since it explicitly creates the link to ssmtp. An easier alternative would simply be to check if ssmtp already exists before creating the link, though that might not work as well in the cases where both are being installed at the same time. This isn't a big issue but it would make things more complete/correct. And why should cron.README contain hints about how to set up ssmtp? That's the job for the ssmtp README, isn't it? Agreed. At most, it could contain a pointer to the ssmtp README. Going beyond that isn't wise IMO. -- Larry Hall http://www.rfk.com RFK Partners, Inc. (508) 893-9779 - RFK Office 838 Washington Street (508) 893-9889 - FAX Holliston, MA 01746 -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: sending email from Cygwin
On Jul 14 12:45, Larry Hall wrote: At 11:07 AM 7/14/2004, you wrote: I don't think cron should contain a dependency to ssmtp though. It would be the same as to have a dependency to exim. Well, I brought it up since it explicitly creates the link to ssmtp. An easier alternative would simply be to check if ssmtp already exists before creating the link, though that might not work as well in the cases where both are being installed at the same time. This isn't a big issue but it would make things more complete/correct. Methinks that a correct approach (for a given value of correct) would be to create the symlink in an ssmtp postinstall script. That's what exim does, too. Creating the symlink in the cron postinstall script was a hack at one point. I'd be happy to get rid of it. And why should cron.README contain hints about how to set up ssmtp? That's the job for the ssmtp README, isn't it? Agreed. At most, it could contain a pointer to the ssmtp README. Going beyond that isn't wise IMO. Yeah, that's fine with me. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Co-Project Leader mailto:[EMAIL PROTECTED] Red Hat, Inc. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: sending email from Cygwin
At 01:17 PM 7/14/2004, you wrote: On Jul 14 12:45, Larry Hall wrote: At 11:07 AM 7/14/2004, you wrote: I don't think cron should contain a dependency to ssmtp though. It would be the same as to have a dependency to exim. Well, I brought it up since it explicitly creates the link to ssmtp. An easier alternative would simply be to check if ssmtp already exists before creating the link, though that might not work as well in the cases where both are being installed at the same time. This isn't a big issue but it would make things more complete/correct. Methinks that a correct approach (for a given value of correct) would be to create the symlink in an ssmtp postinstall script. That's what exim does, too. Creating the symlink in the cron postinstall script was a hack at one point. I'd be happy to get rid of it. Capital idea! Robert, can you add this to the next ssmtp release? -- Larry Hall http://www.rfk.com RFK Partners, Inc. (508) 893-9779 - RFK Office 838 Washington Street (508) 893-9889 - FAX Holliston, MA 01746 -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: sending email from Cygwin
Corinna Vinschen [EMAIL PROTECTED] wrote: I don't think cron should contain a dependency to ssmtp though. It would be the same as to have a dependency to exim. And why should cron.README contain hints about how to set up ssmtp? That's the job for the ssmtp README, isn't it? It might save people like this thread's original poster some detective work. Though granted, it's not much work to figure out where sendmail points and then which README is relevant. Perhaps the User's Guide should put a little more stress on the usefulness of /usr/share/doc/Cygwin. Robert -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
/usr/share/doc/Cygwin (Was Re: sending email from Cygwin)
On Wed, 14 Jul 2004, Robert R Schneck wrote: Corinna Vinschen [EMAIL PROTECTED] wrote: I don't think cron should contain a dependency to ssmtp though. It would be the same as to have a dependency to exim. And why should cron.README contain hints about how to set up ssmtp? That's the job for the ssmtp README, isn't it? It might save people like this thread's original poster some detective work. Though granted, it's not much work to figure out where sendmail points and then which README is relevant. Perhaps the User's Guide should put a little more stress on the usefulness of /usr/share/doc/Cygwin. Robert Yep, that would be a very good idea. In particular, it should point out that the information in the READMEs in /usr/share/doc/Cygwin takes precedence over that in the package READMEs and manpages. Maybe even an FAQ entry like I've followed directions in the README / man page / info file to the letter, and still can't get the package to work - what gives? (put in this form, it *is* rather frequently asked). :-) Igor -- http://cs.nyu.edu/~pechtcha/ |\ _,,,---,,_[EMAIL PROTECTED] ZZZzz /,`.-'`'-. ;-;;,_[EMAIL PROTECTED] |,4- ) )-,_. ,\ ( `'-' Igor Pechtchanski, Ph.D. '---''(_/--' `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-. Meow! I have since come to realize that being between your mentor and his route to the bathroom is a major career booster. -- Patrick Naughton -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: /usr/share/doc/Cygwin (Was Re: sending email from Cygwin)
On Wed, 14 Jul 2004, Igor Pechtchanski wrote: On Wed, 14 Jul 2004, Robert R Schneck wrote: Corinna Vinschen [EMAIL PROTECTED] wrote: [snip] Whoops, and a (very belated) http://cygwin.com/acronyms/#PCYMTNQREAIYR to both of us... :-) Igor -- http://cs.nyu.edu/~pechtcha/ |\ _,,,---,,_[EMAIL PROTECTED] ZZZzz /,`.-'`'-. ;-;;,_[EMAIL PROTECTED] |,4- ) )-,_. ,\ ( `'-' Igor Pechtchanski, Ph.D. '---''(_/--' `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-. Meow! I have since come to realize that being between your mentor and his route to the bathroom is a major career booster. -- Patrick Naughton -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: sending email from Cygwin
On 14 Jul, Robert R Schneck wrote: I also see that my /etc/ssmtp directory is completely empty. Someone on the list mentioned /usr/local/exim/README.Cygwin, but there is no /usr/local/exim directory on my machine. You should have read /usr/share/doc/Cygwin/ssmtp-2.60.9.README. It tells you how to create the config file. It has to be done locally. Thanks. And from looking through old email, I found afterwards that there's something called ssmtp-config (it would be a nice thing to mention in the see-also section of the ssmtp man page). Incidentally you don't need revaliases; it can be used if you want different users on your machine to send their mail via different mailhubs. Thanks, Robert. On Jul 14 12:45, Larry Hall wrote (to Corinna?): At 11:07 AM 7/14/2004, you wrote: I don't think cron should contain a dependency to ssmtp though. It would be the same as to have a dependency to exim. Well, I brought it up since it explicitly creates the link to ssmtp. An easier alternative would simply be to check if ssmtp already exists before creating the link, though that might not work as well in the cases where both are being installed at the same time. This isn't a big issue but it would make things more complete/correct. Methinks that a correct approach (for a given value of correct) would be to create the symlink in an ssmtp postinstall script. That's what exim does, too. Creating the symlink in the cron postinstall script was a hack at one point. I'd be happy to get rid of it. Sounds good. For cron to work properly, it must be able to send mail, so it has a weak dependency on *some* mail system. Tricky to describe, I imagine. I also imagine that if you choose to install all, and so get both exim and ssmtp, whichever is installed first makes the sendmail symlink. I think that's interesting, too. One day it might be nice for packages installed via setup, to interact with the user - e.g. to ask if the current package should steal existing symlinks. BTW, I'm replying separately to Pierre A. Humblet about the exim permission error. Should I submit a patch of the ssmtp man page that fixes the two problems I noticed? (/usr/lib/sendmail mentioned instead of /usr/sbin/sendmail; no See Also mention of ssmtp-config.) I also noticed that the exim man page doesn't mention that it can replace sendmail, or that it creates a symlink to sendmail. In fact, it doesn't even have a FILES section. It's auto-generated from something else, though, so fixing that sounds awkward. luke -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: /usr/share/doc/Cygwin (Was Re: sending email from Cygwin)
On 14 Jul, Igor Pechtchanski wrote: Yep, that would be a very good idea. In particular, it should point out that the information in the READMEs in /usr/share/doc/Cygwin takes precedence over that in the package READMEs and manpages. Maybe even an FAQ entry like I've followed directions in the README / man page / info file to the letter, and still can't get the package to work - what gives? (put in this form, it *is* rather frequently asked). :-) Can I also suggest that the FAQ's section called Where can I get more information? / Where's the documentation? would be an excellent place to mention that all the per-package readme files are collected together in /usr/share/doc/Cygwin? That would be where I'd look first to try to discover the info. Regards, luke -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: sending email from Cygwin
Larry Hall wrote: Corinna Vinschen wrote: Methinks that a correct approach (for a given value of correct) would be to create the symlink in an ssmtp postinstall script. That's what exim does, too. Creating the symlink in the cron postinstall script was a hack at one point. I'd be happy to get rid of it. Capital idea! Robert, can you add this to the next ssmtp release? I will do so, probably within the next week. Robert -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: sending email from Cygwin
On 14 Jul, Pierre A. Humblet wrote:
exim -oi luke /tmp/sample
I got this error:
set{u,g}id failed: 22
2004-07-14 10:48:44 unable to set gid=544 or uid=18 (euid=11021): privilege not
needed
(Which I assume means the opposite: that some privilege *is* needed.)
The first error message above is from Cygwin specific startup code that
tries to deal with the fact that there is no suid in Windows.
It's the first such error report.
What versions of Windows, Cygwin and exim are you using?
Did you give yourself unusual privileges?
Could you send the outputs of exim -c and id?
Regarding /usr/sbin/sendmail, it is set to /usr/bin/ssmtp
by the cron postinstall script (if it doesn't exist).
The exim-config script offers to set it to exim.
Pierre
$ id
uid=11021(luke) gid=10513(Domain Users) groups=12919(adaytum),10513(Domain
Users),13876(MS_VisualStudio),15155(RitaTS),13761(ZoneAlarm)
$ exim -c
CYGWIN = nobinmode. Root / mapped to C:\cygwin.
set{u,g}id failed: 22
Starting uid 11021, gid 10513, ntsec 1, privileged 1.
root_uid 11021, exim_uid 18, exim_gid 544.
setgid 10513 10513 0 pid: 3124
setuid 11021 11021 0 pid: 3124
setgid 10513 10513 0 pid: 3124
setuid 11021 11021 0 pid: 3124
setgid 544 10513 -1 pid: 3124
2004-07-15 10:02:26 unable to set gid=544 or uid=18 (euid=11021): privilege not needed
Should I attach a full cygcheck? I'm running Windows XP Professional,
sp1, on a laptop; the cygwin version was initially installed several
years ago, and I update regularly - last time a few weeks ago.
$ uname -a
CYGWIN_NT-5.1 DOYLE 1.5.10(0.116/4/2) 2004-05-25 22:07 i686 unknown unknown Cygwin
$ cygcheck -s | head -7
Cygwin Configuration Diagnostics
Current System Time: Thu Jul 15 10:11:01 2004
Windows XP Professional Ver 5.1 Build 2600 Service Pack 1
Path: c:\PROGRA~1\MICROS~3\Common\MSDev98\BIN
And the most relevant bit:
Cygwin DLL version info:
DLL version: 1.5.10
DLL epoch: 19
DLL bad signal mask: 19005
DLL old termios: 5
DLL malloc env: 28
API major: 0
API minor: 116
Shared data: 4
DLL identifier: cygwin1
Mount registry: 2
Cygnus registry name: Cygnus Solutions
Cygwin registry name: Cygwin
Program options name: Program Options
Cygwin mount registry name: mounts v2
Cygdrive flags: cygdrive flags
Cygdrive prefix: cygdrive prefix
Cygdrive default prefix:
Build date: Tue May 25 22:07:00 EDT 2004
CVS tag: cr-0x5e6
Shared id: cygwin1S4
My CYGWIN env variable is set to nobinmode.
luke
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
Re: sending email from Cygwin
At 10:14 AM 7/15/2004 +1000, [EMAIL PROTECTED] wrote:
On 14 Jul, Pierre A. Humblet wrote:
(That message was rejected by the list spam filter,
I hope this one will make it through)
exim -oi luke /tmp/sample
I got this error:
set{u,g}id failed: 22
2004-07-14 10:48:44 unable to set gid=544 or uid=18 (euid=11021):
privilege not needed
(Which I assume means the opposite: that some privilege *is* needed.)
The first error message above is from Cygwin specific startup code that
tries to deal with the fact that there is no suid in Windows.
It's the first such error report.
What versions of Windows, Cygwin and exim are you using?
Did you give yourself unusual privileges?
Could you send the outputs of exim -c and id?
snip
$ id
uid=11021(luke) gid=10513(Domain Users) groups=12919(adaytum),10513(Domain
Users),13876(MS_VisualStudio),15155(RitaTS),13761(ZoneAlarm)
$ exim -c
CYGWIN = nobinmode. Root / mapped to C:\cygwin.
set{u,g}id failed: 22
Starting uid 11021, gid 10513, ntsec 1, privileged 1.
root_uid 11021, exim_uid 18, exim_gid 544.
setgid 10513 10513 0 pid: 3124
setuid 11021 11021 0 pid: 3124
setgid 10513 10513 0 pid: 3124
setuid 11021 11021 0 pid: 3124
setgid 544 10513 -1 pid: 3124
2004-07-15 10:02:26 unable to set gid=544 or uid=18 (euid=11021):
privilege not needed
Should I attach a full cygcheck? I'm running Windows XP Professional,
sp1, on a laptop; the cygwin version was initially installed several
years ago, and I update regularly - last time a few weeks ago.
Thanks for the feedback.
The problem is that the exim startup code thinks that you are a privileged
user (see privileged 1 above). It does that by checking that you have the
Create Token privilege (you have not answered my question about having
given yourself unusual privileges).
However you are not in the admins group (544), so you can't setuid after
all.
If you don't have that privilege, there is a bug somewhere. That will require
more testing.
If you have it, I would recommend that you remove it. It opens vulnerabilities
for no good reason, AFAIK.
If there is no bug, I will modify exim to take care of your peculiar
environment.
That will be with the next official release.
$ uname -a
CYGWIN_NT-5.1 DOYLE 1.5.10(0.116/4/2) 2004-05-25 22:07 i686 unknown
unknown Cygwin
Pierre
P.S.: On normal Unix systems exim is a suid program starting as root.
When it's not necessary to be root, it setuid to a non privileged account.
That explains the privilege not needed comment in the error message.
That call fails in your case because you are not privileged enough :(
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
Re: sending email from Cygwin
On Thu, Jul 15, 2004 at 09:44:45AM +1000, [EMAIL PROTECTED] wrote: snip I also noticed that the exim man page doesn't mention that it can replace sendmail That's the standard exim man page, wrong list.. or that it creates a symlink to sendmail. exim doesn't. That symlink is created by the cygwin specific exim-config script under explicit user control. That avoids possible conflicts with postinstall scripts. Pierre -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: sending email from Cygwin
Pierre A. Humblet wrote: Luke Kendall wrote: or that it creates a symlink to sendmail. exim doesn't. That symlink is created by the cygwin specific exim-config script under explicit user control. That avoids possible conflicts with postinstall scripts. Hmmm. So perhaps the appropriate new behavior for ssmtp is to do the same thing, asking the user whether to create such a link in the ssmtp-config. I think so. Anyone else advise otherwise? Incidentally is it appropriate to include Cygwin-port-specific information in a man page? Robert -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: sending email from Cygwin
On 14 Jul, Pierre A. Humblet wrote: Thanks for the feedback. The problem is that the exim startup code thinks that you are a privileged user (see privileged 1 above). It does that by checking that you have the Create Token privilege (you have not answered my question about having given yourself unusual privileges). However you are not in the admins group (544), so you can't setuid after all. So that the main user of the machine is able to install software, they are given admin privileges. So, I have admin privileges. I can find out more details about what that precisely means by asking our Windows sysadmin people, if it would help? If you don't have that privilege, there is a bug somewhere. That will require more testing. If you have it, I would recommend that you remove it. It opens vulnerabilities for no good reason, AFAIK. If there is no bug, I will modify exim to take care of your peculiar environment. That will be with the next official release. $ uname -a CYGWIN_NT-5.1 DOYLE 1.5.10(0.116/4/2) 2004-05-25 22:07 i686 unknown unknown Cygwin Pierre P.S.: On normal Unix systems exim is a suid program starting as root. When it's not necessary to be root, it setuid to a non privileged account. That explains the privilege not needed comment in the error message. That call fails in your case because you are not privileged enough :( Ah. So it's trying to say: root privilege not needed (you have admin privileges) or something like that. luke -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: sending email from Cygwin
At 12:02 PM 7/15/2004 +1000, [EMAIL PROTECTED] wrote: On 14 Jul, Pierre A. Humblet wrote: Thanks for the feedback. The problem is that the exim startup code thinks that you are a privileged user (see privileged 1 above). It does that by checking that you have the Create Token privilege (you have not answered my question about having given yourself unusual privileges). However you are not in the admins group (544), so you can't setuid after all. So that the main user of the machine is able to install software, they are given admin privileges. So, I have admin privileges. I can find out more details about what that precisely means by asking our Windows sysadmin people, if it would help? You don't seem to have the admin privilege, at least not in the usual sense of being in the Administrators group. You are not even a PowerUser. $ id uid=11021(luke) gid=10513(Domain Users) groups=12919(adaytum),10513(Domain Users),13876(MS_VisualStudio),15155(RitaTS),13761(ZoneAlarm) Actually another explanation is that your /etc/group file is incomplete. You don't seem to be in any local group... Are the lines produced by mkgroup -l in /etc/group? If not, do mkgroup -l /etc/group and try exim -c again. Check also that uid 18 (system) is in /etc/passwd. Else do mkpasswd -l /etc/passwd By the way, exim-config should give you warnings if those files are incomplete. Did you ever run it? The question I was asking is whether you have the Create Token privilege. You can check that from the Users control panel, or with the editrights cygwin tool. I am on WinME, so I can't give you step by step instructions on how to do that. If your Windows sysadmin people give you that privilege, I think they should reconsider their policies. Pierre -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: sending email from Cygwin
[EMAIL PROTECTED] [EMAIL PROTECTED] wrote: I appear to have both exim and ssmtp installed; but I see that /usr/sbin/sendmail is a symlink to /usr/bin/ssmtp. Fair enough, if interesting. In fact, the ssmtp package does not create the sendmail symlink. As far as I can tell, no Cygwin package sets up such a symlink. I also see that my /etc/ssmtp directory is completely empty. Someone on the list mentioned /usr/local/exim/README.Cygwin, but there is no /usr/local/exim directory on my machine. You should have read /usr/share/doc/Cygwin/ssmtp-2.60.9.README. It tells you how to create the config file. It has to be done locally. Incidentally you don't need revaliases; it can be used if you want different users on your machine to send their mail via different mailhubs. Robert -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: sending email from Cygwin
At 10:16 PM 7/13/2004, you wrote: [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: I appear to have both exim and ssmtp installed; but I see that /usr/sbin/sendmail is a symlink to /usr/bin/ssmtp. Fair enough, if interesting. In fact, the ssmtp package does not create the sendmail symlink. As far as I can tell, no Cygwin package sets up such a symlink. Actually, I can vouch for exim setting up such a symlink. Also, it appears that the cron package will create a link to ssmtp if one doesn't exist, even if ssmtp is not installed. -- Larry Hall http://www.rfk.com RFK Partners, Inc. (508) 893-9779 - RFK Office 838 Washington Street (508) 893-9889 - FAX Holliston, MA 01746 -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: sending email from Cygwin
Larry Hall [EMAIL PROTECTED] wrote: At 10:16 PM 7/13/2004, you wrote: [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: I appear to have both exim and ssmtp installed; but I see that /usr/sbin/sendmail is a symlink to /usr/bin/ssmtp. Fair enough, if interesting. In fact, the ssmtp package does not create the sendmail symlink. As far as I can tell, no Cygwin package sets up such a symlink. Actually, I can vouch for exim setting up such a symlink. But presumably not to ssmtp. Also, it appears that the cron package will create a link to ssmtp if one doesn't exist, even if ssmtp is not installed. Sorry for the misinformation. Maybe the cron package readme should mention how to configure ssmtp (or maybe it does already). Robert -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
