Autorepsonder bug in admin backup/transfer

floyd

floyd

Verified User
Joined
Mar 29, 2005
Messages
6,271
1. Suspend user to prevent file changes during backup.
2. Create backup.
3. Transfer to new server.
4. Restore backup.
5. Autoresponder messages and logs are not present on the new server after restore.

Autoresponder messages are present on the original server. Bug is consistent. I have repeated it several times.
 
On the 20th may I allready reported these errors to directadmin:

Also same problem: suspend -> backup -> transfert to new server -> restore -> unsuspend

1) Some information of the spamassassin configuration is lost (field: “Where do you want the spam to go? (Inbox, spamfolder, delete)”)
2) SPAM Filter information is lost (the filter where you can setup “Block a specific e-mail address”, “Block mail from an entire domain”, …)
3) Catch-all information is lost.
4) Autoresponder information is lost.
5) The language of the controlpanel is lost.

We have had it with several accounts. So maybe it is the same problem (but more information is lost) as this bug report.
 
4) Autoresponder information is lost.
Click to expand...

You were not very specific.

When my client reported it to me at first glance I thought he was crazy because I could clearly see the autoreponders there. But it was the reply message that was lost. He was not specific with me either until I told him I could see the autoreponders there. Then he pointed me to the real problem which was not the autoreponders themselves but the reply messages.

You have to be specific when reporting a bug and tell people exactly how to recreate it. That is why I was specific in stating the messages and logs were lost.

Also I cannot even find your bug report.
 
Last edited:
I don't know about the rest of them but if you described the autoresponder problem to him back then the way you did here I understand why nothing was ever done about it. I reacted the same way when it was reported to me like that. I did not see a problem at first.

When reporting bugs you have to be very specific and describe exactly how to recreate the problem and how to see the result. In this case you have to click on Autoresponders and then click on Modify to see the problem. Just clicking on modify does not show you the problem.

The way I described it I specifically said "Autoresponder messages and logs are not present." That way they would know that I was not simply talking about the email addresses in the autoresponder.conf file which is saved and restored.
 
OK, about the point from the autoresponders, this can maybe be explained better. But what about the other points, they are clear: I told which fields lose there information, what should I do more? Look if the file /etc/virtual/[domain]/filter is present and good?

And another thing, If they look for this problem and they don't see the problem why doesn't they ask more information? I also make programs/php-scripts, and if my customers tell me a problem and I don't find it, I ask for more information. But now I don't know nothing, is it just a problem on our servers? Is it a bug? Have they searched already for the problem? Have they solved it? The only thing I know it that they have taken 'notice' of it.

If a customer contact the support center with a problem, it is not because the program is not good, it is only to help the designers and to make the program better.
 
Last edited:
Hello,

Thanks for all reports. They all aid us in becoming aware of the issues, but we're not always able to solve them right away. As more reports come in, we're usually able to narrow down the cause. In this case, luckily floyed figured out the cause, so we got a specific reproduction: "suspended domains", which allowed us to very quickly see it's a DA issue, thus it was fixed.

Reporting bugs is always the right thing to do, even if you don't know what's causing it, so that we become aware of them and can start looking at possible causes, even if it's not resolved immediately (We don't always figure them out right away). So if you don't get a solution to your report right away, your report still aids us in become aware of what issues are present, narrowing them down as more information about them comes in.

Keep in mind that I am human, contrary to common belief, so I don't always see everything all the time ;)

John
 
John,

I have a suggestion: Is it not beter to make a forum under General, something link 'Bug Reporting'. Where we can report bugs an talk about it (with you and other customers). First, every customer knows about a bug report (and it is all in 1 place). Second, other customers can do the same test to see if they also have that problem, and maybe ask more questions to the topic starter. Third, maybe implement (if possible) something voting/counting how many people have this problem OR a flag where we can say 'yes/no' this is a bug.

Then it is easier for you to make a quick view/judgement if it is an important bug and need to be solved urgent, or if it is only a problem on 1 server or on many servers, ...

Kind regards,
Maarten
 
I agree with having the bug reports in one sub forum. I had to take a minute to figure out where I should even post this one.

A bug reporting forum will also draw your attention to it faster. I don't know if you read all the posts in the entire forum or not. I would think a lot of it would be necessary for you to read. But the bug report sub forum is definitely one you should read since only you can fix it. Whenever you want to focus on fixing bugs you can come to the bug sub forum.

I think it would be a help to you more so than us.
 
You must log in or register to reply here.
Back
Top