debian-user-digest Digest V2007 #2736

From: <debian-user-digest-request(at)lists.debian.org>
Date: Sun Nov 04 2007 - 01:44:56 EDT

Content-Type: text/plain

debian-user-digest Digest Volume 2007 : Issue 2736

Today's Topics:

  Re: Which browser is better, firefox  [ Jose Luis Rivas Contreras  ]
  Re: firewall installation question    [ Paul E Condon  ]
  Re: "Waiting for root file system...  [ Andrew Sackville-West  ]

  Re: Debian Failure Setting Password [ "Redefined Horizons" <redefined.hor ]   reading email from gmail account wit [ Alexandru Cardaniuc <cardaniuc@gmai ]

Date: Sat, 03 Nov 2007 22:44:06 -0400
From: Jose Luis Rivas Contreras <ghostbar38@gmail.com> To: debian-user@lists.debian.org
Cc: debian-user@lists.debian.org
Subject: Re: Which browser is better, firefox? Message-ID: <472D31F6.9020408@gmail.com> Content-Type: multipart/signed; micalg=pgp-sha1;  protocol="application/pgp-signature";
 boundary="------------enig6EDFDE0850C0C2FC2BDAAF45"

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)

--------------enig6EDFDE0850C0C2FC2BDAAF45
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

hce wrote:
> Hi,

>=20
> Is the firefox the best browser?

The "best" word is a relative-word, not absolute. If you like it better then is the best for _you_.

>=20

> When I installed the Debian, it automatically included iceweasel. I
> removed it and tryed to install firefox by "apt-get install firefox",
> but it it got iceweasel gain. How can I install the firefox?

Iceweasel =3D=3D Firefox with name changed during compile time but the sa= me
at the end.

Regards,
Jose Luis.
--=20

ghostbar on debian linux 'sid' 2.6.22 x86_64-SMP - #382503 Weblog: http://ghostbar.ath.cx/ - http://linuxtachira.org http://debian.org.ve - irc.debian.org #debian-ve #debian-devel-es San Crist=C3=B3bal, Venezuela. http://chaslug.org.ve GPG: 0xCACAB118

--------------enig6EDFDE0850C0C2FC2BDAAF45
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFHLTH2OKCtW8rKsRgRArfpAKDZ7s0JHms2jOJlk7dgeXK8C2rdugCfd/WE a8V4SjYw4ojLdAlFyznYJHo=
=lihY
-----END PGP SIGNATURE----- --------------enig6EDFDE0850C0C2FC2BDAAF45--

Date: Sun, 4 Nov 2007 02:54:31 +0000
From: Andy Smith <andy@lug.org.uk>
To: debian-user@lists.debian.org
Subject: Re: Connect to remote CVS server Message-ID: <20071104025431.GF4325@bitfolk.com> Content-Type: multipart/signed; micalg=pgp-sha1;

        protocol="application/pgp-signature"; boundary="H5pgEA8DvTwLpheO" Content-Disposition: inline

--H5pgEA8DvTwLpheO

Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

Hi Rocky,

On Thu, Nov 01, 2007 at 01:11:54AM -0000, rockymaxsource wrote:
> Can any of you tell me how to use SSH to connect to remote CVS
> repository with user name and password please?

Set the CVS_RSH variable to 'ssh' and then use :ext:username as your username in the cvs root specification. For example:

$ export CVS_RSH=3D'ssh'
$ cvs -d :ext:andy@strugglers.net:/data/cvs checkout some_module

This checks out the module some_module, from the cvsroot of /data/cvs, on the host strugglers.net, over ssh, authenticating as user andy.

See
http://cvsbook.red-bean.com/cvsbook.html#Accessing%20A%20Repository for more information.

Cheers,
Andy

--=20
http://bitfolk.com/ -- No-nonsense VPS hosting Encrypted mail welcome - keyid 0x604DE5DB

--H5pgEA8DvTwLpheO

Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFHLTRnIJm2TL8VSQsRAuiXAKC4dN6V8QwbSeUfQT0kMnjJghxFfgCeK6ci ukkEgdS4SkReDjndBb8hyyU=
=hSEd
-----END PGP SIGNATURE----- --H5pgEA8DvTwLpheO--

Date: Sat, 3 Nov 2007 21:15:54 -0600
From: Paul E Condon <pecondon@mesanetworks.net> To: debian-user@lists.debian.org
Subject: Re: firewall installation question

Message-ID: <20071104031554.GC5997@big.lan.gnu>
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline

On Sun, Nov 04, 2007 at 01:53:57AM +0000, Steve Kemp wrote:
> On Sat Nov 03, 2007 at 19:49:40 -0600, Paul E Condon wrote:
>
> > > You must chmod +x this script:
> > > # chmod +x script_name
> > >
> >
> > Thanks, but I was forced to +x the script in order to run it manually.
> > Something else is the problem.
>
> Files in that directory are executed by 'run-parts'. That
> has some restrictions upon the filenames you may use. See
> 'man run-parts' for details.

Yes! I knew that once! My filename contained a dot-extension. Get rid of the dot and now it works!
Oh joy! Oh rapture!

And Thankyou, Thankyou, Thankyou.

-- 
Paul E Condon           
pecondon@mesanetworks.net

Date: Sat, 3 Nov 2007 20:56:27 -0700 From: Andrew Sackville-West <andrew@farwestbilliards.com> To: debian-user@lists.debian.org Subject: Re: Thinkpad T20 wireless troubles - revisited Message-ID: <20071104035627.GR12370@localhost.localdomain> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="b0op/nKJ9CeIhp9z" Content-Disposition: inline --b0op/nKJ9CeIhp9z Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, Nov 04, 2007 at 12:46:45AM +0100, Sjoerd Hiemstra wrote:
> Op Tue, 30 Oct 2007 23:23:11 -0400 Celejar wrote:
> > On Tue, 30 Oct 2007 23:10:48 +0100 Sjoerd Hiemstra wrote:
> > > Following the directions at [2], the entry for wifi0
> > > in /etc/network/interfaces now looks like this:
> > >=20
> > > iface wifi0 inet dhcp
> > > wireless-essid <....>
> > > wireless-key <....>
> > > auto wifi0
> > > allow-hotplug wifi0
> > >=20
> > > If I do an 'iwlist wifi0 scan' then my AP is detected correctly (as
> > > well as two neighbouring APs - interesting).
> > >=20
> > > There is only one remaining obstacle.
> > > The following messages appear if I do an 'ifup wifi0'.
> > > They also appear after '/etc/init.d/networking stop' and then
> > > '/etc/init.d/networking start'.
> > > And they also appear if I do a 'dhclient wifi0'.
> > >=20
> > > wifi0: unknown hardware address type 801
> > > wifi0: unknown hardware address type 801
> > > Listening on LPF/wifi0/
> > > Sending on LPF/wifi0/
> > > Sending on Socket/fallback
> > > DHCPDISCOVER on wifi0 to 255.255.255.255 port 67 interval 5
> > > DHCPDISCOVER on wifi0 to 255.255.255.255 port 67 interval 12
> > > DHCPDISCOVER on wifi0 to 255.255.255.255 port 67 interval 14
> > > DHCPDISCOVER on wifi0 to 255.255.255.255 port 67 interval 11
> > > DHCPDISCOVER on wifi0 to 255.255.255.255 port 67 interval 12
> > > DHCPDISCOVER on wifi0 to 255.255.255.255 port 67 interval 7
> > > No DHCPOFFERS received.
> > > No working leases in persistent database - sleeping.
> > >=20
> > > Something wrong with DHCP on the AP? My main computer works well
> > > with it, through a wired ethernet connection.
Since you question the state of DHCP on the AP, then have you checked that? It may be that you can control whether DHCP is offered over wireless independently of whether it is offered over wired interface.=20
> >=20
> > This can also indicate that the card isn't properly associating with
> > the AP. What does 'iwconfig wifi0' give?
>=20
> # iwconfig wifi0
> wifi0 IEEE 802.11-DS ESSID:"SX551559148"
> Mode:Managed Frequency:2.432 GHz Access Point:00:01:E3:55:91:48
> Bit Rate:11 Mb/s Tx-Power=3D17 dBm Sensitivity=3D0/65535
> Retry limit:16 RTS thr:off Fragment thr:off
> Encryption key:****-****-****-****-****-****-** [4] Security mode=
:open
> Power Management:off
> Link Quality=3D80/100 Signal level=3D-55 dBm Noise level=3D-98 =
dBm
> Rx invalid nvid:614 Rx invalid crypt:437 Rx invalid frag:0
> Tx excessive retries:0 Invalid misc:12986 Missed beacon:0
I looks like it *is* associated with the Access Point listed above. Is that you're access point? Look at the MAC address on the bottom of the AP. >=20
> The output of 'dmesg | grep airo' is:
> airo(): Probing for PCI adapters
> airo(eth0): Found an MPI350 card
> airo(eth0): WPA is supported.
> airo(eth0): MAC enabled 0:2:8a:dd:a6:b7
> airo(): Finished probing for PCI adapters
>=20
> So I am under the impression that I should use the eth0 interface instead.
> But then 'iwconfig eth0' gives hardly any difference:
>=20
> # iwconfig eth0
> eth0 IEEE 802.11-DS ESSID:"SX551559148"
> Mode:Managed Frequency:2.432 GHz Access Point:00:01:E3:55:91:48
here you are associated with the same AP, looks like it doesn't matter which interface name you use.
> Bit Rate:11 Mb/s Tx-Power=3D17 dBm Sensitivity=3D0/65535
> Retry limit:16 RTS thr:off Fragment thr:off
> Encryption key:****-****-****-****-****-****-** [4] Security mode=
:open
> Power Management:off
> Link Quality=3D72/100 Signal level=3D-59 dBm Noise level=3D-98 =
dBm
> Rx invalid nvid:94 Rx invalid crypt:341 Rx invalid frag:0
> Tx excessive retries:0 Invalid misc:4709 Missed beacon:0
>=20
> And still there's the error message 'No DHCPOFFERS received'.
> And there is some difference with the output of 'iwlist eth0 scan':
>=20
> # iwlist eth0 scan
> ....
> Cell 03 - Address: 00:01:E3:55:91:48
> ESSID:"SX551559148"
> Mode:Master
> Frequency:2.432 GHz (channel 5)
> Quality=3D88/100 Signal level=3D-51 dBm Noise level:-98 dBm
> Encryption key:on
> Bit rates: 1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 6Mb/s
> 12 Mb/s; 24 Mb/s; 36 Mb/s
> Extra:bcn_int=3D100
> IE: IEEE 802.11i/WPA2 Version 1
-----------------------------^^^^ Are yiou using wpasupplicant? Looks like you need to use wpa to connect... A --b0op/nKJ9CeIhp9z Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFHLULraIeIEqwil4YRAi18AJ49iLorH/EXmZOWxwAL1l771I9f6ACgxO6G JJ+HbcYVcDodDEEs8+a238k= =hSi5 -----END PGP SIGNATURE----- --b0op/nKJ9CeIhp9z--

Date: Sat, 3 Nov 2007 20:47:27 -0700 From: "Redefined Horizons" <redefined.horizons@gmail.com> To: debian-user <debian-user@lists.debian.org> Subject: Debian Failure Setting Password Message-ID: <e24752a10711032047k36ea9cd8hdd2369221bf1f737@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline I've run into a problem after I performed the following: [1] Changed the password for my root user with the usermod command. [2] Changed the password of a non-root user with the usermod command. [3] Added a new user with a password using the useradd command. After making these changes I could no longer log in as the root user or the non-root user for whom I changed the password. I also could not log in as the new user. I tried this with both old and new passwords. (All user names were recognized, but Debian is telling me the passwords are incorrect.) I booted with the System Rescue CD and followed the advice at this link: http://www.debianadmin.com/forgot-root-password-or-reset-root-password-in-debian.html When I edited the etc/shadow file I found the passwords for the root user, non-root user, and new user to be exactly as I had set them with the usermod and useradd commands. The passwords are the same ones that failed. I reset them using nano and System Rescue CD. After a reboot the original passwords, the new passwords, and the passwords reset using the System Rescue CD all failed. Note: I had one existing non-root user whose password I did not modify. I can still log into my system using this user. I am know backing up that users data in case I have to reinstall. Does anyone have any idea what is going on? I'm really wishing that I wouldn't have reset that root password now. It's the last time I'll ever do that. I really appreciate any suggestion on how to resolve this. I hope I don't have to reinstall and/or loose the data for the other users. Scott Huey

Date: Sun, 4 Nov 2007 14:54:25 +1100 From: hce <webmail.hce@gmail.com> To: "Gerard Robin" <g.robin3@free.fr> Cc: debian <debian-user@lists.debian.org> Subject: Re: How to set up postfix logfile Message-ID: <95455e980711032054n24d0d356m2c0c7ee5608a8d0c@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Thanks Gerard, I tried, but did not give me the informaiotn where is the postfix log file. The postfix has been restarted, but I still could not send mails from the mutt. Thank you. Kind Regards, Jim On 11/4/07, Gerard Robin <g.robin3@free.fr> wrote:
> On Sun, Nov 04, 2007 at 10:50:56AM +1100, hce wrote:
> >From: hce <webmail.hce@gmail.com>
> >To: debian-user@lists.debian.org
> >Subject: How to set up postfix logfile
> >X-Spam-Status: No, score=3D-5.75 tagged_above=3D3.6 required=3D5.3 tests=
=3D[AWL=3D0.614,
> > BAYES_00=3D-2, LDO_WHITELIST=3D-5, SARE_MSGID_LONG40=3D0.637,
> > SPF_PASS=3D-0.001]
> >X-Spam-Level:
> >
> >Hi,
> >
> >I sent emails from mutt, but does not seem work. Where can I check
> >postfix logfile? The postfix is called from booting, I could not find
> >config file from postfix?
>
> Try:
> sudo dpkg-reconfigure postfix
>
> hth
> --
> G=E9rard
> >

Date: Sat, 3 Nov 2007 21:14:44 -0700 From: Andrew Sackville-West <andrew@farwestbilliards.com> To: debian-user@lists.debian.org Subject: Re: "Waiting for root file system..." hang solved Message-ID: <20071104041444.GS12370@localhost.localdomain> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="DIYaQRZjygY6fA2m" Content-Disposition: inline --DIYaQRZjygY6fA2m Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sat, Nov 03, 2007 at 02:38:36AM +0000, Cameron L. Spitzer wrote:
> In article <9ldY5-Hs-17@gated-at.bofh.it>, Andrew Sackville-West wrote:
>=20
> > I've had to learn my
> > way around that having just reconfigured my laptop. The critical item
> > is the contents of $ROOT. The value of $ROOT gets set by the kernel
> > command line and if it doesn't match, then you have trouble. If you
> > change that to the appropriate value you can then 'exit' busybox and
> > the boot will carry on.
>=20
> I didn't know that. If I hadn't had a working option in GRUB
> I would have tried editing the kernel command line next.
> I've also rescued Debian by booting Knoppix, mounting stuff,
> and running a chroot shell.
it turns out you can do a reasonable amount of stuff in that busybox shell and if the system is close to booting, you can get it to go. What I was missing, and desperately wanted, was some kind of text editor. I ended up have to do some funky 'cat'ing of files and text input to tweak an encryption-key script. Not fun without an editor, but you sure can do it...=20 >=20 >=20
> > Once you're up and running, then rebuil the
> > initrd's.
>=20
> I actually tried that before going to volume labels. Rebuilding
> the initrd puts the same old /etc/fstab in the new initrd image.
sorry, updating /etc/fstab apparently doesn't go without saying... ;).=20
> That doesn't get you past the udev hang. I guess a more sophisticated
> update-initrd would alert you to the difference between the
> current mtab and the /etc/fstab contents.
There are a handful of issues I've seen with currnet initramsfs-tools that probably need addressing. The one I ran across: the lvm and encrypted root scripts expect /dev/mapper/ names with hyphens in them. I have /dev/mapper/vgcrypt-root (an LVM volume on top of encrypted partition). I prefer to access these things through /dev/vgcrypt/root (or whatever it was), but the scripts are expecting that hyphenated name... it appears to only be documented in the code itself. oh well. it works now...
> I've been using Debian for a long time. It's just *weird* to
> see anything broken like that.
somewhere Linus talks about breaking UUID names as well, on purpose, because he thinks there should be some other persistent naming method and since UUID is generated in user space, its not reliable. I don't know, but watch out for that. A --DIYaQRZjygY6fA2m Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFHLUc0aIeIEqwil4YRAgE2AKC8DQXNtf3FagMQe4bu/ZHcXj1fyQCfbYCj m6Q/8CemvgOKyKvrJD4hNLM= =qs9n -----END PGP SIGNATURE----- --DIYaQRZjygY6fA2m--

Date: Sat, 3 Nov 2007 21:22:14 -0700 From: Andrew Sackville-West <andrew@farwestbilliards.com> To: debian-user@lists.debian.org Subject: Re: Debian Failure Setting Password Message-ID: <20071104042214.GT12370@localhost.localdomain> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="7Ha3rcGc4ZVRbLT1" Content-Disposition: inline --7Ha3rcGc4ZVRbLT1 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sat, Nov 03, 2007 at 08:47:27PM -0700, Redefined Horizons wrote:
> I've run into a problem after I performed the following:
>=20
> [1] Changed the password for my root user with the usermod command.
> [2] Changed the password of a non-root user with the usermod command.
according to man usermod, the --password command expects an encrypted password. did you supply encrypted passwords?
> [3] Added a new user with a password using the useradd command.
>=20
> After making these changes I could no longer log in as the root user
> or the non-root user for whom I changed the password. I also could not
> log in as the new user. I tried this with both old and new passwords.
> (All user names were recognized, but Debian is telling me the
> passwords are incorrect.)
>=20
> I booted with the System Rescue CD and followed the advice at this link:
>=20
> http://www.debianadmin.com/forgot-root-password-or-reset-root-password-in=
-debian.html >=20
> When I edited the etc/shadow file I found the passwords for the root
> user, non-root user, and new user to be exactly as I had set them with
> the usermod and useradd commands. The passwords are the same ones that
> failed. I reset them using nano and System Rescue CD.
did you reset them or delete them? I think you need to delete them (remove the characters between the first and second colon) because they get stored in an encrypted method. You'd have to know what wacky string to type so that the encrypted output matches whatever plain text is in there... I think go back in through system rescue cd, delete the passwords, log in with blank passwords and then change them using passwd.=20 >=20
> After a reboot the original passwords, the new passwords, and the
> passwords reset using the System Rescue CD all failed.
>=20
> Note: I had one existing non-root user whose password I did not
> modify. I can still log into my system using this user. I am know
> backing up that users data in case I have to reinstall.
>=20
> Does anyone have any idea what is going on? I'm really wishing that I
> wouldn't have reset that root password now. It's the last time I'll
> ever do that.
well, better to learn to do it properly than not do it at all... A --7Ha3rcGc4ZVRbLT1 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFHLUj2aIeIEqwil4YRAgPDAJ4n7fX37GdhTSGt1oKK0oRmRtizcQCfTRpM rTGswZDKPf875B6tI6kFDiw= =zIjG -----END PGP SIGNATURE----- --7Ha3rcGc4ZVRbLT1--

Date: Sun, 4 Nov 2007 00:17:36 -0400 From: Carl Fink <carl@finknetwork.com> To: debian-user@lists.debian.org Subject: Re: How to set up postfix logfile Message-ID: <20071104041736.GA6744@nitpicking.com> Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Sun, Nov 04, 2007 at 02:54:25PM +1100, hce wrote:
> Thanks Gerard, I tried, but did not give me the informaiotn where is
> the postfix log file. The postfix has been restarted, but I still
> could not send mails from the mutt.
The default location is /var/log/mail.log. Please don't top-post. -- Carl Fink nitpicking@nitpicking.com Read my blog at nitpickingblog.blogspot.com. Reviews! Observations! Stupid mistakes you can correct!

Date: Sat, 3 Nov 2007 21:29:02 -0700 From: "Redefined Horizons" <redefined.horizons@gmail.com> To: debian-user@lists.debian.org Subject: Re: Debian Failure Setting Password Message-ID: <e24752a10711032129v7efb181dhc41a28854ac8d27@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline Andrew, You are probably correct. I didn't think about encryption. I'm going to give the system rescue cd another shot. Scott Huey On 11/3/07, Andrew Sackville-West <andrew@farwestbilliards.com> wrote:
> On Sat, Nov 03, 2007 at 08:47:27PM -0700, Redefined Horizons wrote:
> > I've run into a problem after I performed the following:
> >
> > [1] Changed the password for my root user with the usermod command.
> > [2] Changed the password of a non-root user with the usermod command.
>
> according to man usermod, the --password command expects an encrypted
> password. did you supply encrypted passwords?
>
> > [3] Added a new user with a password using the useradd command.
> >
> > After making these changes I could no longer log in as the root user
> > or the non-root user for whom I changed the password. I also could not
> > log in as the new user. I tried this with both old and new passwords.
> > (All user names were recognized, but Debian is telling me the
> > passwords are incorrect.)
> >
> > I booted with the System Rescue CD and followed the advice at this link:
> >
> > http://www.debianadmin.com/forgot-root-password-or-reset-root-password-in-debian.html
> >
> > When I edited the etc/shadow file I found the passwords for the root
> > user, non-root user, and new user to be exactly as I had set them with
> > the usermod and useradd commands. The passwords are the same ones that
> > failed. I reset them using nano and System Rescue CD.
>
> did you reset them or delete them? I think you need to delete them
> (remove the characters between the first and second colon) because
> they get stored in an encrypted method. You'd have to know what wacky
> string to type so that the encrypted output matches whatever plain
> text is in there...
>
> I think go back in through system rescue cd, delete the passwords, log
> in with blank passwords and then change them using passwd.
> >
> > After a reboot the original passwords, the new passwords, and the
> > passwords reset using the System Rescue CD all failed.
> >
> > Note: I had one existing non-root user whose password I did not
> > modify. I can still log into my system using this user. I am know
> > backing up that users data in case I have to reinstall.
> >
> > Does anyone have any idea what is going on? I'm really wishing that I
> > wouldn't have reset that root password now. It's the last time I'll
> > ever do that.
>
> well, better to learn to do it properly than not do it at all...
>
> A
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.6 (GNU/Linux)
>
> iD8DBQFHLUj2aIeIEqwil4YRAgPDAJ4n7fX37GdhTSGt1oKK0oRmRtizcQCfTRpM
> rTGswZDKPf875B6tI6kFDiw=
> =zIjG
> -----END PGP SIGNATURE-----
> >

Date: 03 Nov 2007 21:50:07 -0700 From: Alexandru Cardaniuc <cardaniuc@gmail.com> To: debian-user@lists.debian.org Subject: reading email from gmail account with gnus in Emacs22 Message-ID: <87y7dewr5s.fsf@gmail.com> Content-Type: text/plain; charset=us-ascii Hi All! Does anybody here use gnus from Emacs22 to read mail from gmail account? I managed to make it work with Emacs21. Recently I tried Emacs22 and my old config from Emacs21 doesn't work. I get some errors when fetching from gmail with pop. Did anybody here manage to make gnus in Emacs22 work with gmail? Any hints on the configuration of .gnus ? That's the setup that works fine for Emacs21 but doesn't work for Emacs22: ------------------------------------------- (setq user-full-name "Alexandru Cardaniuc") (setq user-mail-address "whatever@gmail.com") ;; using GNUS to send mail (setq message-send-mail-function 'smtpmail-send-it) (setq send-mail-function 'smtpmail-send-it) ;; use 'one file per mail' back end (setq gnus-select-method '(nnml "")) (setq gnus-secondary-select-methods nil) ;; tell Gnus how to fetch mail (setq mail-sources '((file :path "/var/spool/mail/alexandru") (pop :server "pop.gmail.com" :port 995 :user "whatever@gmail.com" :connection ssl :password "secret" :leave t))) ; leave the mail on the server (load-library "smtpmail") (load-library "pop3") (load-library "starttls") ;(setq pop3-debug t) (setq smtpmail-local-domain nil) ;(setq smtpmail-debug-info t) ; only to debug problems (setq smtpmail-auth-credentials '(("smtp.gmail.com" 25 "whatever@gmail.com" "secret"))) (setq smtpmail-starttls-credentials '(("smtp.gmail.com" 25 nil nil))) (setq smtpmail-smtp-service "25") ------------------------------------------ -- "The only thing necessary for evil to flourish is for good men to do nothing." - Edmund Burke End of debian-user-digest Digest V2007 Issue #2736 ************************************************** Received on Sun Nov 4 01:45:08 2007