when you telnet , any idea what message id has been given to the email ? I do see a possible flaw with piler because there is no guarantee that message Id's will be unique across multiple email servers.
For example we have 10 email servers, one could assume as some point there will be Atleast 1 message id that is ignored or overwritten even when the mails are unique Sent from my iPhone > On 17 Sep 2014, at 1:07 PM, Konstantin <[email protected]> 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]>: >> 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 4000000054195dd1009690ec0009f80c20ad <> >> >> 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]: 4000000054195dd1009690ec0009f80c20ad: >> discarding: duplicate message, id: 6074, message-id: null >> Sep 17 12:10:03 piler piler[2693]: 4000000054195dd1009690ec0009f80c20ad: >> 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% recycled electrons.
