Olaf,
With some friendly help and prodding from Steve Langeseck, I
recognized some logic errors in the postinst script. Frankly, I am
surprised no one ran into it earlier. Here's what I surmise was
happening.
1. You had installed clamsmtp in the past.
2. You had removed the package with the --purge flag at some point.
this removed the clamav user from the clamsmtp group. (NOTE:
clamsmtp user and group had not been removed by the --purge.)
3. When you re-installed the package, the postinst script tested for
the existence of the clamsmtp user and group. If it found them,
it assumed that everything was fine and moved on to the fixperms
portion of the script. This skipped the routines to add clamav
to the clamsmtp group, adding clamsmtp to the aliases file, and
"fixing" the config file.
I've uploaded a new package that doesn't have these flaws. You do not
need to re-install the package, as it sounds like you've worked out
the bugs with your current installation.
I'm not sure why you needed to specify the 127.0.0.1:10025 address in
the OutAddress configuration directive. It could be an issue with
ipv4 v.s. ipv6. Though, I'm not sure that's something I can handle in
a postinst script. It would be possible to change the template
config file to include it, however.
If you could do some more testing on your platform to confirm this, I
would appreciate it. As it doesn't relate to this bug, per se, you
could open a new bug report.
I know that reportbug isn't a required tool, but it does include some
very helpful information regarding your installed environment,
including architecture, debconf settings, and package dependencies. I
would urge you to consider using it.
Thanks!
--
Chad Walstrom <[EMAIL PROTECTED]> http://www.wookimus.net/
assert(expired(knowledge)); /* core dump */
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
