[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-bugs-dist
Subject:    [Bug 73936] New: special transport doesn't work
From:       Neal Becker <ndbecker () verizon ! net>
Date:       2004-02-01 1:56:30
Message-ID: 20040201015630.26970.qmail () ktown ! kde ! org
[Download RAW message or body]

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
      
http://bugs.kde.org/show_bug.cgi?id=73936      
           Summary: special transport doesn't work
           Product: kmail
           Version: 1.6
          Platform: unspecified
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: NOR
         Component: general
        AssignedTo: kmail-devel@kde.org
        ReportedBy: ndbecker@verizon.net


Version:           1.6 (using KDE 3.2.0 RC1, compiled sources)
Compiler:          gcc version 3.3.2 20031022 (Red Hat Linux 3.3.2-1)
OS:          Linux (i686) release 2.4.22-1.2149.nptl

I have 2 accounts at verizon dot net, they are
ndbecker and ndbecker2.

I setup 2 identities, verizon and verizon2.

I do edit identities, choose verizon2, and choose special transport.  select \
verizon2.

I have already setup an outgoing account for verizon2.

When I try to send with verizon2 identity, it fails (because verizon required \
authentication, and auth is different for the two accounts), but it says

 Sending failed:
The server did not accept the sender address "ndbecker2 at verizon.net". The server \
responded: "You are not authorized to send mail as " The message will stay in the \
'outbox' folder until you either fix the problem (e.g. a broken address) or remove \
the message from the 'outbox' folder. The following transport protocol was used: \
verizon

Note the last part!  It isn't using verizon2, even though I have repeatedly tried to \
tell it to use the special transport, and even tried exiting and restarting kmail.


[prev in list] [next in list] [prev in thread] [next in thread]