Hi All.

It would be nice to have a possibility to define multiple inbound directories which were all searhed for inbound mail.

Currently I have created this functionality by playing with env vars.

How about it? :)

'Tommi


---
* Origin: nntps://news.fidonet.fi (2:221/6)

Hello Tommi!

24 Oct 21, Tommi Koivula wrote to All:

It would be nice to have a possibility to define multiple inbound directories which were all searhed for inbound mail.

How about it? :)

Instead of increasing the complexity you should increase the basic compatibility first. For example, setting a common msgid. This could have avoid the four same messages.

The next problem is that your mails got the same path but different seen-bys.

Please do us a favor, when you're testing something please be so kind and use a dedicated test echoarea.

Regards

Kai

--- GoldED+/LNX 1.1.4.7
* Origin: Monobox (2:240/77)

Hi Kai.

24 Oct 21 23:55:40, you wrote to me:

@TID: hpt/lnx 1.4.0-sta 09-04-05

Instead of increasing the complexity you should increase the basic compatibility first. For example, setting a common msgid.
This could have avoid the four same messages.

The next problem is that your mails got the same path but different seen-bys.

Please do us a favor, when you're testing something please be so kind and use a dedicated test echoarea.

Why don't you do a favour to yourself and update your outdated hpt to a version that can detect dupes also of messages that have no MSGID.

'Tommi

---
* Origin: rbb.fidonet.fi (2:221/360)

Hello Tommi!

25 Oct 21, Tommi Koivula wrote to Kai Richter:

@TID: hpt/lnx 1.4.0-sta 09-04-05

Instead of increasing the complexity you should increase the
basic compatibility first. For example, setting a common
msgid. This could have avoid the four same messages.

The next problem is that your mails got the same path but
different seen-bys.

Please do us a favor, when you're testing something please be so
kind and use a dedicated test echoarea.

Why don't you do a favour to yourself and update your outdated hpt to
a version that can detect dupes also of messages that have no MSGID.

Because the update failed and the upgrade would require far more complex migration, which had already started and is in ongoing progress. The migrated site won't be interacting with the real ftn until the migration is fully completed. In other words: Doing is far more complex than not doing.

And as you may noticed i didn't complain about the dupes. I'm still not sure if those mails met the definition of dupes. Because the path is the same there should be the same seen-bys too. But there aren't. It looks like something is really broken in your tosser and before worst things happen it would be a good idea to seperate the production and development environment like a pro.

Regards

Kai

--- GoldED+/LNX 1.1.4.7
* Origin: Monobox (2:240/77)