sendmail & qpopper

SUSE Linux Enterprise Server SLES Configure-Administer
1

A client who system is to be upgraded from SLES 11 to SLES 12 uses sendmail and qpopper for mail services. They want to stick with that setup. Getting sendmail running on SLES 12 SP5 wasn’t much of a challenge, but qpopper is another matter. I really don’t want to have to migrate to dovecot, mostly because documentation on that software is poor and time is of the essence in making this conversion. Can anyone point me toward either a qpopper RPM or source code that I can build on SLES 12?

Thanks!

2

Hi
That is pretty old code? Looks like a user has cleaned a few things up here;
https://build.opensuse.org/package/show/home:vodoo/qpopper
You could just ask the home repo owner to add the build target your after?
The src rpm is here;
https://download.opensuse.org/repositories/home:/vodoo/SLE_11/src/qpopper-4.1.0-6.1.src.rpm

3

https://build.opensuse.org/package/show/home:vodoo/qpopper

I’ve been there. The page prompts me for a username and password when I attempt to download anything. I haven’t a clue what credentials are expected.

:smile:

4

Hi
You need to create an account, but the download link for the src rpm should work?

5

I have an account at OpenSuSE (as well as here, of course), but the credential request doesn’t recognize my username and password as valid. I can log into OpenSuSE.

I was able to grab the qpopper source RPM. All rpm -i does is lodge the source into /usr/src/packages/SOURCE. The source will not build on SLES12 SP5 or SLES11 SP4. After installing bison and flex, I was able to configure the source but the compilation failed almost immediately with errors:

In file included from pop_dele.c:29:0:
popper.h:316:30: error: conflicting types for ‘sys_errlist’
      extern char         *   sys_errlist[];
                              ^
In file included from /usr/include/stdio.h:853:0,
                 from pop_dele.c:24:
/usr/include/bits/sys_errlist.h:27:26: note: previous declaration of ‘sys_errlist’ was here
 extern const char *const sys_errlist[];
                          ^
Makefile:224: recipe for target 'pop_dele.o' failed
make[1]: *** [pop_dele.o] Error 1
Makefile:72: recipe for target 'popper_server' failed
make: *** [popper_server] Error 2

My alternative is to convince the client to go with dovecot. He is strongly resistant to that due to dovecot’s dismal documentation. I can’t figure out much of dovecot, and I’ve been doing E-mail on UNIX and Linux for some 30 years.

6

Hi
OK, let me have a play…

7

Hi
https://build.opensuse.org/package/show/home:malcolmlewis:SLE_12_General/qpopper
A build should be available at https://download.opensuse.org/repositories/home:/malcolmlewis:/SLE_12_General/SLE_12_SP5 soon (it needs to publish for the repo to appear).

Do you need it for SLE 11 SP4?

8

The first link is the one asking for unknown log-in credentials.

I will give the second link a try. Can I zypper that, or do I have to download the file and rpm it?

Regarding SLES11 SP4, my software development machine is running on that release and already has qpopper. I was try to build from the source RPM on that machine after I couldn’t get it to compile on SLES12 SP5.

9

Hi
Yes, zypper in https://download.opensuse.org/repositories/home:/malcolmlewis:/SLE_12_General/SLE_12_SP5/x86_64/qpopper-4.1.0-1.1.x86_64.rpm will work

10

Got qpopper working on SLES12 SP5. Thank you so much!

What I’d be interested in knowing is what you had to do to get qpopper to compile. I struggled with trying to get it past gcc but could not seem to resolve whatever dependencies were involved. I’d like to have buildable source code available, as I am anticipating this scenario again with some other clients’ systems.

11

Hi
I would suggest creating an account on the Build Service, you can use osc on your local machine or just copy a package into your home build area, add a build target and away you go. Then the fun begins…

I’d need to see the whole build log as don’t have a SLE 12 SP5 setup, likely a missing build requires.

BuildRequires:  gdbm-devel openssl-devel pam-devel postfix

Just remember, installing packages like mine would likely create support issues.
If I need in SLE and it’s in openSUSE Tumbleweed it can be submitted to SUSE Package Hub :wink:

12

“Just remember, installing packages like mine would likely create support issues.”

I hammered away at qpopper for a while, using encrypted user/pass exchanges. Everything seems copacetic. We are going to run a live test in a few days, which should uncover any problems, if they exist.

Again, thanks!

13

“BuildRequires: gdbm-devel openssl-devel pam-devel postfix”

The target system is using sendmail instead of postfix. postfix is not installed and is the case with dovecot, is not wanted.

14

Hi
Well the errors you saw are from the standard development libs, so something conflicted somewhere…
If you have problems, just post back here and will see what i can do :slight_smile:

15

It’ll likely be a few days before I take another whack at compiling qpopper. Too much stuff to do and insufficient time in which to do it. :slight_smile: