freebsd-ports/mail/vpopmail/pkg-plist

117 lines
5.1 KiB
Text
Raw Normal View History

@owner vpopmail
@group vchkpw
vpopmail/bin/authvchkpw
vpopmail/bin/clearopensmtp
2004-04-09 11:38:26 +02:00
vpopmail/bin/dotqmail2valias
vpopmail/bin/vaddaliasdomain
vpopmail/bin/vadddomain
vpopmail/bin/vadduser
vpopmail/bin/valias
vpopmail/bin/vchangepw
@(,,%%VCHKPW_MODE%%) vpopmail/bin/vchkpw
vpopmail/bin/vconvert
vpopmail/bin/vdeldomain
vpopmail/bin/vdelivermail
vpopmail/bin/vdeloldusers
vpopmail/bin/vdeluser
vpopmail/bin/vdominfo
2001-01-29 13:01:31 +01:00
vpopmail/bin/vipmap
vpopmail/bin/vkill
vpopmail/bin/vlist
vpopmail/bin/vmkpasswd
vpopmail/bin/vmoddomlimits
vpopmail/bin/vmoduser
vpopmail/bin/vpasswd
vpopmail/bin/vpopbull
vpopmail/bin/vpopmaild
vpopmail/bin/vsetuserquota
vpopmail/bin/vusagec
vpopmail/bin/vuserinfo
vpopmail/etc/inc_deps
vpopmail/etc/lib_deps
@exec if [ ! -f %D/vpopmail/etc/defaultdomain ]; then install -o vpopmail -g vchkpw /dev/null %D/vpopmail/etc/defaultdomain; fi
@unexec if [ -f %D/vpopmail/etc/defaultdomain ] && [ ! -s %D/vpopmail/etc/defaultdomain ]; then rm -f %D/vpopmail/etc/defaultdomain; fi
@unexec if cmp -s %D/vpopmail/etc/tcp.smtp %D/vpopmail/etc/tcp.smtp-dist; then rm -f %D/vpopmail/etc/tcp.smtp; fi
vpopmail/etc/tcp.smtp-dist
@exec if [ ! -f %D/vpopmail/etc/tcp.smtp ] ; then cp -p %D/%F %B/tcp.smtp; fi
@unexec if cmp -s %D/vpopmail/etc/vlimits.default %D/vpopmail/etc/vlimits.default-dist; then rm -f %D/vpopmail/etc/vlimits.default; fi
vpopmail/etc/vlimits.default-dist
@exec if [ ! -f %D/vpopmail/etc/vlimits.default ] ; then cp -p %D/%F %B/vlimits.default; fi
%%LDAP%%@unexec if cmp -s %D/vpopmail/etc/vpopmail.ldap %D/vpopmail/etc/vpopmail.ldap-dist; then rm -f %D/vpopmail/etc/vpopmail.ldap; fi
%%LDAP%%vpopmail/etc/vpopmail.ldap-dist
%%LDAP%%@exec if [ ! -f %D/vpopmail/etc/vpopmail.ldap ] ; then cp -p %D/%F %B/vpopmail.ldap; fi
%%LDAP%%@exec echo "You need to specify the LDAP connection settings in the %D/vpopmail/etc/vpopmail.ldap file" | /usr/bin/fmt
%%MYSQL%%@unexec if cmp -s %D/vpopmail/etc/vpopmail.mysql %D/vpopmail/etc/vpopmail.mysql-dist; then rm -f %D/vpopmail/etc/vpopmail.mysql; fi
%%MYSQL%%vpopmail/etc/vpopmail.mysql-dist
%%MYSQL%%@exec if [ ! -f %D/vpopmail/etc/vpopmail.mysql ] ; then cp -p %D/%F %B/vpopmail.mysql; fi
@unexec if cmp -s %D/vpopmail/etc/vusagec.conf %D/vpopmail/etc/vusagec.conf-dist; then rm -f %D/vpopmail/etc/vusagec.conf; fi
vpopmail/etc/vusagec.conf-dist
@exec if [ ! -f %D/vpopmail/etc/vusagec.conf ] ; then cp -p %D/%F %B/vusagec.conf; fi
@owner
@group
%%PORTDOCS%%vpopmail/doc/doc_html/vpopmail.html
%%PORTDOCS%%vpopmail/doc/doc_html/vpopmail5.abw
%%PORTDOCS%%vpopmail/doc/doc_html/vpopmailapi.png
%%PORTDOCS%%vpopmail/doc/man_html/clearopensmtp.html
%%PORTDOCS%%vpopmail/doc/man_html/index.html
%%PORTDOCS%%vpopmail/doc/man_html/vaddaliasdomain.html
%%PORTDOCS%%vpopmail/doc/man_html/vadddomain.html
%%PORTDOCS%%vpopmail/doc/man_html/vadduser.html
%%PORTDOCS%%vpopmail/doc/man_html/vchkpw.html
%%PORTDOCS%%vpopmail/doc/man_html/vconvert.html
%%PORTDOCS%%vpopmail/doc/man_html/vdeldomain.html
%%PORTDOCS%%vpopmail/doc/man_html/vdelivermail.html
%%PORTDOCS%%vpopmail/doc/man_html/vdeluser.html
%%PORTDOCS%%vpopmail/doc/man_html/vpasswd.html
%%PORTDOCS%%vpopmail/doc/man_html/vpopbull.html
%%PORTDOCS%%vpopmail/doc/man_html/vsetuserquota.html
%%PORTDOCS%%vpopmail/doc/README
Update vpopmail to 5.4.20 after a long delay, mostly due to wondering how to handle the database upgrade and the SpamAssassin patch partial integration. There are several important changes that may affect your vpopmail installation and may need you to handle manually: - THE MYSQL CONNECTION INFORMATION IS NO LONGER DEFINED AT COMPILE-TIME! The WITH_MYSQL_{USER,PASSWD,SERVER,DB} variables should NOT be defined when you build the port; place that information in the vpopmail.mysql file after vpopmail has been installed! - the default domain is also no longer defined at compile time - you need to place it in the defaultdomain file after the installation. - the defaultdomain and vpopmail.mysql files are no longer blindly removed on deinstallation, they are only removed if they have not been modified - in vpopmail 5.4.18, the database schema was changed - some fields were extended from 64 to 96 characters. If you do not apply those changes to your database, as explained in the vpopmail/doc/UPGRADE file, your vpopmail installation may silently fail or lose the trailing portions of domain names and usernames. - in vpopmail 5.4.19, the upstream authors integrated large parts of Alex Dupre's SpamAssassin support, without the SPAM_THRESHOLD part. If you use vpopmail along with the SpamAssassin FreeBSD port support, take extra care to ensure that your installation still processes e-mail messages in the same way. - vpopmail 5.4.19 added support for maildrop as a mail delivery agent. This is available in the FreeBSD port if WITH_MAILDROP is defined. There is also a new user-limit flag for maildrop delivery. - vpopmail 5.4.19 added support for MySQL connections via Unix sockets instead of TCP sockets to the server. To do that, change the second value (the port number) in vpopmail.mysql to the full pathname of the MySQL socket (e.g. /tmp/mysql.sock). - vpopmail 5.4.20 extended the LDAP support; please see README.ldap for more information, and specify the LDAP connection information in the vpopmail/etc/vpopmail.ldap file after the installation.
2007-10-09 15:27:24 +02:00
%%PORTDOCS%%vpopmail/doc/README.activedirectory
%%PORTDOCS%%vpopmail/doc/README.filelocking
%%PORTDOCS%%vpopmail/doc/README.ipaliasdomains
%%PORTDOCS%%vpopmail/doc/README.ldap
Update vpopmail to 5.4.20 after a long delay, mostly due to wondering how to handle the database upgrade and the SpamAssassin patch partial integration. There are several important changes that may affect your vpopmail installation and may need you to handle manually: - THE MYSQL CONNECTION INFORMATION IS NO LONGER DEFINED AT COMPILE-TIME! The WITH_MYSQL_{USER,PASSWD,SERVER,DB} variables should NOT be defined when you build the port; place that information in the vpopmail.mysql file after vpopmail has been installed! - the default domain is also no longer defined at compile time - you need to place it in the defaultdomain file after the installation. - the defaultdomain and vpopmail.mysql files are no longer blindly removed on deinstallation, they are only removed if they have not been modified - in vpopmail 5.4.18, the database schema was changed - some fields were extended from 64 to 96 characters. If you do not apply those changes to your database, as explained in the vpopmail/doc/UPGRADE file, your vpopmail installation may silently fail or lose the trailing portions of domain names and usernames. - in vpopmail 5.4.19, the upstream authors integrated large parts of Alex Dupre's SpamAssassin support, without the SPAM_THRESHOLD part. If you use vpopmail along with the SpamAssassin FreeBSD port support, take extra care to ensure that your installation still processes e-mail messages in the same way. - vpopmail 5.4.19 added support for maildrop as a mail delivery agent. This is available in the FreeBSD port if WITH_MAILDROP is defined. There is also a new user-limit flag for maildrop delivery. - vpopmail 5.4.19 added support for MySQL connections via Unix sockets instead of TCP sockets to the server. To do that, change the second value (the port number) in vpopmail.mysql to the full pathname of the MySQL socket (e.g. /tmp/mysql.sock). - vpopmail 5.4.20 extended the LDAP support; please see README.ldap for more information, and specify the LDAP connection information in the vpopmail/etc/vpopmail.ldap file after the installation.
2007-10-09 15:27:24 +02:00
%%PORTDOCS%%vpopmail/doc/README.maildrop
%%PORTDOCS%%vpopmail/doc/README.mysql
Update vpopmail to 5.4.20 after a long delay, mostly due to wondering how to handle the database upgrade and the SpamAssassin patch partial integration. There are several important changes that may affect your vpopmail installation and may need you to handle manually: - THE MYSQL CONNECTION INFORMATION IS NO LONGER DEFINED AT COMPILE-TIME! The WITH_MYSQL_{USER,PASSWD,SERVER,DB} variables should NOT be defined when you build the port; place that information in the vpopmail.mysql file after vpopmail has been installed! - the default domain is also no longer defined at compile time - you need to place it in the defaultdomain file after the installation. - the defaultdomain and vpopmail.mysql files are no longer blindly removed on deinstallation, they are only removed if they have not been modified - in vpopmail 5.4.18, the database schema was changed - some fields were extended from 64 to 96 characters. If you do not apply those changes to your database, as explained in the vpopmail/doc/UPGRADE file, your vpopmail installation may silently fail or lose the trailing portions of domain names and usernames. - in vpopmail 5.4.19, the upstream authors integrated large parts of Alex Dupre's SpamAssassin support, without the SPAM_THRESHOLD part. If you use vpopmail along with the SpamAssassin FreeBSD port support, take extra care to ensure that your installation still processes e-mail messages in the same way. - vpopmail 5.4.19 added support for maildrop as a mail delivery agent. This is available in the FreeBSD port if WITH_MAILDROP is defined. There is also a new user-limit flag for maildrop delivery. - vpopmail 5.4.19 added support for MySQL connections via Unix sockets instead of TCP sockets to the server. To do that, change the second value (the port number) in vpopmail.mysql to the full pathname of the MySQL socket (e.g. /tmp/mysql.sock). - vpopmail 5.4.20 extended the LDAP support; please see README.ldap for more information, and specify the LDAP connection information in the vpopmail/etc/vpopmail.ldap file after the installation.
2007-10-09 15:27:24 +02:00
%%PORTDOCS%%vpopmail/doc/README.onchange
%%PORTDOCS%%vpopmail/doc/README.oracle
%%PORTDOCS%%vpopmail/doc/README.pgsql
Update vpopmail to 5.4.20 after a long delay, mostly due to wondering how to handle the database upgrade and the SpamAssassin patch partial integration. There are several important changes that may affect your vpopmail installation and may need you to handle manually: - THE MYSQL CONNECTION INFORMATION IS NO LONGER DEFINED AT COMPILE-TIME! The WITH_MYSQL_{USER,PASSWD,SERVER,DB} variables should NOT be defined when you build the port; place that information in the vpopmail.mysql file after vpopmail has been installed! - the default domain is also no longer defined at compile time - you need to place it in the defaultdomain file after the installation. - the defaultdomain and vpopmail.mysql files are no longer blindly removed on deinstallation, they are only removed if they have not been modified - in vpopmail 5.4.18, the database schema was changed - some fields were extended from 64 to 96 characters. If you do not apply those changes to your database, as explained in the vpopmail/doc/UPGRADE file, your vpopmail installation may silently fail or lose the trailing portions of domain names and usernames. - in vpopmail 5.4.19, the upstream authors integrated large parts of Alex Dupre's SpamAssassin support, without the SPAM_THRESHOLD part. If you use vpopmail along with the SpamAssassin FreeBSD port support, take extra care to ensure that your installation still processes e-mail messages in the same way. - vpopmail 5.4.19 added support for maildrop as a mail delivery agent. This is available in the FreeBSD port if WITH_MAILDROP is defined. There is also a new user-limit flag for maildrop delivery. - vpopmail 5.4.19 added support for MySQL connections via Unix sockets instead of TCP sockets to the server. To do that, change the second value (the port number) in vpopmail.mysql to the full pathname of the MySQL socket (e.g. /tmp/mysql.sock). - vpopmail 5.4.20 extended the LDAP support; please see README.ldap for more information, and specify the LDAP connection information in the vpopmail/etc/vpopmail.ldap file after the installation.
2007-10-09 15:27:24 +02:00
%%PORTDOCS%%vpopmail/doc/README.qmail-default
%%PORTDOCS%%vpopmail/doc/README.quotas
%%PORTDOCS%%vpopmail/doc/README.roamingusers
Update vpopmail to 5.4.20 after a long delay, mostly due to wondering how to handle the database upgrade and the SpamAssassin patch partial integration. There are several important changes that may affect your vpopmail installation and may need you to handle manually: - THE MYSQL CONNECTION INFORMATION IS NO LONGER DEFINED AT COMPILE-TIME! The WITH_MYSQL_{USER,PASSWD,SERVER,DB} variables should NOT be defined when you build the port; place that information in the vpopmail.mysql file after vpopmail has been installed! - the default domain is also no longer defined at compile time - you need to place it in the defaultdomain file after the installation. - the defaultdomain and vpopmail.mysql files are no longer blindly removed on deinstallation, they are only removed if they have not been modified - in vpopmail 5.4.18, the database schema was changed - some fields were extended from 64 to 96 characters. If you do not apply those changes to your database, as explained in the vpopmail/doc/UPGRADE file, your vpopmail installation may silently fail or lose the trailing portions of domain names and usernames. - in vpopmail 5.4.19, the upstream authors integrated large parts of Alex Dupre's SpamAssassin support, without the SPAM_THRESHOLD part. If you use vpopmail along with the SpamAssassin FreeBSD port support, take extra care to ensure that your installation still processes e-mail messages in the same way. - vpopmail 5.4.19 added support for maildrop as a mail delivery agent. This is available in the FreeBSD port if WITH_MAILDROP is defined. There is also a new user-limit flag for maildrop delivery. - vpopmail 5.4.19 added support for MySQL connections via Unix sockets instead of TCP sockets to the server. To do that, change the second value (the port number) in vpopmail.mysql to the full pathname of the MySQL socket (e.g. /tmp/mysql.sock). - vpopmail 5.4.20 extended the LDAP support; please see README.ldap for more information, and specify the LDAP connection information in the vpopmail/etc/vpopmail.ldap file after the installation.
2007-10-09 15:27:24 +02:00
%%PORTDOCS%%vpopmail/doc/README.spamassassin
%%PORTDOCS%%vpopmail/doc/README.sybase
Update vpopmail to 5.4.20 after a long delay, mostly due to wondering how to handle the database upgrade and the SpamAssassin patch partial integration. There are several important changes that may affect your vpopmail installation and may need you to handle manually: - THE MYSQL CONNECTION INFORMATION IS NO LONGER DEFINED AT COMPILE-TIME! The WITH_MYSQL_{USER,PASSWD,SERVER,DB} variables should NOT be defined when you build the port; place that information in the vpopmail.mysql file after vpopmail has been installed! - the default domain is also no longer defined at compile time - you need to place it in the defaultdomain file after the installation. - the defaultdomain and vpopmail.mysql files are no longer blindly removed on deinstallation, they are only removed if they have not been modified - in vpopmail 5.4.18, the database schema was changed - some fields were extended from 64 to 96 characters. If you do not apply those changes to your database, as explained in the vpopmail/doc/UPGRADE file, your vpopmail installation may silently fail or lose the trailing portions of domain names and usernames. - in vpopmail 5.4.19, the upstream authors integrated large parts of Alex Dupre's SpamAssassin support, without the SPAM_THRESHOLD part. If you use vpopmail along with the SpamAssassin FreeBSD port support, take extra care to ensure that your installation still processes e-mail messages in the same way. - vpopmail 5.4.19 added support for maildrop as a mail delivery agent. This is available in the FreeBSD port if WITH_MAILDROP is defined. There is also a new user-limit flag for maildrop delivery. - vpopmail 5.4.19 added support for MySQL connections via Unix sockets instead of TCP sockets to the server. To do that, change the second value (the port number) in vpopmail.mysql to the full pathname of the MySQL socket (e.g. /tmp/mysql.sock). - vpopmail 5.4.20 extended the LDAP support; please see README.ldap for more information, and specify the LDAP connection information in the vpopmail/etc/vpopmail.ldap file after the installation.
2007-10-09 15:27:24 +02:00
%%PORTDOCS%%vpopmail/doc/README.vdelivermail
%%PORTDOCS%%vpopmail/doc/README.vlimits
%%PORTDOCS%%vpopmail/doc/README.vpopmaild
%%PORTDOCS%%vpopmail/doc/README.vqmaillocal
Update vpopmail to 5.4.20 after a long delay, mostly due to wondering how to handle the database upgrade and the SpamAssassin patch partial integration. There are several important changes that may affect your vpopmail installation and may need you to handle manually: - THE MYSQL CONNECTION INFORMATION IS NO LONGER DEFINED AT COMPILE-TIME! The WITH_MYSQL_{USER,PASSWD,SERVER,DB} variables should NOT be defined when you build the port; place that information in the vpopmail.mysql file after vpopmail has been installed! - the default domain is also no longer defined at compile time - you need to place it in the defaultdomain file after the installation. - the defaultdomain and vpopmail.mysql files are no longer blindly removed on deinstallation, they are only removed if they have not been modified - in vpopmail 5.4.18, the database schema was changed - some fields were extended from 64 to 96 characters. If you do not apply those changes to your database, as explained in the vpopmail/doc/UPGRADE file, your vpopmail installation may silently fail or lose the trailing portions of domain names and usernames. - in vpopmail 5.4.19, the upstream authors integrated large parts of Alex Dupre's SpamAssassin support, without the SPAM_THRESHOLD part. If you use vpopmail along with the SpamAssassin FreeBSD port support, take extra care to ensure that your installation still processes e-mail messages in the same way. - vpopmail 5.4.19 added support for maildrop as a mail delivery agent. This is available in the FreeBSD port if WITH_MAILDROP is defined. There is also a new user-limit flag for maildrop delivery. - vpopmail 5.4.19 added support for MySQL connections via Unix sockets instead of TCP sockets to the server. To do that, change the second value (the port number) in vpopmail.mysql to the full pathname of the MySQL socket (e.g. /tmp/mysql.sock). - vpopmail 5.4.20 extended the LDAP support; please see README.ldap for more information, and specify the LDAP connection information in the vpopmail/etc/vpopmail.ldap file after the installation.
2007-10-09 15:27:24 +02:00
%%PORTDOCS%%vpopmail/doc/UPGRADE
vpopmail/include/client.h
vpopmail/include/conf.h
vpopmail/include/config.h
vpopmail/include/ippp.h
vpopmail/include/storage.h
vpopmail/include/vauth.h
vpopmail/include/vlimits.h
vpopmail/include/vpopmail.h
vpopmail/include/vpopmail_config.h
vpopmail/lib/libvpopmail.a
%%LDAP%%vpopmail/ldap/README.ldap
Update vpopmail to 5.4.20 after a long delay, mostly due to wondering how to handle the database upgrade and the SpamAssassin patch partial integration. There are several important changes that may affect your vpopmail installation and may need you to handle manually: - THE MYSQL CONNECTION INFORMATION IS NO LONGER DEFINED AT COMPILE-TIME! The WITH_MYSQL_{USER,PASSWD,SERVER,DB} variables should NOT be defined when you build the port; place that information in the vpopmail.mysql file after vpopmail has been installed! - the default domain is also no longer defined at compile time - you need to place it in the defaultdomain file after the installation. - the defaultdomain and vpopmail.mysql files are no longer blindly removed on deinstallation, they are only removed if they have not been modified - in vpopmail 5.4.18, the database schema was changed - some fields were extended from 64 to 96 characters. If you do not apply those changes to your database, as explained in the vpopmail/doc/UPGRADE file, your vpopmail installation may silently fail or lose the trailing portions of domain names and usernames. - in vpopmail 5.4.19, the upstream authors integrated large parts of Alex Dupre's SpamAssassin support, without the SPAM_THRESHOLD part. If you use vpopmail along with the SpamAssassin FreeBSD port support, take extra care to ensure that your installation still processes e-mail messages in the same way. - vpopmail 5.4.19 added support for maildrop as a mail delivery agent. This is available in the FreeBSD port if WITH_MAILDROP is defined. There is also a new user-limit flag for maildrop delivery. - vpopmail 5.4.19 added support for MySQL connections via Unix sockets instead of TCP sockets to the server. To do that, change the second value (the port number) in vpopmail.mysql to the full pathname of the MySQL socket (e.g. /tmp/mysql.sock). - vpopmail 5.4.20 extended the LDAP support; please see README.ldap for more information, and specify the LDAP connection information in the vpopmail/etc/vpopmail.ldap file after the installation.
2007-10-09 15:27:24 +02:00
%%LDAP%%vpopmail/ldap/nsswitch.conf
%%LDAP%%vpopmail/ldap/pam_ldap.conf
%%LDAP%%vpopmail/ldap/pam_ldap.secret
%%LDAP%%vpopmail/ldap/qmailUser.schema
%%LDAP%%vpopmail/ldap/slapd.conf
%%LDAP%%vpopmail/ldap/vpopmail.ldif
Update vpopmail to 5.4.20 after a long delay, mostly due to wondering how to handle the database upgrade and the SpamAssassin patch partial integration. There are several important changes that may affect your vpopmail installation and may need you to handle manually: - THE MYSQL CONNECTION INFORMATION IS NO LONGER DEFINED AT COMPILE-TIME! The WITH_MYSQL_{USER,PASSWD,SERVER,DB} variables should NOT be defined when you build the port; place that information in the vpopmail.mysql file after vpopmail has been installed! - the default domain is also no longer defined at compile time - you need to place it in the defaultdomain file after the installation. - the defaultdomain and vpopmail.mysql files are no longer blindly removed on deinstallation, they are only removed if they have not been modified - in vpopmail 5.4.18, the database schema was changed - some fields were extended from 64 to 96 characters. If you do not apply those changes to your database, as explained in the vpopmail/doc/UPGRADE file, your vpopmail installation may silently fail or lose the trailing portions of domain names and usernames. - in vpopmail 5.4.19, the upstream authors integrated large parts of Alex Dupre's SpamAssassin support, without the SPAM_THRESHOLD part. If you use vpopmail along with the SpamAssassin FreeBSD port support, take extra care to ensure that your installation still processes e-mail messages in the same way. - vpopmail 5.4.19 added support for maildrop as a mail delivery agent. This is available in the FreeBSD port if WITH_MAILDROP is defined. There is also a new user-limit flag for maildrop delivery. - vpopmail 5.4.19 added support for MySQL connections via Unix sockets instead of TCP sockets to the server. To do that, change the second value (the port number) in vpopmail.mysql to the full pathname of the MySQL socket (e.g. /tmp/mysql.sock). - vpopmail 5.4.20 extended the LDAP support; please see README.ldap for more information, and specify the LDAP connection information in the vpopmail/etc/vpopmail.ldap file after the installation.
2007-10-09 15:27:24 +02:00
%%MAILDROP%%vpopmail/maildrop/maildroprc.v1
%%MAILDROP%%vpopmail/maildrop/maildroprc.v2
@dir(vpopmail,vchkpw,) vpopmail/domains
@dir(vpopmail,vchkpw,) vpopmail/bin
@dir(vpopmail,vchkpw,) vpopmail/etc
@dir(vpopmail,vchkpw,) vpopmail/include
@dir(vpopmail,vchkpw,) vpopmail/lib
@dir(vpopmail,vchkpw,) vpopmail
%%SPAMASSASSIN%%@exec echo "***********************************************************************"
%%SPAMASSASSIN%%@exec echo "Now you should add the following options to your spamd.sh startup file:"
%%SPAMASSASSIN%%@exec echo "-v -u vpopmail"
%%SPAMASSASSIN%%@exec echo "***********************************************************************"