Hello Adrian!
Just ideas while working on/with this script.
1-
Why should incoming.pl always connect when there are alternative methods to reduce mysql connections.
For e.g. if user exists on the harddisk/data/users only then a mysql query could be a possible logic! Understand, what I mean? Or is this taking longer than connection.
Hence the line 483 of incoming.pl is not necessary at all!!!
If not, simply bounce with the help of line 586 of incoming.pl and directly DELE that message fom the box. Why decode, boundry, parse???
2-
Can it not first get a list of bounce + spam filters and parse the emails in the mailbox. They need to be deleted anyway.
Just ideas while working on/with this script.
1-
Why should incoming.pl always connect when there are alternative methods to reduce mysql connections.
For e.g. if user exists on the harddisk/data/users only then a mysql query could be a possible logic! Understand, what I mean? Or is this taking longer than connection.
Hence the line 483 of incoming.pl is not necessary at all!!!
If not, simply bounce with the help of line 586 of incoming.pl and directly DELE that message fom the box. Why decode, boundry, parse???
2-
Can it not first get a list of bounce + spam filters and parse the emails in the mailbox. They need to be deleted anyway.