Jump to:
| Project: | Mailhandler |
| Version: | 6.x-1.8 |
| Component: | Miscellaneous |
| Category: | support request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | closed (fixed) |
Issue Summary
Hello,
We have created a forum that is being fed content by mailhandler. The content is automatically generated by another application that adds a converted timestamp to the end of the email subject.
The emails subjects are similar to the following, with different dates and times:
LogRhythm Reports: S - SMF, 09/23/09 09:00 AM to 09/25/09 09:04 AM GMT -05:00 (Past 48 Hours)
Subsequent emails added to the forum are added as comments to the first forum topic, when they should be added to the forum as new topics. All of these emails differ only in dates and times.
Additionally, the titles for the created comments are clipped versions of the original email subjects. For example:
LogRhythm Reports: S - SMF, 09/23/09 09:00 AM to 09/25/09 09:06 AM GMT -05:00 (Past 48 Hours)
becomes
LogRhythm Reports: S - SMF, 09/23/09 09:00 AM to 09/25/09 09:06
The mailhandler commands we are using for that particular mailbox are as follows:
tid: 349
status: 1
Am I doing something wrong here, or is this truly a bug?
Any help would be greatly appreciated.
Thank you,
-Matthew C Moss-
Comments
#1
Does anyone know of a way to force Mailhandler to retrieve all mailbox content as newly created nodes and not comments?
That would solve my problem to a degree.
Thank you,
-Matthew C Moss-
#2
Try the following:
taxonomy: [Support Forum]status: 1
type: forum
where "Support Forum" is the name of the forum into which the incoming post should go.
#3
Is it possible you also installed listhandler, if so uninstall listhandler and try again,
Did this solution work for you? If so plz. close the bug.
If not let us know what was the result and where it went still wrong.
#4
@matt.moss, do you still experience the issue and did you investigate as stated above? If so it would be great if you could let us know your outcome and close this issue.
#5
No reply, going to assume this is fixed.
#6
Automatically closed -- issue fixed for 2 weeks with no activity.