I'm connecting fine and receiving posts when made manually, but when I try to receive mails sent from the listserv mails are rejected with the message "The e-mail address 'example@example.net' may not create story items." I have "Sender" in the "From header:" field and I have checked that the email header for "Sender" corresponds to the email address of a user with permissions to post stories.
If I check the logs it seems that the "From header:" command isn't having any effect, and it is using the "From:" field instead.
Any help or suggestions would be appreciated.
Cheers, Ben.
| Comment | File | Size | Author |
|---|---|---|---|
| #9 | parenth5x.patch | 817 bytes | marcp |
| #8 | parenth.patch | 843 bytes | z.stolar |
| #5 | mailhandler.diff | 544 bytes | cbguder |
Comments
Comment #1
grub commentedThis seems to be a problem with mailman, I've tried with other mailing lists and all is working as it should. Mailman seems to append '-bounces' to the Sender field, perhaps that is what is causing the problem. If anybody knows how to make a mailman listserv compatible with mailhandler, or a possible workaround, that'd be great.
Comment #2
grub commentedI changed the From header: field to "X-BeenThere" and everything works as it should. The X-BeenThere header references the mailing list 'example@example.net' while the drupal user account must have the email 'example-bounces@example.net' for this to work.
Comment #3
moshe weitzman commentedComment #4
Anonymous (not verified) commentedAutomatically closed -- issue fixed for two weeks with no activity.
Comment #5
cbguder commentedThis bug still exists in 1.5.
The attached patch fixes it.
Comment #6
marcp commentedThis same issue exists in 5.x-1.4. Manually applying the patch above fixes the problem there, too. In 5.x-1.4 the fix needs to happen on line 432.
Comment #7
marcp commentedLooking at the code again, you shouldn't need to break the thing up into the assignment and if statements. The code currently says:
It needs some more parentheses:
Comment #8
z.stolar commentedPlease test the attached patch. If there are no errors, I'll commit it.
Comment #9
marcp commentedI'm using 5.x -- here is a patch that works.
Comment #10
z.stolar commentedCommitted.
Comment #12
marcp commentedThanks for committing to 5.x. The most recent 5.x release is over 4 months old. Does the bug fix in this issue qualify for an official 5.x-1.5 release?
Comment #13
mr.j commentedI just came to post a patch for this bug on 5.x too - a 1.5 release would be good.