Debian & Linux Daantje on 23 May 2005 12:59 pm
ipopd gives ‘unknown authorization state command’
Solution 1:
You should connect using SSL, this goes through port 995. On the server you should enable this in your /etc/inetd.conf:
pop3s stream tcp nowait root /usr/sbin/tcpd /usr/sbin/ipop3d
Than restart inetd
/etc/init.d/inetd restart
Reconfigure your pop3 client so it uses SSL passwords trough port 995. And it all should
work… If you are using the server behind NAT, don’t forget to forward
the port 995!
Solution 2:
But I had a problem with all my old Macintoshes connecting to my internal ‘debian/unstable (SID)’ pop3 (ipopd) server. Here’s how I enabled the plain text passwords again, and how I compiled new debian (.deb) packages again. (A real step-by-step howto I wrote for a friend of mine, so just copy paste the bold lines into your root shell. Even my mum can do this ;) )
First I created a directory:
mkdir /usr/src/ipopd
Go to the new created dir:
cd /usr/src/ipopd
And downloaded the debian source package:
apt-get source ipopd
Get dependencies:
apt-get build-dep ipopd
Now you should have the following:
- uw-imap-2002edebian1
- uw-imap_2002edebian1-3.diff.gz
- uw-imap_2002edebian1-3.dsc
- uw-imap_2002edebian1.orig.tar.gz
Go to the directory ‘uw-imap-2002edebian1′
cd /usr/src/ipopd/uw-imap-2002edebian1
Edit the make file:
vi Makefile
Search for the config line (now some crash course vi 4 U :-)
/SSLTYPE=nopwd
(’/’ means search in vi and vim and we’re going to look for the needle ‘SSLTYPE=nopwd’, to search again for the same needle, use a backslash)
Edit the line:
i
(this will enable the editor, now you can type into the document, change the line ‘SSLTYPE=nopwd’ to ‘SSLTYPE=none’ when you don’t want to use SSL, set the line to ‘SSLTYPE=unix’ when you want to be able to use both.)
SSLTYPE=none
Now press the escape button on your keyboard ;) This will disable the editor again so we can give commands to save and quit…
:wq
(’:’ will give a command, ‘w’ = write, ‘q’ = quit)
Now we should have a prompt again… Let’s bake a package. ;) Now you’ll have to change the changelog, or else when we’ve build and installed this package, and we do an apt-get upgrade, our fresh baked package will be overwritten by the original one again. Now concentrate! ;) You’ll need to edit the changelog in a special
format.
Open the file in vi and ADD the following lines AT THE TOP of the changelog file:
vi debian/changelog
uw-imap (7:2002edebian1-3b1) unstable; urgency=low * Disabled secure passw... -- Daantje Mon, 05 Apr 2004 20:34:34 +0200Please mind the TWO spaces, between the email address and date!
I’ve updated the original version ‘7:2002edebian1-3′ to ‘7:2002edebian1-3b1′ so the next upgrade will be done by apt-get when there’s a new release.
Now compile it with the debian script:
debian/rules build
(Wait while your machine compiles…)
debian/rules binary
(Wait while your machine creates the packages…)
The packages should be one directory above, we want to install them all! ;)
dpkg -i ../*.deb
(Wait wile it’s installing the packages)
We are done! Check your mail! Drink beer!
3 Responses to “ipopd gives ‘unknown authorization state command’”
Leave a Reply
You must be logged in to post a comment.
on 06 Jun 2008 at 3:22 pm 1.Issa Tangara said …
Hello,
When I try to build package:
issa:/usr/src/ipopd/uw-imap-2002edebian1# debian/rules binary
I have this error.
dh_installchangelogs -puw-imapd-ssl
parsechangelog/debian : erreur : ligne de fin mal formée, fichier debian/changelog ligne 7
dh_installchangelogs: changelog parse failure
make: *** [binary-install/uw-imapd-ssl] Erreur 1
Can I have your help ?
Issa Tangara
Bamako Mali
on 06 Jun 2008 at 5:49 pm 2.Issa Tangara said …
Hello,
When I do not add this lines:
uw-imap (7:2002edebian1-3b1) unstable; urgency=low
* Disabled secure passw…
— Daantje Mon, 05 Apr 2004 20:34:34 +0200
Every is OK.
Thank you.
Issa Tangara
Bamako Mali
on 06 Jun 2008 at 11:18 pm 3.Daantje said …
You could try to do a “debian/rules clean” before you build to loose that error… If you don’t change the changelog, the version number will not change. And then when you do an apt-get upgrade, your package will be over written by the default one out of the apt feed… There is a way to supress this, but you should google or rtfm for that ;) Do not know it by heart.