Posts by anarking

Hi BeNe,

Pardon the delay. I just do simple global filtering with spamassassin and clamav. Basically I do reject (so no bounce spam can happen) and have the rest go through, marked as spam.

I keep levels relatively low, and have postgrey off. It is the same for all users. I get no false positives, and very little spam gets through.

I prefer to do this because I don't want the mail servers getting bombarded with spam that has to get processed, I'd rather reject it before it comes in, and this works well.

I really think the upgrade script should just give an option to leave things alone (upgrade postfix config files? yes/no), or integrate find/replace and add (for new lines) when dealing with master.cf and main.cf files. Mail is just too customizable to wipe it clean everytime like that.

Happy to help with this implementation.

hey sci.

good suggestion for recreations from upgrade... i was planning on changing the filename structure (just removing hour:minute or just minute), as the hour:minute format now is problematic/annoying for some scripts, etc., because linux has to put escape characters inbetween the ":". So I will make it to check for that format filename and else if it is the old format.

the reason why i want to add the initial gzip rsyncable to the create account (create only, modify is not affected), is because then the backup job can just be rsync. otherwise it has to run logic every time to if no backup exist, run gzip rsyncable.

to run a gzip rsyncable at the end of create account should take less than 1 second because the directory is very small at creation. this seems more efficient than adding more logic to run with every cron.

where is the end of the account creation script? at least for my own testing

thanks for the help sci.

okay so I am getting to work on this finally after virtualizing my infrastructure. the backup script is not a problem in imscp-backup-all, no problem there, i am familiar with it, but...

which file and where should the initial gzip rsyncable creation script go? It needs to happen at the end of the domain add script, as soon as that completes, so where is best for me to put the gzip creation lines? i am not familiar with the domain add engine files. (user_add#.php files?)

just let me know and i will finish the new backup system and let you guys know.

Hi All,

Just wondering, for the upgrade, is there or will there be options to leave the webmail untouched and also to leave postfix files (at least main.cf and master.cf) intact? I think giving the choice on whether or not to do such things during upgrade is a good option.

I changed out squirrelmail for roundcube, but now use afterlogic webmail lite, and don't want it changed, right now anyways

Also, I have modified my postfix main.cf and master.cf files, as I have a postfix/dovecot/spamassassin/clamav setup that is finely tuned.

Will the imscp upgrade overwrite those files? I have changed the original imscp master files it has also.

Thanks for any info

WHMCS is the best option and isn't very much cost per month for what it can do. These guys made a very nice bridge for it that works wonderfully. I recommend the setup.

hallo, what do you guys think about making the SSL option per domain (package option)?Thereby giving resellers/admins control over who can enable SSL. I think this might be a very nice way to option the new SSL feature you guys worked so hard on, but am not sure where to start with implementing this change...

i have always setup ispcp and imscp with dovecot/amavis/spamassassin as i find it to be the tightest filter without having false-positives. postgrey i often disable or relax.

i think to really integrate it with imscp would either be easy or take a decent amount of work.

easy - integrate it with the postfix/dovecot mail system. i always do this. very few false positives.

harder - integrate it will the mail system, but give the option (per domain) to enable/disable spam filtering and provide an option to delete the spam or redirect to a spam mailbox they have with their domain.

I'll see what I can do It will be a couple weeks before I can work on it, but it shouldn't take too long to implement. I do not know Perl very well, but bash is my friend so we will see.

The basic formula I think is this...

At domain creation, do gzip -rsyncable to backups directory.
For backup-all, rsync... (but it will need a check to make sure a gz is there, if it is not, it will need to run gzip). the behavior for this... what do you think?

if no gzip file found... run gzip? immediately? or wait until after other rsyncs are done? send error?

Hi All,

So, I realized a new behavior with sci2tech's sweet backup script, that, for me, is not ideal, and I think maybe others may want it changed in the release... I will let you decide...

The backup script deletes any folders in the /backups folder. For me, I have some domains with an archive script backing up to /backups/archive/ ... customers may also store something else there, who knows..

To modify this, I just modified /var/www/imscp/engine/backup/imscp-backup-all at line 108.

i changed

to

so that it is no longer recursive, and doesn't send the inconsequential "can't delete folder" error to the imscp error mailer

Also, (and I know this has been brought up before) what do we think about implementing something a little less disk intensive than deleting everything and recreating with tar+zip?

Perhaps if we went with an initial gzip --rsyncable and then did rsync backups from then on? Our servers would be much happier.

We could integrate the initial gzip --rsyncable with the domain creation process, that way we don't have to write any strange checks in the backup script, and that would be quick since it's only doing a couple files to start with.

How does this sound to everyone?

I think I'm going to begin implementing it myself anyways...

Nice, thank you balazsz, I didn't know about their webmail, it's a nice interface.

and for the lazy folks for this step... //Download AfterLogic: http://www.afterlogic.org/download/webmail-lite, and upload your web server

wget http://www.afterlogic.com/download/webmail_php.zip

Also, if one would for some reason like to hide the webmail lite footer at the bottom of the login/logout page, they would just need to edit the /webmail/index.php page at the very bottom, starting with this line, change it to look like this:

You could of course just delete the lines as well.
[hr]
The reason I went with this, is because roundcube doesn't like to be loaded in an iframe by default, and rather than spend time allowing it (roundcube is not so great anyways, this is by far a better client)... I just went with this.

However, on logout, it refreshes to index.php, which gets out of the iframe.

To change it so that when someone clicks logout, it redirects to the page of your choosing, simply modify /webmail/index.php and after line 115 (where it says CSession::ClearAll(); ) but before the next line's closing bracket }, add:

header( 'Location: http://www.whateveryouwant.com/email' ) ;

it can also be a relative path, but be aware it is going from the /webmail directory.