| Project: | Listhandler |
| Version: | 4.7.x-1.x-dev |
| Component: | Code |
| Category: | bug report |
| Priority: | normal |
| Assigned: | philipnet |
| Status: | closed (fixed) |
Issue Summary
I am attempting to post a large number of messages from a YahooGroups archive to my forums in several date-specific archive forums. When I retrieve a batch of messages, I get a number of errors all related to the way the module decides whether a posting is a comment to a pre-existing node:
Many messages do not get posted because apparently they are being posted to a closed node:
Type error
Date Monday, 30 January, 2006 - 16:19
User Nuestros Ranchos
Location /?q=admin/mailhandler/retrieve/1
Message Comment: unauthorized comment submitted or comment submitted to a closed node Margarita'sRememberanceJerezZacatecas/SantaMariadeLosAngelesJalisco.
Severity notice
Hostname 4.21.128.2
All of my messages that are regarded as comments to a pre-existing node are given the date and time stamp of the time they are retrieved from the mail archive and not the time and date they were sent.
Messages that match the title (subject line) of nodes in other forums get posted to that forum rather than to the forum indicated in the instruction line by the taxonomy id "tid:"
Comments
#1
3) the title matching is a measure of last resort emplyoed by the module. usually it tried to use the specified forum. One can argue that it should match against titles from othe forums. Patches are welcome for this.
2) date parsing isn't implemented, sorry. Again: patches are welcome.
1) Closed nodes cannot have comments posted to them. Nothing listhandler can do about that. The nodes shouldn't be closed.
#2
>3) the title matching is a measure of last resort emplyoed by the module. usually it tried to use the specified forum. One can argue >that it should match against titles from othe forums. Patches are welcome for this.
This does not appear to be the case since I am specifically telling the module in the mailhandler configuration which topic id "tid" the messages should be sent to. Thus every message is sent with a forum designation explicitly... if it were using titles for matching only as last resort, it would never match a comment to a node from another forum.
>2) date parsing isn't implemented, sorry. Again: patches are welcome.
This does not appear to be the case since the first message with a given title which is converted into a node is assigned the date of the email time stamp. Only subsequent messages that are appended as comments to that pre-existing node are given the time stamp of the time of appendage rather than the time stamp of the message.
For an example, see:
http://www.nuestrosranchos.com/forum/27
You will note I uploaded each batch of messages at a specified time, so all messages that belong in the forum were uploaded 30 Jan 2006 ~ 3:58 PM. However, I did the next batch at 4:18 PM and there are a few of these messages mixed in there... and the next batch at 10:18 PM and there is one of those messages in there as well:
http://www.nuestrosranchos.com/node/12991
You will note that the node has a submitted time stamp of 14 March, 2005 - 9:24pm, which is when the message was sent and the appended comment has a time stamp of 30 January 2006 - 10:18 pm, which is when the batch of messages was uploaded.
>1) Closed nodes cannot have comments posted to them. Nothing listhandler can do about that. The nodes shouldn't be closed.
I agree that the nodes should not be closed. But it is the listhandler module that is creating the nodes and therefore the fact that they are closed is an inherent error in the module.
#3
This "closed node" error can happen if you delete imported posts and then re-import them. The problem is that the listhandler table keeps track of the old, deleted node numbers, and when the mail is re-imported, it tries to post them to non-existent nodes. The solution is to delete the relevant records in the listhandler table if you delete previously imported nodes.
#4
Oops, I changed the issue title by mistake. This post is just to change it back.
#5
That seems to have done the trick. I went into the MySQL panel and deleted all of the preexisting entries for messages and re-uploaded them and they uploaded fine with no closed node errors.
Perhaps this bug should be changed to implement a deletion of listhandler table entries for nodes that are deleted.
#6
I have now gotten the Yahoo!Groups messages importing OK... no more bounced nodes, etc.
I now have another issue... any message that is sent from the Forum gets posted multiple times.
My setup is:
1. Yahoo!Groups includes a subscriber that is the mailbox of one of the forums, which is specifically set up to receive postings on the Yahoo!Groups mailing list we are looking to replace (a transition period solution)...
2. Each of the other three forums has its own mailbox and its own mailing list set up via Mailman.
3. Each of the Mailman lists includes the Yahoo!Groups posting address as one of its members (also part of the transition period solution)
4. Each Mailman list includes the respective forum's mailbox as one of its members (so postings made via email can get distributed).
My problem is:
When something gets posted (from within Drupal) to one of the three new forums, it gets published on the site and gets sent out to the respective Mailman list. That list then sends a copy to Yahoo!Groups and back to the mailbox for the list. Yahoo!Groups then also sends back a copy to the mailbox for the fourth Yahoo!Groups forum. The message gets posted as a comment to the original posting and also as a new node in the Yahoo!Groups board.
Is there not a check that ensures that the same message does not get posted multiple times in an endless loop? It seems as though Yahoo!Groups and Mailman are killing the message the second time they get it but listhandler is not.
#7
Screenshot of listhandler table in MySQL
#8
#9
Since these are multiple issues in one report, I've tried to alter the status of this issue to the best possible here.
Fixed, see http://drupal.org/node/47170#comment-373899 and http://drupal.org/node/47170#comment-373901
This is Listhandler issue already solved
if ($node->sentbylisthandler) { // avoid running an infinite loop.This is a duplicate of #1000440: Mailhandler comment created and changed date and time stored incorrectly
#10
Automatically closed -- issue fixed for 2 weeks with no activity.
#11
Just go to admin - user management - permissions - and give a permission to post comments and administer comments