#43 Netmail packages not tossed to designated areas, remain in var/inbound/ - affects all versions >= 1.0.7.22
After updating my setup from version 1.0.7.21 to 1.0.7.24 (and also when updating from 1.0.7.21 to 1.0.8) I noticed that Netmail packages are no longer being tossed to their designated areas.
I tested further and it seems that beginning with version 1.0.7.22, netmail packages are being tossed to their designated Areas anymore. echomail packages will be tossed to their designated areas just fine, but all netmail packages remain in the var/inbound/ directory.
I've tried allowing Aliases and Private/Public messages in mbsetup for the Netmail areas, but this didn't fix the problem.
This is just affecting incoming messages, I can send out messages and these arrive at their destination without problem.
Switching back to a version < 1.0.7.22 works fine and all Net- and echomails
are being tossed to their designated areas without problem.
I am under the impression that beginning with 1.0.7.22 there are some serious
problems with mbfido and the problem I am facing can be reproduced up to the current version 1.0.8
I have had a similar experience BUT it was related to running more than one instance of golded at the same time.
After all had been closed and waiting a few minutes, all packets were tossed etc.
Suggest you check your logs (system.log and error.log ) to see what was happening (or not) at the time, just in case you have similar possible reasons.
I feel a bit sheepish now, since I fell "victim" to a change in mbsetup / mbfido that was introduced with version 1.0.7.22 - it's the mbsebbs menu option 1.11.21 (Unp. .PKTs) and the new mbfido option "-unp" that are required to be set / to be used to have mbfido behave like it did with previous (< 1.0.7.22) versions. I must admit that I missed out on that change, so I blamed mbfido when in fact I was the dummy here.
So eventually this ticket can be closed with "not a bug" and I wish to apologize for any confusion this may have caused.
Last edit: lodger 2022-07-21
There are issues with that option, so I recommend that you do NOT enable it at this time. I have fixed the problem you reported in v1.0.8.1; there will be another version soon that should allow the 1.11.21 option to be safely enabled again.
This should be fixed in v1.0.8.1.
Yes, I read that in the commit log but I encounter problems with 1.0.8.1 when editing Echomail Groups: setting Max Msgs. and Days Old will cause an error message telling me the setup is unable to write to "mareas.data" and an additional "mareas.temp" file is then left behind in etc/ - I can open a new ticket for that 1.0.8.1 issue if you like?
The netmail not tossing issue has been fixed in v1.0.8.2, and you may enable the automatic tossing of .PKTs from the unprotected inbound (1.11.21) if you desire.
The mareas.data/mareas.temp issue is a known problem; Mike has temporarily disabled the duplicate message area checking feature until he gets this bug squashed.