Let me know if this one has any password lurking inside.
Let me know if this one has any password lurking inside.
Still came through as bad:
+ Jan 11 21:20:59 Process: Importing EchoMail
+ Jan 11 21:20:59 Waiting for BUSY nodes
+ Jan 11 21:20:59 Importing 11212059.PKT (2:221/1.58 to 618:500/23)
! Jan 11 21:20:59 No echomail node configured for 2:221/1.58
! Jan 11 21:20:59 Moving /home/pi/mystic/echomail/in/unsecure/11212059.PK T to /home/pi/mystic/echomail/bad/11212059.PKT + Jan 11 21:20:59 Results: 0 echo, 0 net, 0 dupes, 0 tossed in 0.10s
So the difference to my netmail was that my .pkt did not contain
password.
I'll send you one more crashmail, with pkt.password 12345678.
So the difference to my netmail was that my .pkt did not contain
password.
I'll send you one more crashmail, with pkt.password 12345678.
Bingo! This one failed:
+ Jan 12 10:24:21 Process: Importing EchoMail
+ Jan 12 10:24:21 Waiting for BUSY nodes
+ Jan 12 10:24:21 Importing 12172411.PKT (2:221/1.2 to 1:229/664)
! Jan 12 10:24:21 No echomail node configured for 2:221/1.2
! Jan 12 10:24:21 Moving /home/pi/mystic/echomail/in/unsecure/12172411.PKT to
/home/pi/mystic/echomail/bad/12172411.PKT + Jan 12 10:24:21 Results: 0 echo, 0 net, 0 dupes, 0 tossed
in 0.09s
So the difference to my netmail was that my .pkt did not contain
password.
I'll send you one more crashmail, with pkt.password 12345678.
Bingo! This one failed:
So it seems that Mystic doesn't like .pkt's with password in unsecure inbound. It is not necessarily a bad thing. :)
Sysop: | altere |
---|---|
Location: | Houston, TX |
Users: | 66 |
Nodes: | 4 (0 / 4) |
Uptime: | 15:47:23 |
Calls: | 718 |
Files: | 7,654 |
Messages: | 293,894 |