Facebook
Twitter
Autoresponder API (not enabling after creation)
CPU: AuthenticAMD, Quad-Core AMD Opteron(tm) Processor 2352
Version: Parallels Plesk Panel v10.4.4_build1013111102.18 os_CentOS 5
OS: Linux 2.6.18-194.26.1.el5xen
Using the API I am able to create an autoresponder for a previously non-existent email address.
The problem is, even though it's created, it's is not enabled.
EXPECTED RESULT: autoresponder created and enabled
ACTUAL RESULT: autoresponder created and NOT enabled
More info:
a.) Control panel shows it as enabled (see screenshot attached)
b.) sql query of psa.mail_resp shows:
mysql> select * from mail_resp;
+----+-------+-----------+--------+-----------+---------+----------+--------------+---------+---------------+---------+----------+-----------+
| id | mn_id | resp_name | keystr | key_where | subject | reply_to | content_type | charset | text | resp_on | ans_freq | mem_limit |
+----+-------+-----------+--------+-----------+---------+----------+--------------+---------+---------------+---------+----------+-----------+
| 43 | 66 | default | | no | | | text/plain | UTF-8 | Here ya go... | true | 1 | 1000 |
+----+-------+-----------+--------+-----------+---------+----------+--------------+---------+---------------+---------+----------+-----------+
1 row in set (0.00 sec)
c.) sql query of psa.mail where id=66 shows:
mysql> select * from mail where id=66;
+----+--------+-----------+---------+---------+------------+----------+------------+------------+---------------+------------+-------------+------------+--------+
| id | userId | mail_name | perm_id | postbox | account_id | redirect | redir_addr | mail_group | autoresponder | spamfilter | virusfilter | mbox_quota | dom_id |
+----+--------+-----------+---------+---------+------------+----------+------------+------------+---------------+------------+-------------+------------+--------+
| 66 | 0 | testblah | 0 | false | 88 | false | | false | false | false | none | -1 | 6 |
+----+--------+-----------+---------+---------+------------+----------+------------+------------+---------------+------------+-------------+------------+--------+
1 row in set (0.00 sec)
d.) mail -i [email protected] shows:
[root@shared3 htdocs]# /usr/local/psa/bin/mail -i [email protected]
Mailname: testblah
Domain: qrtrackcenter.com
Mailbox: false
Password:
Password type: plain
Mbox quota: Unlimited
Mailgroup: false
Attachment files: 1_4eedf53598f74.mp3
Autoresponders: Disabled
Status: true
Answer with subject: Re: <incoming subject>
Answer text: Here ya go...
Attachment files: 1_4eedf53598f74.mp3
Forward request:
Antivirus mail checking: Can not determine
SUCCESS: Gathering information for '[email protected]' complete
e.) autoresponder -i -mail [email protected] shows:
[root@shared3 htdocs]# /usr/local/psa/bin/autoresponder -i -mail [email protected]
Status true
Answer with subj:
Format: plain
Charset: UTF-8
Answer text: Here ya go...
Attach files: 1
1_4eedf53598f74.mp3
Forward request:
SUCCESS: Gathering information for autoresponder complete
f.) API REQUEST
<packet version="1.6.3.0">
<mail>
<create>
<filter>
<site-id>6</site-id>
<mailname>
<name>testblah</name>
<autoresponder>
<enabled>true</enabled>
<subject></subject>
<text>Here ya go...</text>
<attachment>
<tmp-name>{$pnFile}</tmp-name>
<file-name>{$fname}</file-name>
</attachment>
</autoresponder>
</mailname>
</filter>
</create>
</mail>
</packet>
g.) API RESPONSE
<?xml version="1.0" encoding="UTF-8"?>
<packet version="1.6.3.0"><mail><create><result><status>ok</status><mailname><id>66</id><name>testblah</name></mailname></result></create></mail></packet>
h.) If I run /usr/local/psa/bin/autoresponder -u -mail [email protected], the autoresponder enables and works. Doing this, I noticed in the DB after running the command that psa.mail [autoresponder switches from "false" to "true"]. HOWEVER, making a sql query to change that value in lieu of running the command line autoresponder utility does NOT work so I'm guessing other elements in the DB get changed(?) or something else happens when running the update on the command line.
Any clarification on this issue would be great. I've been over the API reference and docs a thousand times and unless I'm missing something I believe this to be a bug in the API system. I'm not opposed to a "temporary" fix involving making a DB query to enable after setting this up via API but I cannot use the command line utility for this application.
Thanks,
J
CPU: AuthenticAMD, Quad-Core AMD Opteron(tm) Processor 2352
Version: Parallels Plesk Panel v10.4.4_build1013111102.18 os_CentOS 5
OS: Linux 2.6.18-194.26.1.el5xen
Using the API I am able to create an autoresponder for a previously non-existent email address.
The problem is, even though it's created, it's is not enabled.
EXPECTED RESULT: autoresponder created and enabled
ACTUAL RESULT: autoresponder created and NOT enabled
More info:
a.) Control panel shows it as enabled (see screenshot attached)
b.) sql query of psa.mail_resp shows:
mysql> select * from mail_resp;
+----+-------+-----------+--------+-----------+---------+----------+--------------+---------+---------------+---------+----------+-----------+
| id | mn_id | resp_name | keystr | key_where | subject | reply_to | content_type | charset | text | resp_on | ans_freq | mem_limit |
+----+-------+-----------+--------+-----------+---------+----------+--------------+---------+---------------+---------+----------+-----------+
| 43 | 66 | default | | no | | | text/plain | UTF-8 | Here ya go... | true | 1 | 1000 |
+----+-------+-----------+--------+-----------+---------+----------+--------------+---------+---------------+---------+----------+-----------+
1 row in set (0.00 sec)
c.) sql query of psa.mail where id=66 shows:
mysql> select * from mail where id=66;
+----+--------+-----------+---------+---------+------------+----------+------------+------------+---------------+------------+-------------+------------+--------+
| id | userId | mail_name | perm_id | postbox | account_id | redirect | redir_addr | mail_group | autoresponder | spamfilter | virusfilter | mbox_quota | dom_id |
+----+--------+-----------+---------+---------+------------+----------+------------+------------+---------------+------------+-------------+------------+--------+
| 66 | 0 | testblah | 0 | false | 88 | false | | false | false | false | none | -1 | 6 |
+----+--------+-----------+---------+---------+------------+----------+------------+------------+---------------+------------+-------------+------------+--------+
1 row in set (0.00 sec)
d.) mail -i [email protected] shows:
[root@shared3 htdocs]# /usr/local/psa/bin/mail -i [email protected]
Mailname: testblah
Domain: qrtrackcenter.com
Mailbox: false
Password:
Password type: plain
Mbox quota: Unlimited
Mailgroup: false
Attachment files: 1_4eedf53598f74.mp3
Autoresponders: Disabled
Status: true
Answer with subject: Re: <incoming subject>
Answer text: Here ya go...
Attachment files: 1_4eedf53598f74.mp3
Forward request:
Antivirus mail checking: Can not determine
SUCCESS: Gathering information for '[email protected]' complete
e.) autoresponder -i -mail [email protected] shows:
[root@shared3 htdocs]# /usr/local/psa/bin/autoresponder -i -mail [email protected]
Status true
Answer with subj:
Format: plain
Charset: UTF-8
Answer text: Here ya go...
Attach files: 1
1_4eedf53598f74.mp3
Forward request:
SUCCESS: Gathering information for autoresponder complete
f.) API REQUEST
<packet version="1.6.3.0">
<mail>
<create>
<filter>
<site-id>6</site-id>
<mailname>
<name>testblah</name>
<autoresponder>
<enabled>true</enabled>
<subject></subject>
<text>Here ya go...</text>
<attachment>
<tmp-name>{$pnFile}</tmp-name>
<file-name>{$fname}</file-name>
</attachment>
</autoresponder>
</mailname>
</filter>
</create>
</mail>
</packet>
g.) API RESPONSE
<?xml version="1.0" encoding="UTF-8"?>
<packet version="1.6.3.0"><mail><create><result><status>ok</status><mailname><id>66</id><name>testblah</name></mailname></result></create></mail></packet>
h.) If I run /usr/local/psa/bin/autoresponder -u -mail [email protected], the autoresponder enables and works. Doing this, I noticed in the DB after running the command that psa.mail [autoresponder switches from "false" to "true"]. HOWEVER, making a sql query to change that value in lieu of running the command line autoresponder utility does NOT work so I'm guessing other elements in the DB get changed(?) or something else happens when running the update on the command line.
Any clarification on this issue would be great. I've been over the API reference and docs a thousand times and unless I'm missing something I believe this to be a bug in the API system. I'm not opposed to a "temporary" fix involving making a DB query to enable after setting this up via API but I cannot use the command line utility for this application.
Thanks,
J
Attachments
Last edited:
