bridge - irrecoverable error processing message #1135
Description
Dear Justin.
I tried to submit this possible bug via the mailing list but the captcha kept preventing me from 2x opting I apologize in advance if this duplicates that.
I have a discussion list configured to use Bridge to pick messages up from a POP3 box. A subscriber/member sent two messages: a short 4-sentence paragraph with a link, following message composed of 7 or so paragraphs with 8 or so URLs therein regarding sources looking for contributors.
The first, short message went through fine and went to archive as usual. The longer second message disappeared. Upon tailing postfix, syslog, and dada error log I found an error message:
Mailing List: YorkTalk (yorktalk)
- Connecting with Net::POP3 v3.14
- Connecting to POP3 host:'172.16.xxx.x1' on port:'995'
- Dovecot (Ubuntu) ready.
Capabilities:
PIPELINING:
CAPA:
SASL: PLAIN LOGIN
USER:
RESP-CODES:
UIDL:
AUTH-RESP-CODE:
TOP:
APOP may NOT be supported.
SSL Supported
Authentication via POP.
POP3 Login succeeded!
Message count: 1
Message Size: 7.62K
Received message is below maximum size allowed.
Received message is below maximum soft size allowed.
* Message Size is below both Soft and Hard Max Sizes.
- Checking Recipient: postmaster@mailings.york.cuny.edu
* From List Owner: No.
* Discussion List Support is enabled.
* Moderation disabled.
* From Subscriber: No.
* Authorized Senders is enabled.
* From Authorized Sender: Yes.
* SpamAssassin check is enabled.
* Looking for embedding SpamAssassin Headers...
* Message passed! Spam Test (Score of: , 6 needed.)
bridge - irrecoverable error processing message. Skipping message: parse_data: unable to open in-memory file handle at plugins/bridge line 2545.
Sending a copy of the message to the List Owner
- Removing message from server:
* Disconnecting from POP3 server
Processing Digests:
Mailing List: YorkTalk (yorktalk)
* Digests are not enabled for, yorktalk
Line 2545 in the bridge app is not very helpful as it points to various variables etc. I've tried switching from parsing messages on disk in .dada_files and using RAM and /tmp folder. Neither adjustment of those settings resulted in any positive change, either remediating the parsing problem and or sending the message out to the list.
I've included some output that I think may be useful mail-sample.txt
Any thoughts or suggestions would be greatly appreciated.
In health,
-est2