Hi Konstantin,
Thanks for your quick help. I have grepped /var/log/mail* for
4000000054195dd1009690ec0009f80c20ad, and it only displays my test message.
Also I'd expect the the message id to be assigned automatically, and
thus 'automatically' be unique..?
If I enter '4000000054195dd1009690ec0009f80c20ad' as a search term in
piler, it gives no results.
MJ
On 9/17/2014 13:07, Konstantin wrote:
Check message id.
If a message with the same message_id has been sent before - piler will
mark it as duplicate and discard.
2014-09-17 13:20 GMT+03:00 heupink <[email protected]
<mailto:[email protected]>>:
Hi Janos, hi others,
I've just updated to piler-1.1.0 and now I'm just testing to make
sure everything still works. So: trying to submit a test message to
piler, using:
telnet my.piler.host 25
After the smtp conversation, I see:
250 Ok 4000000054195dd1009690ec0009f8__0c20ad <>
I'm using a unique from-address, and unique message data, but the
message never ends up in the archive:
root@piler:/var/log# cat syslog | grep 20ad
Sep 17 12:10:03 piler piler[2693]:
4000000054195dd1009690ec0009f8__0c20ad: discarding: duplicate
message, id: 6074, message-id: null
Sep 17 12:10:03 piler piler[2693]:
4000000054195dd1009690ec0009f8__0c20ad: from=, size=79/0,
attachments=0, reference=, message-id=null, retention=0,
delay=52.64, delays=52.64/0.00/0.00/0.00/0.__00/0.00, status=duplicate
root@piler:/var/log#
Why would piler think the message is a duplicate? When searching the
piler archive for the "FROM" or message content, I'm getting no
results at all.
I'm seeing other messages with status=stored, so the updated piler
is accepting and storing mails. Is telnet submitted mail perhaps
treated differently somehow..?
Regards,
Mourik Jan
--
*This message was delivered using 100% recycledelectrons***.
