When writing emails to multiple bcc: recipient, the email does not get sent. It just sticks in the outgoing mail folder. No error message. When doing a manual send (right-click, sent mail), nothing happens. When adding another message with a single recipient, it gets sent, the one with multipel recipients not. When doing a "sent later" and setting the message to be sent, say, after five minutes, it works... Reproducible: Always
Actually, "send later" does not work either. It looks like it's sent, but nobody gets it... Nor error message
Do you have error info in console or log ?
I'll send out an email later this week and will see what outputs there are in console. Where would the kmail (or akonadi, if the problem's there) be?
sorry, I meant kmail logs... ;-)
O.k., tried again. Sending didn't work. No error messages on console. Akonadi Mail Dispatcher does not even see any mail. "Sending later" did work partially, akonadi mail dispatcher saw and did send the mail, but only the "to" recipient got it, all bcc recipients did not get anything. Again, no errror messages in console. Console output: (but I switched folders and ran the antivirus assistand to see whether that would change anything, which it didn't..): PROMPT:~$ kontact QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave. QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave. Hspell: can't open /usr/share/hspell/hebrew.wgz.sizes. kontact(20752) KDirWatch::removeDir: doesn't know "/home/martin/.kde/share/apps/messageviewer/themes/" kontact(20752) KDirWatch::removeDir: doesn't know "/usr/share/kde4/apps/messageviewer/themes/" martin@martin-W65-67SZ:~$ Bus::open: Can not get ibus-daemon's address. IBusInputContext::createInputContext: no connection to ibus-daemon error: line 1: missing or bad word count in the dic file Hash Manager Error : 4 X Error: BadWindow (invalid Window parameter) 3 Major opcode: 20 (X_GetProperty) Resource id: 0x7000122 error: line 1: missing or bad word count in the dic file Hash Manager Error : 4 X Error: BadWindow (invalid Window parameter) 3 Major opcode: 20 (X_GetProperty) Resource id: 0x7000144 error: line 1: missing or bad word count in the dic file Hash Manager Error : 4 kontact(20752)/libakonadi Akonadi::ProtocolHelper::parseItemFetchResult: Failed to open attribute file: "57067_r0" kontact(20752)/libakonadi Akonadi::ProtocolHelper::parseItemFetchResult: Failed to open attribute file: "57067_r0" mCurrentItem.parentCollection() Collection ID: 141 remote ID: "outbox" name: "" url: KUrl("akonadi://?collection=141") parent: 4 "/home/martin/.local/share/local-mail" resource: "" rights: QFlags(0x1|0x2|0x4|0x8|0x10|0x20) contents mime type: () isVirtual: false CachePolicy: inherit: true interval: -1 timeout: -1 sync on demand: false local parts: () CollectionStatistics: count: -1 unread count: -1 size: -1 kontact(20752)/libakonadi Akonadi::ProtocolHelper::parseItemFetchResult: Failed to open attribute file: "57067_r0" ClamAV 0.98.1/19085/Wed Jun 11 08:30:32 2014 /bin/sh: 1: sweep: not found /bin/sh: 1: f-prot: not found /bin/sh: 1: antivir: not found X Error: BadWindow (invalid Window parameter) 3 Major opcode: 20 (X_GetProperty) Resource id: 0x70001ea X Error: BadWindow (invalid Window parameter) 3 Major opcode: 20 (X_GetProperty) Resource id: 0x7000200 ClamAV 0.98.1/19085/Wed Jun 11 08:30:32 2014 /bin/sh: 1: sweep: not found /bin/sh: 1: f-prot: not found /bin/sh: 1: antivir: not found X Error: BadWindow (invalid Window parameter) 3 Major opcode: 20 (X_GetProperty) Resource id: 0x7000213 X Error: BadWindow (invalid Window parameter) 3 Major opcode: 20 (X_GetProperty) Resource id: 0x7000220 QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave. QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave. X Error: BadWindow (invalid Window parameter) 3 Major opcode: 20 (X_GetProperty) Resource id: 0x700026f X Error: BadWindow (invalid Window parameter) 3 Major opcode: 20 (X_GetProperty) Resource id: 0x70001c9 kontact(20752)/libakonadi Akonadi::ProtocolHelper::parseItemFetchResult: Failed to open attribute file: "57097_r0" kontact(20752)/libakonadi Akonadi::ProtocolHelper::parseItemFetchResult: Failed to open attribute file: "57097_r0" mCurrentItem.parentCollection() Collection ID: 141 remote ID: "outbox" name: "outbox" url: KUrl("akonadi://?collection=141") parent: 4 "/home/martin/.local/share/local-mail" resource: "akonadi_maildir_resource_0" rights: QFlags(0x1|0x2|0x4|0x8|0x10|0x20) contents mime type: ("message/rfc822", "inode/directory") isVirtual: false CachePolicy: inherit: true interval: -1 timeout: 1 sync on demand: true local parts: ("ENVELOPE") CollectionStatistics: count: 1 unread count: 1 size: 21024 kontact(20752)/libakonadi Akonadi::ProtocolHelper::parseItemFetchResult: Failed to open attribute file: "57097_r0" X Error: BadWindow (invalid Window parameter) 3 Major opcode: 20 (X_GetProperty) Resource id: 0x700031d
I enabled debug in akonadi before sending, and this is the output: 97 UID FETCH 24259 ALLATTR EXTERNALPAYLOAD (UID COLLECTIONID FLAGS SIZE REMOTEID REMOTEREVISION DATETIME) * 24259 FETCH (UID 24259 REV 0 REMOTEID "" MIMETYPE "message/rfc822" COLLECTIONID 141 SIZE 31997 DATETIME "20-Jun-2014 14:34:29 +0000" FLAGS ($QUEUED) ATR:AddressAttribute [FILE] {8} 58209_r0 ATR:DispatchModeAttribute {11} immediately ATR:SentActionAttribute {4} 97 OK UID FETCH completed 98 UID FETCH 24259 ALLATTR EXTERNALPAYLOAD (UID COLLECTIONID FLAGS SIZE REMOTEID REMOTEREVISION DATETIME) * 24259 FETCH (UID 24259 REV 1 REMOTEID "1403274869.R911.martin-W65-67SZ" MIMETYPE "message/rfc822" COLLECTIONID 141 SIZE 31997 DATETIME "20-Jun-2014 14:34:29 +0000" FLAGS ($QUEUED) ATR:AddressAttribute [FILE] {8} 58209_r0 ATR:DispatchModeAttribute {11} immediately ATR:SentActionAttribute {4} 98 OK UID FETCH completed 99 STATUS 141 (MESSAGES UNSEEN SIZE) * STATUS "Lokale Ordner/outbox" (MESSAGES 1 UNSEEN 1 SIZE 31997) 99 OK STATUS completed 100 LSUB 141 0 () () * 141 4 (NAME "outbox" MIMETYPE (message/rfc822 inode/directory) REMOTEID "outbox" REMOTEREVISION "1403274815000" RESOURCE "akonadi_maildir_resource_0" VIRTUAL 0 CACHEPOLICY (INHERIT true INTERVAL -1 CACHETIMEOUT 1 SYNCONDEMAND true LOCALPARTS (ENVELOPE)) SpecialCollectionAttribute "outbox" ENTITYDISPLAY "(\"Postausgang\" \"mail-folder-outbox\" \"\" ())") 100 OK List completed 101 UID FETCH 24259 ALLATTR EXTERNALPAYLOAD (UID COLLECTIONID FLAGS SIZE REMOTEID REMOTEREVISION DATETIME) * 24259 FETCH (UID 24259 REV 2 REMOTEID "1403274869.R911.martin-W65-67SZ" MIMETYPE "message/rfc822" COLLECTIONID 141 SIZE 21026 DATETIME "20-Jun-2014 14:34:30 +0000" FLAGS ($QUEUED) ATR:AddressAttribute [FILE] {8} 58209_r0 ATR:DispatchModeAttribute {11} immediately ATR:SentActionAttribute {4} 101 OK UID FETCH completed 102 STATUS 141 (MESSAGES UNSEEN SIZE) * STATUS "Lokale Ordner/outbox" (MESSAGES 1 UNSEEN 1 SIZE 21026) 102 OK STATUS completed 103 LSUB 141 0 () () * 141 4 (NAME "outbox" MIMETYPE (message/rfc822 inode/directory) REMOTEID "outbox" REMOTEREVISION "1403274869000" RESOURCE "akonadi_maildir_resource_0" VIRTUAL 0 CACHEPOLICY (INHERIT true INTERVAL -1 CACHETIMEOUT 1 SYNCONDEMAND true LOCALPARTS (ENVELOPE)) SpecialCollectionAttribute "outbox" ENTITYDISPLAY "(\"Postausgang\" \"mail-folder-outbox\" \"\" ())") 103 OK List completed
It's still there in 4.13.3. Is there any way I could check, how this bug is triggered? Things I tried so far: reducing the bcc addresses to below 150 checking all email addresses (removing " and , in descriptive names) anything else I could try?
Still there in 4.14.1. I switched to google in the meantime, but it's still the same. I can save the mail as draft and then send it from within google, but it is suboptimal.
150 Bcc ?:) I don't have 150 address :) How do you want that I test it ?:)
I actually send this mail to over 300 people in bcc... ;-) If you can get me an idea how to test it, I send this stuff about once a week or every other week, so it's kind of a repeatable exercise... I could send you the email with the adresses offline so you could check whether there's something wrong with the adresses, although I doubt it (I checked it before twice and actually did find and resolve some problems, but it didn't help).
I actuall did test it with only about 50 bcc with the same result.
Actually I came across a restriction on the google server we are using: you cannot send emails to more than 100 recipients at once from an email client. You need to do that from the web interface. Don't know whether that is related to the problem, but it somehow fixes it as I can't use kmail anyway anymore for these emails...
This bug has never been confirmed for a KDE PIM version that is based on KDE Frameworks (5.x). Those versions differ significantly from the old 4.x series. Therefore, I plan to close it in around two or three months. In the meantime, it is set to WAITINGFORINFO to give reporters the oportunity to check if it is still valid. As soon as someone confirms it for a recent version (at least 5.1, ideally even more recent), I'll gladly reopen it. Please understand that we lack the manpower to triage bugs reported for versions almost two years beyond their end of life.
Google restrictions still apply, but that's not kmails fault. Closing.