On Fri, 5 Dec 2025, Tom Hendrikx via Postfix-users wrote:
Date: Fri, 5 Dec 2025 01:01:54 +0100
From: Tom Hendrikx via Postfix-users <[email protected]>
Reply-To: Tom Hendrikx <[email protected]>
To: [email protected]
Subject: [pfx] Re: Postfix with mysql dspam and procmail
On 12/5/25 00:42, Viktor Dukhovni via Postfix-users wrote:
On Thu, Dec 04, 2025 at 05:44:57PM -0500, Al via Postfix-users wrote:
Can't help you with "uid"s, unclear why that'd either be known to
Postfix or useful. Only the Postfix local(8) and virtual(8) and
delivery agents deal with "uid"s, in every other context Postfix
deals with email addresses, which are resolved to "uids" only when
running as a user to deliver to user-owned files.
Dec 4 17:17:51 mail dspam[85005]: query error: Column 'uid' cannot be
null:
see sql.errors for more details
That's a dspam internal issue, not related to Postfix.
The uid column in the original DSPAM db definition is an auto-increment
primary key. Inserting a new username should create a new uid value
automatically. It has no relation to the unix user uid.
This is true. After getting to work it is assigning its own uid, so it is
not using the system uid, or the virtual user uid. It is creating
different profiles for different users, so it creates it once and then
uses it afterward.
I'm sure I don't need to mention that DSPAM is pretty ancient, unmaintained
and unsupported, but I do it anyway.
This is true. I feel the same about procmail, but I still have not found a
replacement for it.
Kind Regards,
Al
_______________________________________________
Postfix-users mailing list -- [email protected]
To unsubscribe send an email to [email protected]
