To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=105669 Issue #|105669 Summary|Problems with sending a newsletter through Open Office Component|Word processor Version|OOo 3.1 Platform|PC URL| OS/Version|Windows XP Status|UNCONFIRMED Status whiteboard| Keywords| Resolution| Issue type|DEFECT Priority|P1 Subcomponent|configuration Assigned to|writerneedsconfirm Reported by|pgru
------- Additional comments from [email protected] Wed Oct 7 06:27:54 +0000 2009 ------- I was trying to send a serial letter and Open Office does not wait for the server response and sends "mail from", then the server closes the connection because OO does not perform accordingly to RFC. Please see below the correct CRAM-MD5 Authentification Log: T 86.59.10.180:54756 -> 89.207.144.23:25 [A] ..):(. -> openoffice verbindet sich zum Server T 89.207.144.23:25 -> 86.59.10.180:54756 [AP] 220 p0006.netstorage.at ESMTP.. <- Server antwortet T 86.59.10.180:54756 -> 89.207.144.23:25 [AP] ehlo if-PC.xip.at.. -> openoffice melde sich T 89.207.144.23:25 -> 86.59.10.180:54756 [AP] 250-p0006.netstorage.at.. <- Server antwortet T 86.59.10.180:54756 -> 89.207.144.23:25 [A] ....z. -> openoffice T 89.207.144.23:25 -> 86.59.10.180:54756 [AP] 250-AUTH=LOGIN CRAM-MD5 PLAIN..250-AUTH LOGIN CRAM-MD5 PLAIN..250-STARTTLS..250-PIPELINING..250 8BITMIME.. <- Server schlaegt Authentifizierungsvarianten vor T 86.59.10.180:54756 -> 89.207.144.23:25 [AP] AUTH CRAM-MD5.. -> openoffice waehlt CRAM-MD5 T 89.207.144.23:25 -> 86.59.10.180:54756 [AP] 334 PDMyNDMuMTI1NDg0MTE2NkBwMDAwNi5uZXRzdG9yYWdlLmF0Pg==.. <- Server sendet Key T 86.59.10.180:54756 -> 89.207.144.23:25 [A] ...db. -> openoffice sollte auf den Key antworten und das Server-OK abwarteten. T 86.59.10.180:54756 -> 89.207.144.23:25 [AP] mail FROM:<[email protected]>.. -> openoffice wartet nicht die Serverantwort ab und sendet "mail From" T 89.207.144.23:25 -> 86.59.10.180:54756 [AP] 535 malformed input.. <- Server schliesst die Verbindung da openoffice sich nicht RFC konform verhaelt. So sollte eine korrekte CRAM-MD5 Authentifizierung aussehen: Server: 220 mail.zeitform.de ESMTP Client: EHLO my.host.com Server: 250-mail.zeitform.de 250-AUTH LOGIN CRAM-MD5 PLAIN 250-AUTH=LOGIN CRAM-MD5 PLAIN 250-PIPELINING 250 8BITMIME Client: AUTH CRAM-MD5 Server: 334 PDQwMzYuMTA3NjMyNDM4MUBndWlsZGVuc3Rlcm4uemVpdGZvcm0uZGU+ Client: YmVudXR6ZXJAemVpdGZvcm0uZGUgMmQ5MzczZGZkOTFlMmU2NjMxYzhlMWFkNjk4MzRmYWQ= Server: 235 ok, go ahead (#2.0.0) Sie koennen hier diesen Bug bei openoffice reporten: http://www.openoffice.org/project/qa/issue_handling/pre_submission.html T 86.59.10.180:54756 -> 89.207.144.23:25 [AP] rset.. # T 89.207.144.23:25 -> 86.59.10.180:54756 [AP] 250 flushed.. # T 86.59.10.180:54756 -> 89.207.144.23:25 [A] ...... --------------------------------------------------------------------- Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/project_issues.html#notification --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
