Bug 145643

Summary:	Kmail fails EITHER to Receive OR instead to Send when configured to BTOpenworld (server=mail.btinternet,com)PAYG
Product:	[Unmaintained] kmail	Reporter:	Richard Wilford <rw>
Component:	general	Assignee:	kdepim bugs <kdepim-bugs>
Status:	RESOLVED REMIND
Severity:	normal
Priority:	NOR
Version:	unspecified
Target Milestone:	---
Platform:	openSUSE
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Richard Wilford 2007-05-18 18:37:23 UTC

Version: (using KDE KDE 3.5.5)
Installed from: SuSE RPMs
Compiler: gcc41 == 4.1.2_20061115-5
OS: Linux

I am a technician atteempting to set up KMAIL for a client on a new Fujitsu-Siemens notebook with external USB dial-up modem using SuSE Linux 10.2 and the associated KDE desktop. I have used this (Kortex modem and configured KMail successfully many times. However with this installation and using ISP BTOpenworld which in turn relates to the common POP3=SMTP server address of mail.btinternet.com one operation of EITHER sending OR reciving of email is disfunctional.
No error messages are reported.

The settings have all been transferred identically from a pre-existing PC running MS Windows and Outlook Express version5 which displays no such problem.

The original attempt at configuration resulted in an initial Outgoing test mail being sent and an apparent block on receiving. Then apparently the situation reversed with no evident changes being made, whereafter no emails could then be sent, but Incoming mail was received AOK. After wiping all the settings and starting over, using the same settings apart from including the full email address as the UserName in both POP3 and SMTP configuration (though only the stem of the Username without the domain functioned without problem under Outlook Express) transmission of email now functions but not reception.
i.e. One can either send or receive but not both,
Is a complete uninstall of KDEpim3 and then reinstallation first required within SuSE Linux, or is there a simpler or more rational solution

Comment 1 Philip Rodrigues 2007-05-19 23:07:37 UTC

Can you be a bit more specific about what's not working? ie, what steps do you perform, what do you expect to happen, and what *actually* happens? I suspect this is a configuration issue rather than a bug

Comment 2 Richard Wilford 2007-06-02 14:07:41 UTC

All KMail configuration settings are confirmed as correct against BT configuration instructions and by direct contact with their Tech Support
Sending of email works trouble-free(which for this ISP requires authenticated SMTP by username and password)
Receiving of email does not even give any indication of trying to contact the server since it instantly reports 'No New Messages' even when messages awaiting download are known to reside on the ISP server.
The ISP Send AND Receive servers are identical

Suse 10.2 has been fully re-installed as a new installation and Yast>Network Devices>modems reconfigured
The modem is an external hardware modem connected via a serial-USB adapter and designated as ttyUSB0.  There is no difficulty experienced in connecting and holding the line (nor indeed when sending email).

In SuSE 10.2 it seems impossible to disable/uninstall Network Manager when attempting to use Kinternet, though the problem arises whichever of these two modules is used.
P does however work under MS Windows Millennium/Outlook Express5 on another PC with an internal PCI modem.

What more specific extra information might be helpful?

With thanks
Richard WILFORD

Comment 3 Richard Wilford 2007-06-02 16:06:05 UTC

PS
In desperation, we installed Mozilla Thunderbird with exactly the same configuration settings, which immediately works whereas KMail fails.

Comment 4 Philip Rodrigues 2007-06-03 14:05:46 UTC

Try the following: 
1. Install debug-enabled KDE packages (see below).
2. Run "KDE_FORK_SLAVES=1 kmail" from a konsole.
3. Run "Check mail" in kmail
4. Look at the debug output from the konsole - some of it may be relevant to the problem.

You can find information about getting debug-enabled packages for your distro at:
http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports
in the section "Preparing your KDE packages".

In fact, I suggest we move this discussion to the kde@kde.org mailing list - there are more people reading that list than there are here. If this does turn out to be a real bug and not a config issue, we can reopen this report. Thanks!