ispman-developers Mailing List for ispman

Feature Requests item #3292176, was opened at 2011-04-23 17:34
Message generated for change (Comment added) made by rmiddle
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=358390&aid=3292176&group_id=8390

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Robert Middleswarth (rmiddle)
Assigned to: Nobody/Anonymous (nobody)
Summary: ispman-agent add new command line option nodaemon

Initial Comment:
I was having problems keeping the agent running so I went and made a one line patch to remove the sleep line.  Once I did that and moved the agent to running on cron I haven't had a real problem with the agent in 2 years.  This week I decided to write up the patch into a proper patch but the basic's of this patch has been in use on my site for 2 years.



----------------------------------------------------------------------

>Comment By: Robert Middleswarth (rmiddle)
Date: 2011-04-25 11:28

Message:
Updated patch had a logic mistake in the 1st one.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=358390&aid=3292176&group_id=8390

Feature Requests item #3292176, was opened at 2011-04-23 17:34
Message generated for change (Tracker Item Submitted) made by rmiddle
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=358390&aid=3292176&group_id=8390

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Robert Middleswarth (rmiddle)
Assigned to: Nobody/Anonymous (nobody)
Summary: ispman-agent add new command line option nodaemon

Initial Comment:
I was having problems keeping the agent running so I went and made a one line patch to remove the sleep line.  Once I did that and moved the agent to running on cron I haven't had a real problem with the agent in 2 years.  This week I decided to write up the patch into a proper patch but the basic's of this patch has been in use on my site for 2 years.



----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=358390&aid=3292176&group_id=8390

Bugs item #2872205, was opened at 2009-10-03 11:56
Message generated for change (Tracker Item Submitted) made by nobody
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=108390&aid=2872205&group_id=8390

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: admin-interface
Group: 1.4
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Nobody/Anonymous (nobody)
Assigned to: Nobody/Anonymous (nobody)
Summary: Can't create email user.

Initial Comment:
I installed ISPMan on one machine where are located bind,apache, cyrus-imapd.

Everything works fine except cyrus-imapd. I cannoct create a new email user from web interface.

I see that ispman starts this command:

perl /var/www/ispman/bin/ispman.createMailbox -h sentinel.mydomain.tld us...@my...d

but user is not created and processes fails. I started this command as root from command line and i get this error:

IMAP::Admin [ create ]: couldn't create use...@do...d : try NO Permission denied

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=108390&aid=2872205&group_id=8390

Hey guys I wanted to save some problems for others, I just spent 4  
days trying to figure this out.  I just sent this to the perdition  
list so I hope it gets fixed, just incase I thought I'd share, here is  
what I sent to their list.  Hope it helps.

---

I'm not sure if this affects all ldap users, but since 1.18rc1 I  
couldn't login anymore using us...@do...d like used in ispman.

We used to use

http://server/?o=ispman?mailRoutingAddress?sub?(uid=%25s)

Since it's not using serverdb_get2 I updated that line to use

http://server/?o=ispman?mailRoutingAddress,mailHost?sub?(uid=%25s)

Which works 100% using ldap search  It returns

mailRoutingAddress = user_domain_tld@mailHost
mailHost = mailHost

so I had to also add to perdition.conf

strip_domain remote_login

Now that being said even with all that I'd get server null, looking  
into perditiondb_ldap.c I found that it wasn't setting the ref  
values.  I had to changes these lines

        /* Build the return string */
        if (returns[0])
                user_str = &returns[0];
        if (returns[1])
                server_str = &returns[1];
        if (returns[2])
                port_str = &returns[2];

to look like this

        /* Build the return string */
        if (returns[0])
                *user_str = returns[0];
        if (returns[1])
                *server_str = returns[1];
        if (returns[2])
                *port_str = returns[2];

Now everything works 100%, server gets set as does the user, hope this  
helps others cause it was 4 days of hell for me :D
---
TS
http://southofheaven.org/
Chaos is the beginning and end, try dealing with the rest.

Bugs item #2571722, was opened at 2009-02-06 08:34
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=108390&aid=2571722&group_id=8390

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: admin-interface
Group: 1.4
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Margusja (margusja)
Assigned to: Nobody/Anonymous (nobody)
Summary: missing ";" in file lib/database.MySQL.lib in line 125

Initial Comment:
    my $sql =
        "DELETE FROM mysql.user "
      . "WHERE User=\'" . $params->{'ispmanDBUser'} . "\' "
      . "AND Host=\'" . $params->{'ispmanDBAccessFilter'} . "\';"
    $sql .= "DROP DATABASE " . $params->{'ispmanDBName'} . ";";

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=108390&aid=2571722&group_id=8390

Bugs item #2483485, was opened at 2009-01-03 10:35
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=108390&aid=2483485&group_id=8390

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: admin-interface
Group: 1.4
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Joerg Delker (jdelker)
Assigned to: Joerg Delker (jdelker)
Summary: Form verification on database add form is broken

Initial Comment:
The verify function (js:verifyForm) on cgi/tmp/database/add.tmpl is never called.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=108390&aid=2483485&group_id=8390

Patches item #2455981, was opened at 2008-12-21 14:42
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=308390&aid=2455981&group_id=8390

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Joerg Delker (jdelker)
Assigned to: Joerg Delker (jdelker)
Summary: vhost actions

Initial Comment:
Added patch in behalf of Andreas John/Hans J. Martin:

This adds vhost actions to ispman.

Original comment (in german):

Moin moin,

da ich das irgendwie nicht wieder finden konnte, habe ich anliegend "mal
eben" einen kleinen patch geschrieben, der die Skripte ausführt.
Ich habe zwei Parameter übergeben:
a) Skriptname
b) uid des Vhost.
Die uid halte ich für die eindeutigste id, die zudem noch ein bequemes
ermitteln aller anderen Daten zum vhost (z.B, mittels id, getent passwd
etc) ermöglicht.

Die implementierte Lösung arbeitet analog zu den DomainActions. Für
beide Fälle würde ich aber vorschlagen, dass die verschiedenen Actions
auch per Komma separiert werden sollten (jetzt mit |) und * jeweils
vorselektierte Optionen sein sollten.
Zusätzlich würde ich das | Zeichen nutzen, um eine Beschreibung zum
Skriptname zu speichern. Das Feld würde dann z.B. so gefüllt sein:
"installT3Site.sh|TYPO3 Installieren,installVTiger.sh|VTiger CRM
installieren"
Ist alles kein "rocketscience", aber ich wollte das jetzt nicht ohne OK
für den Upstream den kram reinbasteln, da ein fork nur dazu führt, dass
wir das hauptprogramm nicht weiter entwickeln.



----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=308390&aid=2455981&group_id=8390

Bugs item #2213932, was opened at 2008-11-01 12:43
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=108390&aid=2213932&group_id=8390

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Andreas John (derjohn)
Assigned to: Nobody/Anonymous (nobody)
Summary: Allow nodns/slave domains to be changed to to other types

Initial Comment:
Hi,
if you created a Domain as "nodns", you cannot change the domain's type to "primary" or "secondary" afterwards.

There is already a patch out somewhere in the net, which solved the problem partly:

----
Hi,

ChangeLog:
  * Allow "nodns" and "slave" domains to be changed to "nodns", "slave",
    or "primary" domains.

  -- John K. Hohm, ProviNET Solutions <jh...@pr...>

http://marc.info/?l=ispman-developers&m=108007771518943&w=2
----

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=108390&aid=2213932&group_id=8390

Hey Ali,

I suspect something wrong with your general ISPMan installation.
How did you install?
How does your ISPMan directory layout look like?

Regards,
Joerg

Ali Nebi wrote:
> Hi,
> 
> i have a problem when try to get all users with overquotas. When i run 
> the script i get
> these errors:
> 
> Can't locate package AutoLoader for <at> ISPMan::Config::ISA at
> /var/www/ispman/bin/../lib/ISPMan/Config.pm line 90, <DATA> line 424.
> Can't locate package AutoLoader for <at> ISPMan::Config::ISA at
> /var/www/ispman/bin/../lib/ISPMan/Config.pm line 90, <DATA> line 424.
> Can't locate package AutoLoader for <at> ISPMan::Config::ISA at
> /var/www/ispman/bin/../lib/ISPMan/Config.pm line 90, <DATA> line 424.
> Name "main::mailbox" used only once: possible typo at 
> ./ispman.listOverQuotaMailboxes
> line 32, <DATA> line 424.
> Use of uninitialized value in substitution (s///) at
> /var/www/ispman/bin/../lib/mailbox_actions_cyrus.lib line 27, <DATA> 
> line 424.
> Use of uninitialized value in concatenation (.) or string at
> /var/www/ispman/bin/../lib/mailbox_actions_cyrus.lib line 29, <DATA> 
> line 424.
> 
> We have installed this version: ispman-1.3CVS
> 
> and these perl pakages are installed:
> perl-Compress-Zlib-1.42-1.fc6
> perl-DBD-MySQL-3.0007-1.fc6
> perl-RPM2-0.67-1.el5.rf
> perl-XML-SAX-0.14-5
> perl-Email-Valid-0.179-1.el5.rf
> perl-FreezeThaw-0.43-5.el5.kb.1
> perl-JSON-1.15-1.el5.rf
> perl-Mail-DomainKeys-1.0-1.el5.rf
> perl-AppConfig-1.66-1.el5.rf
> perl-Locale-Maketext-Lexicon-0.66-1.el5.rf
> perl-Pod-POM-0.17-3
> perl-version-0.74-1.el5.rf
> perl-String-CRC32-1.4-2.fc6
> perl-Net-DNS-0.59-3.el5
> newt-perl-1.08-9.2.2
> mod_perl-2.0.2-6.3.el5
> perl-IO-Zlib-1.04-4.2.1
> perl-Mail-SPF-Query-1.999.1-2.el5.rf
> perl-Net-IMAP-Simple-1.17-1.el5.centos
> perl-Net-Jabber-2.0-1.2.el5.rf
> perl-Crypt-Blowfish-2.10-1.2.el5.rf
> perl-IO-stringy-2.110-1.2.el5.rf
> perl-Authen-SASL-2.11-1.el5.rf
> perl-Socket6-0.19-3.fc6
> perl-URI-1.35-3
> perl-IO-Socket-INET6-2.51-2.fc6
> perl-Net-IP-1.25-2.fc6
> perl-DBI-1.52-1.fc6
> perl-DBD-Pg-1.49-1.fc6
> perl-Crypt-DES-2.05-3.2.el5.rf
> perl-MailTools-1.77-1.el5.centos
> perl-Sys-Hostname-Long-1.4-1.2.el5.rf
> perl-Convert-ASN1-0.20-1.1
> perl-DNS-ZoneParse-0.95-2.centos5
> perl-Net-XWhois-0.90-1.2.el5.rf
> perl-IO-Multiplex-1.08-4
> perl-Crypt-OpenSSL-RSA-0.25-1.el5.rf
> perl-Template-Toolkit-2.19-1.el5.rf
> perl-GSSAPI-0.26-1.el5.rf
> perl-Convert-BinHex-1.119-2.2.el5.rf
> perl-TeX-Hyphen-0.140-1.2.el5.rf
> perl-CGI-Session-4.30-1.el5.rf
> perl-BSD-Resource-1.28-1.fc6.1
> perl-HTML-Parser-3.55-1.fc6
> perl-libwww-perl-5.805-1.1.1
> cyrus-imapd-perl-2.3.7-1.1.el5
> perl-5.8.8-10.el5_0.2
> perl-DBD-SQLite-1.14-1.el5.rf
> perl-Data-UUID-1.148-1.el5.rf
> perl-XML-NamespaceSupport-1.09-1.2.1
> perl-MIME-tools-5.420-4.el5.kb
> perl-Archive-Zip-1.16-1.2.1
> perl-XML-Stream-1.22-1.2.el5.rf
> perl-Log-Agent-0.307-1.el5.rf
> perl-Compress-LZF-3.11-1.el5.rf
> perl-Crypt-OpenSSL-Random-0.04-1.el5.rf
> perl-Geography-Countries-1.4-2.2.el5.rf
> perl-Convert-UUlib-1.051-1.2.el5.rf
> perl-Razor-Agent-2.84-1.el5.rf
> perl-Convert-TNEF-0.17-3.2.el5.rf
> perl-Unicode-String-2.09-1.2.el5.rf
> perl-Text-Iconv-1.7-1.el5.rf
> perl-IP-Country-2.24-1.el5.rf
> perl-BerkeleyDB-0.34-1.el5.rf
> perl-SOAP-Lite-0.710.05-1.el5.rf
> perl-Digest-SHA1-2.11-1.2.1
> perl-HTML-Tagset-3.10-2.1.1
> perl-Net-SSLeay-1.30-4.fc6
> perl-Archive-Tar-1.30-1.fc6
> perl-Net-CIDR-Lite-0.20-1.2.el5.rf
> perl-Mail-Sendmail-0.79-6
> perl-Net-XMPP-1.02-1.el5.rf
> perl-Crypt-CBC-2.24-1.el5.rf
> perl-Unix-Syslog-1.0-1.el5.rf
> perl-Digest-HMAC-1.01-15
> perl-IO-Socket-SSL-1.01-1.fc6
> perl-TimeDate-1.16-5.el5
> perl-LDAP-0.33-3.fc6
> perl-Mail-RFC822-Address-0.3-1.el5.rf
> perl-Net-Server-0.97-1.el5.rf
> perl-Text-Autoformat-1.13-1.2.el5.rf
> perl-MIME-Lite-3.021-1.el5.rf
> perl-Text-Reform-1.11-3
> perl-IMAP-Admin-1.6.4-1.2.el5.rf
> perl-Net-SNMP-5.2.0-1.2.el5.rf
> perl-Text-Template-1.45-1.el5.rf
> 
> The OS is Centos 5 x86_64
> 
> What can i do to solve this problem?
> 
> Thanks in advanced!
> 
> 
> ------------------------------------------------------------------------
> 
> -------------------------------------------------------------------------
> Check out the new SourceForge.net Marketplace.
> It's the best place to buy or sell services for
> just about anything Open Source.
> http://sourceforge.net/services/buy/index.php
> 
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> Ispman-developers mailing list
> Isp...@li...
> https://lists.sourceforge.net/lists/listinfo/ispman-developers

Hi,

i have a problem when try to get all users with overquotas. When i run the
script i get
these errors:

Can't locate package AutoLoader for <at> ISPMan::Config::ISA at
/var/www/ispman/bin/../lib/ISPMan/Config.pm line 90, <DATA> line 424.
Can't locate package AutoLoader for <at> ISPMan::Config::ISA at
/var/www/ispman/bin/../lib/ISPMan/Config.pm line 90, <DATA> line 424.
Can't locate package AutoLoader for <at> ISPMan::Config::ISA at
/var/www/ispman/bin/../lib/ISPMan/Config.pm line 90, <DATA> line 424.
Name "main::mailbox" used only once: possible typo at
./ispman.listOverQuotaMailboxes
line 32, <DATA> line 424.
Use of uninitialized value in substitution (s///) at
/var/www/ispman/bin/../lib/mailbox_actions_cyrus.lib line 27, <DATA> line
424.
Use of uninitialized value in concatenation (.) or string at
/var/www/ispman/bin/../lib/mailbox_actions_cyrus.lib line 29, <DATA> line
424.

We have installed this version: ispman-1.3CVS

and these perl pakages are installed:
perl-Compress-Zlib-1.42-1.fc6
perl-DBD-MySQL-3.0007-1.fc6
perl-RPM2-0.67-1.el5.rf
perl-XML-SAX-0.14-5
perl-Email-Valid-0.179-1.el5.rf
perl-FreezeThaw-0.43-5.el5.kb.1
perl-JSON-1.15-1.el5.rf
perl-Mail-DomainKeys-1.0-1.el5.rf
perl-AppConfig-1.66-1.el5.rf
perl-Locale-Maketext-Lexicon-0.66-1.el5.rf
perl-Pod-POM-0.17-3
perl-version-0.74-1.el5.rf
perl-String-CRC32-1.4-2.fc6
perl-Net-DNS-0.59-3.el5
newt-perl-1.08-9.2.2
mod_perl-2.0.2-6.3.el5
perl-IO-Zlib-1.04-4.2.1
perl-Mail-SPF-Query-1.999.1-2.el5.rf
perl-Net-IMAP-Simple-1.17-1.el5.centos
perl-Net-Jabber-2.0-1.2.el5.rf
perl-Crypt-Blowfish-2.10-1.2.el5.rf
perl-IO-stringy-2.110-1.2.el5.rf
perl-Authen-SASL-2.11-1.el5.rf
perl-Socket6-0.19-3.fc6
perl-URI-1.35-3
perl-IO-Socket-INET6-2.51-2.fc6
perl-Net-IP-1.25-2.fc6
perl-DBI-1.52-1.fc6
perl-DBD-Pg-1.49-1.fc6
perl-Crypt-DES-2.05-3.2.el5.rf
perl-MailTools-1.77-1.el5.centos
perl-Sys-Hostname-Long-1.4-1.2.el5.rf
perl-Convert-ASN1-0.20-1.1
perl-DNS-ZoneParse-0.95-2.centos5
perl-Net-XWhois-0.90-1.2.el5.rf
perl-IO-Multiplex-1.08-4
perl-Crypt-OpenSSL-RSA-0.25-1.el5.rf
perl-Template-Toolkit-2.19-1.el5.rf
perl-GSSAPI-0.26-1.el5.rf
perl-Convert-BinHex-1.119-2.2.el5.rf
perl-TeX-Hyphen-0.140-1.2.el5.rf
perl-CGI-Session-4.30-1.el5.rf
perl-BSD-Resource-1.28-1.fc6.1
perl-HTML-Parser-3.55-1.fc6
perl-libwww-perl-5.805-1.1.1
cyrus-imapd-perl-2.3.7-1.1.el5
perl-5.8.8-10.el5_0.2
perl-DBD-SQLite-1.14-1.el5.rf
perl-Data-UUID-1.148-1.el5.rf
perl-XML-NamespaceSupport-1.09-1.2.1
perl-MIME-tools-5.420-4.el5.kb
perl-Archive-Zip-1.16-1.2.1
perl-XML-Stream-1.22-1.2.el5.rf
perl-Log-Agent-0.307-1.el5.rf
perl-Compress-LZF-3.11-1.el5.rf
perl-Crypt-OpenSSL-Random-0.04-1.el5.rf
perl-Geography-Countries-1.4-2.2.el5.rf
perl-Convert-UUlib-1.051-1.2.el5.rf
perl-Razor-Agent-2.84-1.el5.rf
perl-Convert-TNEF-0.17-3.2.el5.rf
perl-Unicode-String-2.09-1.2.el5.rf
perl-Text-Iconv-1.7-1.el5.rf
perl-IP-Country-2.24-1.el5.rf
perl-BerkeleyDB-0.34-1.el5.rf
perl-SOAP-Lite-0.710.05-1.el5.rf
perl-Digest-SHA1-2.11-1.2.1
perl-HTML-Tagset-3.10-2.1.1
perl-Net-SSLeay-1.30-4.fc6
perl-Archive-Tar-1.30-1.fc6
perl-Net-CIDR-Lite-0.20-1.2.el5.rf
perl-Mail-Sendmail-0.79-6
perl-Net-XMPP-1.02-1.el5.rf
perl-Crypt-CBC-2.24-1.el5.rf
perl-Unix-Syslog-1.0-1.el5.rf
perl-Digest-HMAC-1.01-15
perl-IO-Socket-SSL-1.01-1.fc6
perl-TimeDate-1.16-5.el5
perl-LDAP-0.33-3.fc6
perl-Mail-RFC822-Address-0.3-1.el5.rf
perl-Net-Server-0.97-1.el5.rf
perl-Text-Autoformat-1.13-1.2.el5.rf
perl-MIME-Lite-3.021-1.el5.rf
perl-Text-Reform-1.11-3
perl-IMAP-Admin-1.6.4-1.2.el5.rf
perl-Net-SNMP-5.2.0-1.2.el5.rf
perl-Text-Template-1.45-1.el5.rf

The OS is Centos 5 x86_64

What can i do to solve this problem?

Thanks in advanced!

Bugs item #1952308, was opened at 2008-04-26 16:59
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=108390&aid=1952308&group_id=8390

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: admin-interface
Group: HEAD
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Joerg Delker (jdelker)
Assigned to: Joerg Delker (jdelker)
Summary: user's loginshell selection defaults to wrong value

Initial Comment:
The loginshell selection in the user edit form, always defaults to the first value in "availableShells" confVar, regardless of any value set previously.

As a consequence the loginshell is always modified to a possibly wrong value when the user is saved.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=108390&aid=1952308&group_id=8390

Bugs item #1952280, was opened at 2008-04-26 13:08
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=108390&aid=1952280&group_id=8390

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: admin-interface
Group: None
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Andreas John (derjohn)
Assigned to: Nobody/Anonymous (nobody)
Summary: default value for "edit replica"

Initial Comment:
If you edit a replica and look for the dropdown "this Replica points to", there is always a default for the first one in lexicographical order. I would like to see the domain as default value, that is currently chosen as master for that replica. This is something between a bug, an annoyance and a wish, but it file it here ;)






----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=108390&aid=1952280&group_id=8390

Bugs item #1952276, was opened at 2008-04-26 13:05
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=108390&aid=1952276&group_id=8390

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Andreas John (derjohn)
Assigned to: Nobody/Anonymous (nobody)
Summary: Not possible to change a Replicas Master to a noDNS Domain

Initial Comment:
If you create a replica domain for a primary and want to change the replicas primary afterwards, you can only choose primary, but not nodns domains. I regards that as a bug, there must be a some pausibilty check in the code,  that doesnt respect  nodns domains.


----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=108390&aid=1952276&group_id=8390

Bugs item #1952274, was opened at 2008-04-26 13:00
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=108390&aid=1952274&group_id=8390

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Andreas John (derjohn)
Assigned to: Nobody/Anonymous (nobody)
Summary: DNS TXT Records with spaces / special chars might not work

Initial Comment:
I tried to add a TXT Record in a not-so-very-current CVS version of ISPMan. The TXT record contains spaces and equal chars ("="). LDAP is not very 
happy with that:

---
DN passed: txtRecord=v=spf1 ip4:x.y.z.a/20 ip4:a.b.c.d/29 
-all,ou=txtRecord,dc=net-lab,dc=net,ou=DNS,o=ispman,dc=net-lab,dc=net

Return code: 34
Error name: LDAP_INVALID_DN_SYNTAX
Error text: The request contained an invalid DN

Error desc: Invalid DN syntax
MessageID: 5
Error: invalid DN
Server Error: invalid DN
DN:
Canonical DN:
---

Please note that the above record does really make sense in a realworld scenario (SPFs). I worked around by creating a net-lab.net.local file, but think there is a bug TXT records handling (may already resolved?).


----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=108390&aid=1952274&group_id=8390

Feature Requests item #1703226, was opened at 2007-04-18 20:29
Message generated for change (Comment added) made by nose
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=358390&aid=1703226&group_id=8390

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: None
Status: Open
Resolution: Remind
Priority: 5
Private: No
Submitted By: Nathan (technosattva)
Assigned to: Nobody/Anonymous (nobody)
Summary: PowerDNS

Initial Comment:
PowerDNS (powerdns.com) is a DNS server that supports MySQL and LDAP as backends. I haven't found anything about integration between ISPMAN and PDNS, but it would be great to see. 

----------------------------------------------------------------------

Comment By: Norbert Sendetzky (nose)
Date: 2008-04-06 10:27

Message:
Logged In: YES 
user_id=355850
Originator: NO

The PowerDNS LDAP backend uses the dnsdomain2 schema originally created by
the Bind LDAP maintainer. The domainRelatedObject schema defines only the
basic objects that are not included twice in the dnsdomain2 schema.

dnsdomain2 and dnszone schema differ only in one important point: The
domain name is stored in associatedDomain in dnsdomain2 whereas dnszone
splits this into two parts (rdn and zonename). Adding the complete domain
name (rdn.zonename) to associatedDomain would be sufficient to support the 
PowerDNS LDAP backend too. All other records are exactly the same and I've
also added the latest record types to the schemas in both projects.

Regards,


Norbert


----------------------------------------------------------------------

Comment By: Joerg Delker (jdelker)
Date: 2007-04-19 09:55

Message:
Logged In: YES 
user_id=43997
Originator: NO

Unfortunately, a direct integration is currently out of sight, because
powerdns and ispman use different LDAP schemas for dns record storage.
If someone will extend the powerdns ldap backend to support the dnsZone
schema/entries you will have immediate integration.

Powerdns uses the standard "domainRelatedObject" as defined by RFC 1279,
which is good on one hand but on the other lacks support for extended DNS
records (e.g. txtRecords).
So currently I see no way of ispman using this schema.
But I'll remember it for ispman 2.0 design ;)

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=358390&aid=1703226&group_id=8390

Hello Joerg,
I tried to add a TXT Record in a not-so-very-current CVS version of 
ISPMan. The TXT record contains spaces and = chars. LDAP is not very 
happy with that:

---
DN passed: txtRecord=v=spf1 ip4:80.69.32.0/20 ip4:213.83.36.136/29 
-all,ou=txtRecord,dc=net-lab,dc=net,ou=DNS,o=ispman,dc=net-lab,dc=net

Return code: 34
Error name: LDAP_INVALID_DN_SYNTAX
Error text: The request contained an invalid DN

Error desc: Invalid DN syntax
MessageID: 5
Error: invalid DN
Server Error: invalid DN
DN:
Canonical DN:
---

Please note that the above records does reall make sense (SPFs). I 
worked around by creating a net-lab.net.local file, but think there is a 
bug TXT recirds handling (may already resolved?).

rgds,
Andreas

Bugs item #1870758, was opened at 2008-01-13 23:57
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=108390&aid=1870758&group_id=8390

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: backend
Group: HEAD
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Joerg Delker (jdelker)
Assigned to: Joerg Delker (jdelker)
Summary: mail alias check may fail

Initial Comment:
When editing users with mail aliases set, the save may fail with complaining about an alias conflict.
In fact, it complains, that the alias is already used by the very same entry ;)

Cause: Comparison of the found entries fail, because identical DNs don't match due to spaces.



----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=108390&aid=1870758&group_id=8390

Forwarding ....

-------- Original-Nachricht --------
Betreff: Re: [Ispman-developers] Report for a bug probably, that you can
fix in the develop version - Master - Replica domain - virtual_alias_map
Datum: Tue, 1 Jan 2008 22:46:10 +0200
Von: Ali Nebi <ane...@gm...>
An: Andreas John <li...@aj...>
Referenzen:
<9b8...@ma...>	
<477...@aj...>

On Dec 28, 2007 1:58 PM, Andreas John <li...@aj...> wrote:

> Hi,
>
> > The problem is that when we send message to non-exist user
> > (non...@ma...) everything works ok, it rejects the message,
> > but when we send message to replica domain (non...@re...)
> > SMTP server accept the mail. What we want is to reject every mail send
> > to non-exist user in our system.
>
> We have a similar problem, even with non-ISPMan-Setups. The problem
> comes IMVHO from
>
> @domain.foo  @domain.bar
>
> In that case  postfix doesnt reject mail for non-existing users in the
> first steup (client or recipient restrictions).
>
> Currently we circumvent th eproblem by setting
>
> us...@do...o us...@do...r
> us...@do...o us...@do...r
> etc.
>
> rgds,
> Andreas
>
>
Hi,

First of all, i want to wish you happy new year  and also thanks for the
reply.

Yes, this is the reason to try to change ispman to make alias for all
replica domains, this way it will add them to virtual alias table and when
postfix checkes virtual alias map for validating, it will validate only
existing users. Maybe i'm wrong i don't know.


us...@do...o us...@do...r
us...@do...o us...@do...r

This way that you told me, it will work yes.

Regards, Ali Nebi.

Hi,

> The problem is that when we send message to non-exist user
> (non...@ma...) everything works ok, it rejects the message,
> but when we send message to replica domain (non...@re...)
> SMTP server accept the mail. What we want is to reject every mail send
> to non-exist user in our system.

We have a similar problem, even with non-ISPMan-Setups. The problem
comes IMVHO from

@domain.foo  @domain.bar

In that case  postfix doesnt reject mail for non-existing users in the
first steup (client or recipient restrictions).

Currently we circumvent th eproblem by setting

us...@do...o us...@do...r
us...@do...o us...@do...r
etc.

rgds,
Andreas




> I think this happens because we have this for replica domain:
> 
> mailLocalAddress: @replica.com
> mailForwardingAddress: @master.com
> 
> and in virtual_alias_map is writen domain like @replica.com and this
> tell smtp server to accept every mail send top this domain.
> 
> I think that if we make aliases for every user like:
> 
> mailAlias: use...@re...
> 
> for every replica domains and remove the lines:
> 
> mailLocalAddress: @replica.com
> mailForwardingAddress: @master.com
> 
> from replica domain definition, this will help to validate the mails
> send to replica domains.
> 
> What is your opinion for this and is there some way to solve this
> problem ?
> 
> If this is the real problem please to fix this in new version.
> 
> Thanks in advanced!
> 
> Regards, Ali Nebi!
> 
> 
> 
> ------------------------------------------------------------------------
> 
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2005.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> 
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> Ispman-developers mailing list
> Isp...@li...
> https://lists.sourceforge.net/lists/listinfo/ispman-developers

Hi,

before to write what is needed, i want to excuse me for my bad english and
if you need more info for the problem please tell me, i will post it here.

I understood that right now is developing a new version of ISPMan. It is
really a good software.
I want to ask if it is possible to solve in the new version (or offer some
solution for) a problem that i saw. We have installed ispman, postfix and we
are using ispman and ldap to manage
domains and users. But we have a problem with virtual_alias_map in postfix.
We are validating recipients and everything works very well for master
domains, but not for replica domains.

here is a link with more explanation for the same problem:

http://www.nabble.com/Configuring-postfix-to-read-replica-domains-when-mail-arrives-td10248794.html

I will give an example.

Let's tell that our master domain is called master.com and replica
domains is called replica.com that point to master domain - master.com.

This is the structure for master domain:

# master.com, ISPMan, example.com
dn: ispmanDomain=master.com,ou=ISPMan,dc=example,dc=com
objectClass: ispmanDomain
objectClass: posixAccount
objectClass: PureFTPdUser
ispmanStatus: active
ispmanCreateTimestamp: 1024645619
ispmanDomainType: primary
ispmanDomainOwner: Owner 7 GmbH
ispmanDomainCustomer: Owner 7 GmbH
ispmanDomain: master.com
ispmanDomainMailDeliveryMethod: local
cn: master.com
uid: master.com
uidNumber: 1453
gidNumber: 1276
homeDirectory: /var/www/domains/master.com
userPassword:: e21kNX0vNFRhVndRRGJUbkNjZFc3VWRVWFlnPT0=
loginShell: /bin/false
ispmanMaxAccounts: -1
ispmanMaxVhosts: -1
ispmanDomainService: mail
ispmanDomainService: http
ispmanDomainDefaultMailDropHost: gandalf.example.com
ispmanDomainDefaultWebHost: wolf.example.com
FTPStatus: enabled
FTPQuotaMBytes: 1
ispmanDomainDefaultFileServer: wolf.iguanait.com

And this is the structure for replica domain:

# replica.com, ISPMan, example.com
dn: ispmanDomain=replica.com,ou=ISPMan,dc=example,dc=com
objectClass: ispmanDomain
objectClass: ispmanBranch
ispmanStatus: active
ispmanCreateTimestamp: 1029688427
ispmanDomainType: replica
ispmanDomainOwner: Owner GmbH
ispmanDomainCustomer: Owner GmbH
ispmanDomain: replica.com
ispmanDomainMailDeliveryMethod: local
ispmanReplicaMaster: master.com
mailLocalAddress: @replica.com
mailForwardingAddress: @master.com

This is the content in ldap_alias.cf in postfix:

# LDAP virtual maps.
server_host = localhost
version = 3
timeout = 30
bind = no
search_base = ou=ISPMan,dc=example,dc=com
query_filter = (|(mailLocalAddress=%s)(mailAlias=%s)(uid=%s))
result_attribute = mailRoutingAddress,mailForwardingAddress

This is a part of postfix configuration:
smtpd_recipient_restrictions =
        permit_mynetworks,
        permit_sasl_authenticated,
        reject_unauth_destination,
        check_recipient_access hash:/etc/postfix/access,
        reject_multi_recipient_bounce,
        reject_non_fqdn_recipient,
        reject_unknown_recipient_domain

virtual_alias_maps =
        hash:/etc/postfix/virtual,
        ldap:/etc/postfix/ldap-aliases.cf
virtual_alias_domains = hash:/etc/postfix/destination_domains

smtpd_recipient_restrictions =
        permit_mynetworks,
        permit_sasl_authenticated,
        reject_unauth_destination,
        check_recipient_access hash:/etc/postfix/access,
        reject_multi_recipient_bounce,
        reject_non_fqdn_recipient,
        reject_unknown_recipient_domain


The problem is that when we send message to non-exist user
(non...@ma...) everything works ok, it rejects the message,
but when we send message to replica domain (non...@re...)
SMTP server accept the mail. What we want is to reject every mail send
to non-exist user in our system.

I think this happens because we have this for replica domain:

mailLocalAddress: @replica.com
mailForwardingAddress: @master.com

and in virtual_alias_map is writen domain like @replica.com and this
tell smtp server to accept every mail send top this domain.

I think that if we make aliases for every user like:

mailAlias: use...@re...

for every replica domains and remove the lines:

mailLocalAddress: @replica.com
mailForwardingAddress: @master.com

from replica domain definition, this will help to validate the mails
send to replica domains.

What is your opinion for this and is there some way to solve this
problem ?

If this is the real problem please to fix this in new version.

Thanks in advanced!

Regards, Ali Nebi!

Hello all,

Two  things.

1. If you are interested in ISPDirector development, please join the 
group ispdirector-dev on google groups.
http://groups.google.com/group/ispdirector-dev/

I would like not to discuss too much on this list to avoid confusion.


2. One of the design goals of this project which was in the wishlist of 
ispman was to have a backend and frontend (SOAP/REST/etc)
The reason would be something like.
 a) utility developers dont have to know or have to care about the rest
 b) another frontend can be written with any language of choice etc.

I am going with this goal in mind and trying to avoid whatever I can to 
get there.

As I mentioned, the core (the provisioning part) is written so far in php.
For the CLI part it might be perl/python whatever.

I have written a quick cli tool in perl which you can download and 
execute on your own machine without installing anything from ispdirector.
http://ispdirector.googlecode.com/svn/trunk/clients/perl/ispdc.pl

You can run this POC (Proof Of Concept) tool with the following.
perl ispdc.pl listusers

perl ispdc.pl showuser user_id=4

This will actually talk to demo.ispdirector.net over standard http and 
get the data back in JSON and will convert it to perl and will do 
whatever is needed.

best regards

Thanks to Andreas for the demo machine.
You can now see the interface at

http://demo.ispdirector.net
login: admin@localhost
pass: secret

Note: This is only 2 days of work without looking at the ispman sourcecode.
The users and domain interface allows you to add/edit users.





-- 
best regards
Atif Ghaffar

Hi Joerge,

I just found your email. Didnt notice that I contacted you on the -users
list which I dont monitor all the time.
So I am bringing it back to -developers list.


On Dec 17, 2007 10:46 AM, Joerg Delker <jd...@on...> wrote:

>
> Yes indeed, I did a (MySQL based) database layout as a working draft for
>  "ISPMan Next Generation" project, and I'm happy to share that.


Thanks. I look at the schema and it looks very similar to what I jotted
down.
I think we can bring it very close to match.

As you may know, I'm trying myself with an ISPMan rewrite for some time
> now, but am proceeding quite slowly due to many time constraints.
> Actually, a real pity, because I've so many nice ideas... ;)
>

All nice ideas are welcome :-)
I will discuss the schema with you in detail to see where you are going with
it.

I also see that the schema also tries to be compatible with LDAP schema (the
counters table for example).
I see it this way, if we go with the RDBMS and LDAP  aproach then I would
think that we must only generate what is really needed in LDAP.
For example there will be no need to put the config_vars, etc in LDAP.

Perhaps the DNS and vhosts information may not be needed as well.
If it is needed, we can generate it.



>
> Starting a rewrite yourself is somewhat opening competition for me, but
> maybe that gives some "kick" to get going again. ;)

Yup.


>
> My approach is Java/Perl/Webservice based. Currently, that is not yet
> publicly shared, because I still change it a lot, as I'm experimenting
> with various webservice alternatives.

Okay. I have not started on the webservices part yet, but I will get to that
soon.
Currently I am trying to keep the code very clean and separate.

For example there is a core layer and everything else sits on top of it.
The core layer can do db access, etc but other layers never know that there
is a database or LDAP behind.



>
> Rather than considering this as fierce competition, I really would
> prefer a cooperative side-by-side and eventually get the best "out
> of both worlds".

Ofcoarse. For me it is an experiment too to see how well Zend framework
behaves and how manageable it can get.


>
>
> You'll find the schema here:
>
> https://sourceforge.net/tracker/index.php?func=detail&aid=1852150&group_id=8390&atid=358390
> Consider this a working draft, that has not yet passed "reality-check".
> Changes are probably inevitable, but it would be preferable if we could
> align on a common schema within the ongoing projects.
>

so far I done the users, domains, schema.
I will keep documenting the schema here.
http://code.google.com/p/ispdirector/wiki/Design

I am also putting effort in the user-interface at the same time so there
will be something people can see and not just design documents.
I am working on a single panel which can be used by admin, resellers,
customers so we dont have to branch off admin panel and CCP etc.


I am also keeping in mind the localization etc. For example the localization
data will be in the same database which can be used to generate XML or .mo
files.

The dns data is also in the db and I will use your schema for it. It is very
simple and can be used to generate any format for bind, ldap, powerdns mysql
backend etc.

I am waiting for the server that Andreas is setting up for the demo to put
whatever I have online for others to see.

best regards.

Hi Atif,
Yes, I'll gladly provide you an XEN. I'll put a ubuntu 7.10 into it. OK?

Contact me via p-mail for login-data.

rgds,
Andreas



Atif Ghaffar wrote:
> Hello,
> 
> Can someone provide a machine (perhaps virtual) with support for
> php 5.2 and mysql-5
> 
> An ideal would be a machine running ubuntu 7.10 server to match my
> development environment.
> 
> This would help users/developers to see the user-interface at every step and
> provide feedback.
> 
> thanks.
> 
> 
> 
> ------------------------------------------------------------------------
> 
> -------------------------------------------------------------------------
> SF.Net email is sponsored by:
> Check out the new SourceForge.net Marketplace.
> It's the best place to buy or sell services
> for just about anything Open Source.
> http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace
> 
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> Ispman-developers mailing list
> Isp...@li...
> https://lists.sourceforge.net/lists/listinfo/ispman-developers

Hello,

Can someone provide a machine (perhaps virtual) with support for
php 5.2 and mysql-5

An ideal would be a machine running ubuntu 7.10 server to match my
development environment.

This would help users/developers to see the user-interface at every step and
provide feedback.

thanks.