Bug 699249

Summary:	up-imapproxy does not open listening socket
Product:	[Fedora] Fedora EPEL	Reporter:	Jeroen van Meeuwen <vanmeeuwen+fedora>
Component:	up-imapproxy	Assignee:	Tim Jackson <rpm>
Status:	CLOSED WORKSFORME	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	el5	CC:	bryan691, jeff, manuel.wolfshant, rpandit, rpm
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2011-10-09 19:37:24 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Jeroen van Meeuwen 2011-04-24 16:05:49 UTC

Description of problem:

up-imapproxy does not open a listening socket on 127.0.0.1:143 though the configuration in /etc/imapproxy.conf describes that it should.

Version-Release number of selected component (if applicable):

up-imapproxy-1.2.6-1.el5

How reproducible:

Every time

Steps to Reproduce:
1. Install up-imapproxy
2. Configure if necessary
3. Start manually from console with strace
4. Give it a few seconds
5. Abort running process
6. Analyze strace for opening sockets
  
Actual results:

No 127.0.0.1:143 listener socket is opened.

Expected results:


Additional info:

Comment 1 Tim Jackson 2011-07-31 18:42:43 UTC

Was your IMAP daemon already running before you started up-imapproxy?

Comment 2 Jeroen van Meeuwen 2011-08-01 00:55:33 UTC

Yes, where the imap server is running on a remote server, and no other processes had any sockets open on :143

Comment 3 Tim Jackson 2011-10-09 19:37:24 UTC

Works for me. If you still have this problem, please consider seeking help on the upstream mailing list, and if it turns out to be a problem with the packaging then please re-open this bug.

Comment 4 bryan691 2020-10-02 15:30:58 UTC

Hi,

I'm having the same issue.

Up-imapproxy-1.2.7-2.1

Operating System: Suse 11 SP4

Comment 5 Tim Jackson 2020-10-02 19:51:33 UTC

(In reply to bryan691 from comment #4)

> I'm having the same issue.
> Up-imapproxy-1.2.7-2.1
> Operating System: Suse 11 SP4

This bugtracker is for Fedora and EPEL only. We definitely can't help with SuSE.
Here's the upstream mailing list, which might be a better place to seek help: https://sourceforge.net/projects/squirrelmail/lists/squirrelmail-imapproxy