upgrade amavis-new makes havp stop working

[Dieter]

Instellen van amavisd-new (1:2.5.3-1ubuntu3)
creating/updating amavis user account
Starting amavisd: head: cannot open '/etc/mailname' to read. File or directory does not exist.
The value of variable $myhostname is "hannah-desktop", but should have been a fully qualified domain name; perhaps uname(3) did not provide such.
You must explicitly assign a FQDN of this host to variable $myhostname in /etc/amavis/conf.d/05-node_id, or fix what uname(3) provides as a host's networkname! (failed)
invoke-rc.d: initscript amavis, action "start" failed
WARNING: Starting amavis-new failed. Please check your configuration.

That is what i got from the update. And after that the virus-proxy havp did'nt work anymore.
And i don't understand what variable should come into $myhostname, my internetprovider in Hungary or my mailprovider in Holland.

Ubuntu 8.04 (hardy)
Gnome 2.22.3 (Ubuntu 2008-07-09)
Kernel 2.6.24-24-generic (#1 SMP Wed Apr 15 15:54:25 UTC 2009)
GCC version 4.2.4 (i486-linux-gnu)
Hostname hannah-desktop

The version of amavis is, as you can see above, 1:2.5.3-1ubuntu3
Nearly everything from clamav is installed.

I don't know what information to provide more.
So kind regards, Dieter Zoomers.

[Fabio Marconi (fabiomarconi)]

Thank you for taking the time to report this bug and helping to make Ubuntu better.
Is this bug reproducible with the latest Lucid packages ?
Thanks in advance.

[Fabio Marconi (fabiomarconi)]

 Thank you for taking the time to report this bug and helping to make Ubuntu better. This bug did not have a package associated with it, which is important for ensuring that it gets looked at by the proper developers. You can learn more about finding the right package at https://wiki.ubuntu.com/Bugs/FindRightPackage .

When reporting bugs in the future please use apport by using 'ubuntu-bug' and the name of the package affected. You can learn more about this functionality at https://help.ubuntu.com/community/ReportingBugs.

[Fabio Marconi (fabiomarconi)]

We'd like to figure out what's causing this bug for you, but we haven't heard back from you in a while. Could you please provide the requested information? Thanks!

[Fabio Marconi (fabiomarconi)]

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!