Processed: Re: Bug#435909: Kcheckgmail language bug
Processing commands for [EMAIL PROTECTED]: reassign 435909 kdelibs 4:3.5.7.dfsg.1-1 Bug#435909: kcheckgmail is not in correct language. Bug reassigned from package `kcheckgmail' to `kdelibs'. thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: Re: Bug#435760: kcheckgmail bug: always request certificate
Processing commands for [EMAIL PROTECTED]: tag 435760 -upstream Bug#435760: kcheckgmail request a Google certificate everyday. Tags were: upstream Tags removed: upstream reassign 435760 kdelibs 4:3.5.7.dfsg.1-1 Bug#435760: kcheckgmail request a Google certificate everyday. Bug reassigned from package `kcheckgmail' to `kdelibs'. thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
New PAM in experimental needs testing
Hi folks, A new version of PAM (0.99.7.1-1) has been packaged and uploaded to experimental. This is intended to replace 0.79-4. However, because there have been quite a number of upstream changes, and all the Debian-specific patches against the old one were painstakingly re-diffed and updated by hand, and because a broken PAM means a rather broken system, this new version needs some wider testing before it is suitable for unstable. The work for this was done by myself and Jan Christoph Nordholz, who rewrote the @include patch, fixing a memory leak in the current code, as well as doing a lot of testing, building and general reviewing of the PAM packaging. It's thanks to Jan that it's ready for wider review, since I did all the rediffing back in April, but lacked time to squash the last few bugs. If anyone could take the time to install it, test all the services using PAM for authentication/authorisation still work as expected, and report any defects, that would be much appreciated. If you want to avoid breaking your system, it is advisable to install into a chroot. However, we have tested that basic functionality does work (su and passwd in particular), so it should be safe to install for real (but no guarantees are given). Additionally, all of the packages which Build-Depend, Depend or Recommend PAM packages should be tested against the new packages. A complete list is given below, and the maintainer's Bcc'd with this message. If you do hack on the PAM sources, note that the dpatch patch order is important--later patches do rely on earlier patches being present. Also, you need to run debian/rules patch|unpatch by hand, due to the need to re-bootstrap the autotools. To do that debian/rules bootstrap will do everything consistently, providing the patches are applied. Some bits which need wider review and discussion: Several of the Debian-specific patches should probably be removed. For example, the @include (Debian-specific) syntax should be replaced by the include mechanism added by upstream; we should make this a release goal for Lenny IMO. Maintaining Debian-specific hacks imposes a real burden on the PAM maintainers--it took over 15 man hours to do the main re-diffing, and the same again to get it working, which is ridiculous and error-prone. We could easily be introducing Debian-specific security bugs by doing so. Some checks such as the obscure checks for pam_unix and chroot limits for pam_limits should be dropped (who uses this functionality)? The obsure checks appear to predate PAM, but should cracklib not be the replacement? This non-standard stuff should really be deprecated, obsoleted, then dropped. What do other people think about this? The remaining patches should then really be pushed upstream, which possible now we are synched with their latest stable release. One other note: upstream now default to enabling cracklib in pam_unix (in addition to pam_cracklib), which causes passwd to do all the extra checks cracklib does. This has been disabled for now after discussion with Jan, because it brings in quite a few dependencies into base, and may not be generally wanted. It also breaks passwd if you don't have cracklib-runtime *and* a wordlist *and* run update-cracklib, so this needs some fixing of dependencies and coordination to do properly. It might be worth re-adding, if there was consensus for that. I'm not yet sure how this differs from the pam_cracklib functionality, however. Regards, Roger Laszlo Boszormenyi (GCS) [EMAIL PROTECTED] gradm2 Stefan Hornburg (Racke) [EMAIL PROTECTED] courier courier-authlib pure-ftpd Richard A Nelson (Rick) [EMAIL PROTECTED] libnss-ldap libpam-ldap Marco Presi (Zufus) [EMAIL PROTECTED] linesrv Krzysztof Krzyzaniak (eloy) [EMAIL PROTECTED] popa3d Russ Allbery [EMAIL PROTECTED] libpam-afs-session Sebastien Bacher [EMAIL PROTECTED] libgnomesu Carlos Barros [EMAIL PROTECTED] tac-plus Dima Barsky [EMAIL PROTECTED] python-pam Vincent Bernat [EMAIL PROTECTED] xrdp Michael Biebl [EMAIL PROTECTED] partimage Laurent Bigonville [EMAIL PROTECTED] pam-keyring Blars Blarson [EMAIL PROTECTED] nntp Primoz Bratanic [EMAIL PROTECTED] pam-pgsql Joachim Breitner [EMAIL PROTECTED] poldi Adrian Bridgett [EMAIL PROTECTED] dante Chris Butler [EMAIL PROTECTED] wu-ftpd Rubén Porras Campo [EMAIL PROTECTED] libpam-encfs Pierre Chifflier [EMAIL PROTECTED] nufw wzdftpd Adam Conrad [EMAIL PROTECTED] poppassd Christopher Cramer [EMAIL PROTECTED] usermode Debian CUPS Maintainers [EMAIL PROTECTED] cupsys Debian Cyrus SASL Team [EMAIL PROTECTED] cyrus-sasl2 cyrus-sasl2-heimdal Debian Cyrus Team [EMAIL PROTECTED] cyrus-imapd-2.2 Debian Edu Developers [EMAIL PROTECTED] debian-edu Debian GNOME Maintainers [EMAIL PROTECTED] gdm Debian Kolab Maintainers [EMAIL PROTECTED] kolab-cyrus-imapd Debian Multimedia Team [EMAIL PROTECTED]
Bug#435867: kmail: Please only suggest instead of recommend procmail
On Friday 03 August 2007, Wolf Wiegand wrote: Package: kmail Version: 4:3.5.7-2 Severity: normal Hi, inspired by a recent mail to d-d-announce (http://lists.debian.org/debian-devel-announce/2007/08/msg0.html): Debian policy says that only those packages should be recommended by a package that 'would be found together with this one [the recommending package] in all but unusual installations'. I don't think that using kmail without procmail is unusual, so please consider only suggesting this package in kmails dependency fields. Thanks! It is recommends because it is needed. Not for procmail, but for the 'lockfile' utility in the procmail package. I agree that the use of procmail would just be of a 'suggests'-nature if mentioned at all, but several of the account types needs the lockfile command. /Sune -- How may I link the window? First of all you neither have to get access over the menu, nor must open a graphic POP button for debugging the microkernel over a modem of the DLL prompt of a Fast desktop to the line. signature.asc Description: This is a digitally signed message part.
Re: Bug#435093: konqueror does not show the correct language on websites
On Friday 02 March 2007, Hans wrote: Package: konqueror Version: 4:3.5.5a.dfsg.1-6 Severity: normal When calling some websites with konqueror, it should display the website in the language of the environment (in may case it is German). This behaviour is seen on the multilingual website of Debian (http://www.debian.org). What does your user agent string say? try look in the configure browser identification part of the konqueror configuration. /Sune Thwe language is falling automatically back to English, even, if I choose the German site manually. Outgoing links on this German website should be displayed in German, too. They are not. They are falling back to English, too. Thanks for help ! Best regards Hans :wq! -- I cannot send the utility, how does it work? From Explorer you cannot link the shell in order to load the site. signature.asc Description: This is a digitally signed message part.
Bug#436164: kpdf: Should link against poppler
Package: kpdf Version: 4:3.5.7-3 Severity: important [I'm considering this RC, but filing as important nonetheless for now] kpdf embeds a copy of xpdf, which causes a huge maintenance overhead whenever a security problem in found in xpdf. For Lenny kpdf should link against the library version of the xpdf source, poppler. Cheers, Moritz -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.22-1-686 (SMP w/1 CPU core) Locale: LANG=C, [EMAIL PROTECTED] (charmap=ISO-8859-15) Shell: /bin/sh linked to /bin/bash Versions of packages kpdf depends on: ii kdelibs4c2a 4:3.5.7.dfsg.1-3 core libraries and binaries for al ii libc6 2.6-5GNU C Library: Shared libraries ii libfontconfig1 2.4.2-1.2generic font configuration library ii libfreetype62.3.5-1+b1 FreeType 2 font engine, shared lib ii libgcc1 1:4.2.1-1GCC support library ii libjpeg62 6b-13The Independent JPEG Group's JPEG ii libpaper1 1.1.21 Library for handling paper charact ii libqt3-mt 3:3.3.7-6Qt GUI Library (Threaded runtime v ii libstdc++6 4.2.1-1 The GNU Standard C++ Library v3 ii libx11-62:1.0.3-7X11 client-side library ii libxft2 2.1.12-2 FreeType-based font drawing librar ii zlib1g 1:1.2.3.3.dfsg-5 compression library - runtime Versions of packages kpdf recommends: pn kghostviewnone (no description available) -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#436163: koffice: Needs to use poppler for Lenny
Package: koffice Severity: important [I'm considering this RC, but filing as important nonetheless for now] koffice embeds a copy of xpdf, which causes a huge maintenance overhead whenever a security problem in found in xpdf. For Lenny koffice should link against the library version of the xpdf source, poppler. Cheers, Moritz -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.22-1-686 (SMP w/1 CPU core) Locale: LANG=C, [EMAIL PROTECTED] (charmap=ISO-8859-15) Shell: /bin/sh linked to /bin/bash -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Kmail won't work with satellite provider....
Dietz Proepper wrote: Charlie: Have just subscribed to this list and using Icedove to post. Using Debian Etch/Lenny Have just been connected to satellite internet provider Clearnet who have some Linux capable techs on their staff, but have not been able to resolve a problem with Kmail 1.9.5 [using KDE 3.5.7] in Debian testing. These techs should train themselves regarding smtp ;-). Interesting, they sent me a message through kmail from their end, and I received it, but couldn't reply to it. If I attempt to send an email to myself, the test of the satellite provider [smtp], or anyone else using Kmail 1.9.5 [using KDE 3.5.7], with the new email address after setting the accounts up, I get an error message:- Sending failed: Message sending failed since the following recipients were rejected by the server: [EMAIL PROTECTED] (The server responded: relaying mail to clearmail.com.au is not allowed) This indicates that you could connect to the mail server but he rejected your mail for some reason. Therefore you should check this out with your email provider. The provider couldn't discover why this should happen from my end. They had no problem sending to me through kmail from their end? They did describe a different configuration window, so assume they were using something like Ubuntu rather than Debian. It sounded like a more up to date kmail. I have no problem sending through the old dialup provider and have used Kmail for years. This is a new twist. I'd assume that your satellite provider is blacklisted somewhere. Dietz Interesting as well? Icedove isn't blacklisted through that provider? Kmail is? You may well be right, but why kmail and not Icedove? Thanks for your suggestions. Charlie -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Kmail won't work with satellite provider....
On Sun, Aug 05, 2007 at 06:37:14PM +1000, Charlie wrote: If I attempt to send an email to myself, the test of the satellite provider [smtp], or anyone else using Kmail 1.9.5 [using KDE 3.5.7], with the new email address after setting the accounts up, I get an error message:- Sending failed: Message sending failed since the following recipients were rejected by the server: [EMAIL PROTECTED] (The server responded: relaying mail to clearmail.com.au is not allowed) This is your own ISP, and you are sending mail to them rather than to another ISP - have I read that right ? There are two things to check: have you got the right server, and can you authenticate to it OK. They don't seem to have a proper setup page, and there are slightly conflicting setups in the examples they give. Their FAQ at http://www.clearnetworks.com.au/faq.html says: '... using mail.clearmail.com.au as both your SMTP and POP3 servers, and you have selected Authenticated SMTP' OK it's talking about access from outside, but it does say the settings would be the same. However the page on how to setup Outlook Depress at http://www.clearnetworks.com.au/support/wireless_email_oe_setup.pdf says that you need to use an outgoing server specific to your town. I hope that mail.clearmail.com.au will function but you may need to check that detail with them. As for authentication, it's quite simple to set up. In Kmail/Configure/Accounts/Sending, just tick the box server requires authentication and put the username and password they've given you. Then go to the Security tab and press check what the server supports. I would expect it to automatically select TLS and one of the other options. OK through all that, and then give it a whirl, and let us know. Unfortunately kmail isn't too hot at diagnostics but sometimes you can catch an error message if you watch the progress dialogue after pressing the blue up-arrow on the bottom right of the main window. Nick -- http://www.leverton.org/blosxom (now updated!) ... So express yourself -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Kmail won't work with satellite provider....
Charlie: Dietz Proepper wrote: Charlie: Have just subscribed to this list and using Icedove to post. Using Debian Etch/Lenny Have just been connected to satellite internet provider Clearnet who have some Linux capable techs on their staff, but have not been able to resolve a problem with Kmail 1.9.5 [using KDE 3.5.7] in Debian testing. These techs should train themselves regarding smtp ;-). Interesting, they sent me a message through kmail from their end, and I received it, but couldn't reply to it. Sending and receiving email can be two completely different beasts. BTW, how (by which protocols) do you receive and send your mail? Sending failed: Message sending failed since the following recipients were rejected by the server: [EMAIL PROTECTED] (The server responded: relaying mail to clearmail.com.au is not allowed) This indicates that you could connect to the mail server but he rejected your mail for some reason. Therefore you should check this out with your email provider. The provider couldn't discover why this should happen from my end. They The email provider (as opposed to the access (satellite) provider)? They should at least see something in their log files. I'd assume that your satellite provider is blacklisted somewhere. Dietz Interesting as well? Icedove isn't blacklisted through that provider? Kmail is? You may well be right, but why kmail and not Icedove? Eh, you mean, icedove works and kmail fails? I must have overead that in your first mail. If they are configured the same way, this might indicate some glitch on kmail's side. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Kmail won't work with satellite provider....
Am Sonntag 05 August 2007 10:37 schrieb Charlie: Interesting as well? Icedove isn't blacklisted through that provider? Kmail is? So it's clear that your configuration may be wrong. Maybe IceDove uses a different port, does authentication (maybe even something sick like pop-before-smtp) or it's the message-id domain. Also look at the output of both mails to check for differences. A relay check in the smtp server can be configured to anything. Also check that you are actually sending to the right smtp smarthost (View menu in the kmail mail editor window). HS -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Kmail won't work with satellite provider....
On Sunday 05 August 2007 19:14, Nick Leverton sent this for all our perusal: ---} On Sun, Aug 05, 2007 at 06:37:14PM +1000, Charlie wrote: ---} ---} If I attempt to send an email to myself, the test of the satellite ---} provider [smtp], or anyone else using Kmail 1.9.5 [using KDE 3.5.7], ---} with the new email address after setting the accounts up, I get an error ---} message:- ---} ---} Sending failed: ---} Message sending failed since the following recipients were rejected by ---} the server: ---} [EMAIL PROTECTED] (The server responded: relaying mail to ---} clearmail.com.au is not allowed) ---} ---} This is your own ISP, and you are sending mail to them rather than to ---} another ISP - have I read that right ? There are two things to check: ---} have you got the right server, and can you authenticate to it OK. ---} ---} They don't seem to have a proper setup page, and there are slightly ---} conflicting setups in the examples they give. Their FAQ at ---} http://www.clearnetworks.com.au/faq.html says: ---} '... using mail.clearmail.com.au as both your SMTP and POP3 servers, ---} and you have selected Authenticated SMTP' ---} ---} OK it's talking about access from outside, but it does say the settings ---} would be the same. ---} ---} However the page on how to setup Outlook Depress at ---} http://www.clearnetworks.com.au/support/wireless_email_oe_setup.pdf says ---} that you need to use an outgoing server specific to your town. ---} ---} I hope that mail.clearmail.com.au will function but you may need to ---} check that detail with them. ---} ---} As for authentication, it's quite simple to set up. In ---} Kmail/Configure/Accounts/Sending, just tick the box server requires ---} authentication and put the username and password they've given you. ---} Then go to the Security tab and press check what the server supports. ---} I would expect it to automatically select TLS and one of the other ---} options. ---} ---} OK through all that, and then give it a whirl, and let us know. ---} Unfortunately kmail isn't too hot at diagnostics but sometimes you can ---} catch an error message if you watch the progress dialogue after pressing ---} the blue up-arrow on the bottom right of the main window. ---} ---} Nick ---} -- ---} http://www.leverton.org/blosxom (now updated!) ... So express yourself ---} ---} Am at an Internet Kiosk, where I volunteer some time this morning, and using Kmail to send test emails through the clearmail address, without any problems, without any changes in configuration to my lappy's Kmail configuration files. So it would appear to be an error with the Clearnetworks server which is giving me the problem, which doesn't get picked up in Icedove? Or maybe they have fixed it? Will have to see when I get back home tonight. Thank you to all for your help in trying to get this to work. Be well, Charlie -- Registered Linux User:- 329524 +++ 'Come to the edge', he said. They said..'We are afraid'. 'Come to the edge', he said. They came, he pushed them And they flew. __Guillaume Apollinaire *** Debian - an experience in magic. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
