whoisjohngalt

Comments, suggestions, questions welcome. >#!/usr/bin/perl # Account name assigned to you by TCH. # i.e., who do you log in to CPanel with? $accountname = "<accountname>"; # Domain name used for e-mail $domainname = "<domain.name>"; # Mail account this is active for # NOT the entire e-mail address. Just # the section before the '@' sign. $mailuser = "<mailuser>"; # Location of your default mail target $target="inbox"; # Read in from standard input and check each # of our regular expressions. Set targets # accordingly. while(<STDIN>) { if($_ =~ m/^Subject:.*foo/) { $target="foo"; } elsif($_ =~ m/^From:.*badguy/) { $target="badguy"; } elsif($_ =~ m/^To:.*somelist/) { $target="somelist"; } $buffer .= $_; } # Location of your main mail folder $prefix="/home/".$accountname."/mail/".$domainname."/".$mailuser."/"; # Open our target, append our buffer to it, and close it open(MAILFILE, ">>".$prefix.$target); print MAILFILE $buffer; close(MAILFILE);

A hacked solution to this problem: http://www.totalchoicehosting.com/forums/i...?showtopic=8962

Ok ... here's my hack: I set up a filter in CPanel to filter e-mail destined for my e-mail address to |/home/<accountname>/procmail.pl. procmail.pl is a script I whipped up to try to process incoming e-mail. The following script gives 3 example actions: * Move e-mail with 'foo' in the subject to the folder 'foo' * Move e-mail from any address with 'badguy' in it to the 'badguy' folder * Move e-mail sent TO any address with 'somelist' in it to the 'somelist' folder. Obviously, in this loop, you can place procmail-esque rules and the entire script takes up only slightly more space than a real .procmailrc file. >#!/usr/bin/perl # Account name assigned to you by TCH. # i.e., who do you log in to CPanel with? $accountname = "<accountname>"; # Domain name used for e-mail $domainname = "<domain.name>"; # Mail account this is active for # NOT the entire e-mail address. Just # the section before the '@' sign. $mailuser = "<mailuser>"; # Location of your default mail target $target="inbox"; # Read in from standard input and check each # of our regular expressions. Set targets # accordingly. while(<STDIN>) { if($_ =~ m/^Subject:.*foo/) { $target="foo"; } elsif($_ =~ m/^From:.*badguy/) { $target="badguy"; } elsif($_ =~ m/^To:.*somelist/) { $target="somelist"; } $buffer .= $_; } # Location of your main mail folder $prefix="/home/".$accountname."/mail/".$domainname."/".$mailuser."/"; # Open our target, append our buffer to it, and close it open(MAILFILE, ">>".$prefix.$target); print MAILFILE $buffer; close(MAILFILE); Works like a champ. <----- Me doing the dance of joy.

From what I've read, people have used CPanel to setup forwards to the procmail binary. For example, use the forward interface in CPanel to forward all mail bound for someuser@mytchhost.com to |/path/to/procmail. If procmail were installed, that should force procmail to scan the user's home directory for .procmailrc and follow and rules that are in there. I understand TCH's desire to not support it, but if it were at least installed, then advanced users could utilize it nontheless as an unsupported and unadvertised feature. There really wouldn't be much to *support*. I really really really really want procmail (or anything similar) to support things like redirecting mail into specific folders for IMAP and such. I have quite a few procmail recipes that I've used for years and now I'm handcuffed on TCH's servers. If procmail will not be *supported* (i.e. installed at all), then is it possible to squeeze more functionality out of the .filter file? I couldn't get it to deliever my mail to anywhere other than my inbox file.

^^ BUMP ^^ Does procmail actually exist on the server? /usr/bin/procmail perhaps?

Hi all, I was wondering if it is possible to do procmail-type filtering on TCH's servers to filter incoming e-mail into folders? Obviously I'm aware that you can filter on the client, but I check mail through so many different clients, it gets old having to set up each client to filter accordingly. I know that Exim can do this (see this Exim Documentation Snippet) , but it seems as though we are limited to the forwarding functionality that CPanel's interface provides. Any help is appreciated. -M

Has TCH thought about using a DNS BlackList (dnsbl) on the mail server? http://www.exim.org/howto/rbl.html This HOWTO describes how to set it up in Exim. When I was running my domain at my house with Sendmail, these blacklists worked *GREAT* at booting spam off the system.

Thanks so much for your prompt and courteous reply! I understand all of that. I know it's such a little thing to be concerned about, but 7% of my bandwidth is 7% of my bandwidth.

How/where does one receive the password for the TCH customer forum? I would have expected it in my welcome e-mail, but I didn't see it in there.

New member here. So far I'm very pleased with TCH. Thanks for all your hard work. I have a suggestion. One thing that concerns me is the process of migrating a site from an existing host to TCH. In the process of migrating old content to TCH's servers, I have utilized an incredible amount of my monthly bandwidth allocation. Would it be possible for TCH to not count bandwidth utilization until perhaps the second week of membership? Or perhaps allocate some pre-defined extra amount for the first month? Let's assume a user signs up for an account that has the exact amount of disk space he/she needs to host his/her existing site. To migrate his/her site would use up an amount at least equal to his/her allocated disk space. Seeing as how this would be a one-time upload specific to the migration process, it seems a bit extreme to charge this against the user's monthly bandwidth allocation. The only drawback to this I could see would be potential abuse by users signing up for TCH accounts counting on this extra bandwidth for the first month, then signing up for another account the following month, etc. Any thoughts?