Re: [qmailadmin] please
Send a blank mail to: qmailadmin-unsubscr...@inter7.com On 11/21/2011 2:43 PM, TT wrote: please remove me from this list -- Mit freundlichen Grüßen *Thomas Tirel * *www.audioframes.de http://www.audioframes.de* -- Dave Steinberg http://www.geekisp.com/ http://www.steinbergcomputing.com/ http://www.redterror.net/ !DSPAM:4ecaac3a32711930119504!
Re: [qmailadmin] copyright notice
On 1/14/2011 12:21 PM, Rick Romero wrote: Quoting Matt Brookings m...@inter7.com mailto:m...@inter7.com: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 01/14/2011 11:13 AM, Trey Nolen wrote: We received a notice of unauthorized use of an image in the mail today. The image in question is the picture of the mailbox on the qmailadmin login screen named middleleft1.png. I didn't find anyone bringing this up on the mailing list archives. Has anyone else received this notice? The notice we received was from gettyimages (http://www.gettyimages.com). They are asking for a $600 settlement. Any comments or advice? Ignore them. They're incorrect. Who created that? gettyimages are trying to sell the image: http://www.gettyimages.com/Search/Search.aspx?contractUrl=2language=en-USfamily=creativeassetType=imagep=%23CA27907 Image: #CA27907 First, the requisite IANAL. I'm not sure I'd be comfortable ignoring the unauthorized use notice. I'd be the one getting fined and dealing with the hassle, not inter7. Do you guys have copyright over the image or is it licensed appropriately from the copyright holder? I would guess that getty is going to continue bothering the OP unless there is some sort of response indicating that he is using the image legally. Regards, -- Dave Steinberg http://www.geekisp.com/ http://www.steinbergcomputing.com/ http://www.redterror.net/ !DSPAM:4d308e9932711812379194!
Re: [qmailadmin] vmysql: can't read settings from
Mitja Pirih wrote: Hello, I searched through the mailing lists and did not find a solution to my problem. In the apache log I am getting: vmysql: can't read settings from /home/vpopmail/etc/vpopmail.mysql Tell us more about how you're running Apache. Is it running as the vpopmail user? Is it chroot'ed? snip As I can see, the problem would be between apache and executing qmailadmin/vpopmail as apache user. Or I am missing the right direction? I would guess the same as you. If Apache isn't running as your vpopmail user, I'd recommend using suexec to achieve that effect. This, of course, can be its own headache, but the docs are pretty good on the subject. Regards, -- Dave Steinberg http://www.geekisp.com/ http://www.steinbergcomputing.com/ !DSPAM:489b168e32311550932622!
Re: [qmailadmin] Something about spam command
Frankie Wong wrote: I use serversidefilter plugin of squirrelmail to create mailfilter in user's mailbox, content in .qmail file of individual user like this: |preline /usr/local/bin/maildrop /home/vpopmail/domains/mydomains.com/mailuser/Maildir/mailfilter Since mailfilter files in different domains of different users are different. How can I set enable-spam-command work together with it ? or let qmailadmin recongnize any line beginning with |preline to be the default delivery path and won't add additional delivery path to .qmail file when user set vacation or save a copy of forward? I do the same thing, but my .qmail file looks like: |preline -f /usr/local/bin/maildrop -d [EMAIL PROTECTED] If you can make that format work for you, you can try the '--enable-spamcmd-needs-email' flag in addition to the --enable-spam-command option. It was written for exactly this problem. Regards, -- Dave Steinberg http://www.geekisp.com/ http://www.steinbergcomputing.com/ !DSPAM:47bc3790310541220510052!
Re: [qmailadmin] New features
Matt Brookings wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, everyone. We've been hard at work on some new features for qmailadmin. Now that we've made some decent progress with the new features, I figured we should share them with everyone to get input. Sounds great Matt, I definitely appreciate your hard work. The Enable/Disable Account feature is of particular interest to me! :) Regards, -- Dave Steinberg http://www.geekisp.com/ http://www.steinbergcomputing.com/
Re: [qmailadmin] SMTP and IMAP flapping
Also note that you may have 'lots of space' but if you've got less than 5% left, it's reserved for root and won't help you. So don't only look at free space in GB, but also as a percentage. tune2fs will help fix that. I think you have this slightly backwards, the 5% you're mentioning is already accounted for by 'df' (sorta). Assuming the disk is at 100% usage as reported by df, there really is 5% free for use by root. 95% in use implies 5% available to normal users and an extra 5% on top available only to root. Regards, -- Dave Steinberg http://www.geekisp.com/ http://www.steinbergcomputing.com/
Re: [qmailadmin] Qmailadmin Procmail
I would not set up the machine the way you propose. Well, sometimes you gotta make do with one server =) It's basically a non-commercial operation. So I'll assume that it is unwise to use vpopmaild in a shared-hosting environment, and look to another solution to this challenge. Another note on this topic - there is some prior art that works with procmail and maildrop filters, though I can only speak of experience with the maildrop side. It works as a SquirrelMail plugin. http://www.squirrelmail.org/plugin_view.php?id=210 I have some local modifications as well, if you're interested. Regards, -- Dave Steinberg http://www.geekisp.com/ http://www.steinbergcomputing.com/ Regards, -- Dave Steinberg http://www.geekisp.com/ http://www.steinbergcomputing.com/
[qmailadmin] weird problem with corrupt .dir-control file
Hi everyone, I just solved a really weird problem with my dir-control file, and I wanted to seek advice and also record this in the archives in case anyone else had the issue. Basics of my setup: - vpopmail 5.4.6 (I'll upgrade once I'm done inflicting pain on myself in other ways) - NFS mounted home directories provide access to the /home/vpopmail directory. Another NFS volume provides /home/vpopmail/domains. Those are mounted on my 2 mail servers. - I have maproot=vpopmail on the domains mount, so even if I do stuff as root - the permissions stay correct as vpopmail:vchkpw. - NFS connectivity is local, over 100mbit switch. When the problem first started, it manifested itself as the error Unable to chdir to vpopmail/domains when I would run 'vadddomain -r8 testdom.com'. Naturally I *could* chdir to /home/vpopmail/domains - I even wrote a tiny c program and tried it as all the various uid's. No dice. Only after running vadddomain under gdb (props to you guys for keeping '-g' in the CFLAGS), was I able to figure out that the call to next_big_dir in vadddomain returned /home/vpopmail/domains/.dir-control, and so DomainSubDir was being set to /home/vpopmail/domains/.dir-control/testdom.com. Obviously, that doesn't fly to calls to mkdir(). I ended up restoring my .dir-control file from backups, and things appear to be back to normal. What would have really helped me would have been any of the following: - A call to perror() after failed mkdir() / chown calls. Not checking those return values was what bubbled up into a cryptic, misleading error message. - In r_mkdir, testing that tmpbuf either exists and is a directory, or doesn't exist. If its a file / link / pipe / whatever, then things should explode. Sadly, I don't have time to put together a patch at this time. Regards, -- Dave Steinberg http://www.geekisp.com/ http://www.steinbergcomputing.com/
Re: [qmailadmin] dotqmail and spamassassin
For example, $USER is set by qmail-local when it hands mail to vdelivermail, but this envariable is left unaltered: when the .qmail files are processed by vdelivermail, $USER is set to domain.com - which is just silly. Similarly, $HOME is set, but it is incorrect - it should be the virtual user's home, rather than vpopmail's home (why would anybody's mail delivering scripts need to know where vpopmail's home is? if nothing else that can be *EASILY* hardcoded in, it's not like it's gonna CHANGE for any of the users). Agreed, it'd be nice if all my tmda virtual user setups could avoid looking like: ~/username/Maildir/ . It's probably technically correct to leave them as is, just not very useful, and it makes the domain less virtual. If these envariables are fixed by vdelivermail, it would make it *MUCH* easier to move an existing qmail installation into a virtual setup. With the exception of qmail-extensions (which are done weirdly under vpopmail), nobody's .qmail files would need to be manually edited! Above all, it would wonderful if the envariables were made lowercase so I (and others) can take those dang tr calls out of our scripts. But some more intelligent environment setup would be a GREAT help. Well said. :) Regards, -- Dave Steinberg http://www.geekisp.com/ http://www.steinbergcomputing.com/
Re: [qmailadmin] question about qmailadmin feature
The easy way would be to setup basic authentication under Apache Location /cgi-bin/ezmlm-cgi AuthType Basic AuthName MailList AuthUserFile /web/hosts/www.somedomain.com/etc/users Require valid-user /Location The users file is created with htpasswd. I know this works in the web server configuration files, and may work in .htaccess files. While that would be easy, I would contest that it pales in comparison to systems where mailling list subscribers have full blown user accounts with passwords. Then you can have a notion of logging in, in order to check the necessary access required to view the archive. Mailman is one such example - though offhand I don't know of a way to make it work with QmailAdmin. That's a project for another day. The example as written isn't bad for a small group where the mailing list users are finite. When you start dealing with customers who are allowed to make their own mailing lists, and want to protect their archives, things get more complex. Regards, -- Dave Steinberg http://www.geekisp.com/ http://www.steinbergcomputing.com/
Re: [qmailadmin] feature added: append user's email to spam command
On Oct 26, 2004, at 1:00 PM, Tom Collins wrote: On Oct 26, 2004, at 7:16 AM, Dave Steinberg wrote: Hi all, I had the need to pass an individual user's email to my spam command, so I added the feature to QmailAdmin. Thanks Dave, I'll make sure it gets into the next QmailAdmin release. Just to prod a little bit, here's an updated patch against 1.2.7: http://www.redterror.net/patches/spam_needs_email-1.2.7.patch I'd love to see this incorporated into the trunk, so I wouldn't need to patch every time that I upgrade. :-) Regards, -- Dave Steinberg http://www.geekisp.com/ http://www.steinbergcomputing.com/
Re: [qmailadmin] Hard coded paths in qmailadmin
The reason for this is so that I can access qmailadmin purely by going to http://mailserver/ Initially, this seems to work. Browsing to that URL presents the qmailadmin login screen. However, after I enter a domain and password, my browser then attempts to load http://mailserver/cgi-bin/qmailadmin, which results in a 404. Does anyone know how to resolve this? While I realize it's a bit of a bandaid, as an interim you could do some magic with the Redirect directives, or mod_rewrite. Not necessarily ideal, but should work. Regards, -- Dave Steinberg http://www.geekisp.com/
Re: [qmailadmin] Re: [vchkpw] Why support imap?
On Wednesday, August 13, 2003, at 10:54 AM, Jeff Koch wrote: It seems that the qmail, vpopmail, qmailadmin people tend to recommend squirrelmail and sqwebmail. However, these are both imap clients. Our initial reaction is to prefer (in order to save bandwidth, cpu cycles and disk space) pop3 and have users keep their mail folders on their local PC's. Why do you all like the imap web email clients? Are there any pop3 only web email clients that you guys would recommend? I think people like the webmail clients because the protocol allows for more flexibility. There's nothing gained by switching to POP3 for a webmail client -- you still need to keep the user's email on your server. The web browser won't download and store the email on their PC. Getting your users to use a POP3 email client like Outlook Express or Eudora would reduce bandwidth and CPU cycles as the server would transmit only the email messages (without HTML overhead and message manipulation) to the end-user, and would typically only do it once. Some users don't have a single, local PC to store their email on, and prefer to use IMAP so they can access their email from multiple machines, and even have access to old email via a web browser when away from their PC. Well put Tom, agreed on all points. I'd like to add uniform backup capabilities to this list as well. With IMAP, I can advertise to my clients that I provide regular backups of all their mail and subsequently charge them for this service (though I don't actually charge for it, hypothetically I could). I tell them things like you'll never have to worry about losing mail because its all stored on the server and backed up at regular intervals. Plus the power users (like myself) want the flexibility it offers. I like being anywhere in the world (including home, using my primary pc) with access to all of my messages. Regards, -- Dave Steinberg http://www.geekisp.com
