Re: [qmailadmin] unable to login
If you have the compile directory from the old setup, I would look at 'config.log' for the configure script arguments. Maybe you can post your configure command for the current qmailadmin install. Vpopmail should also have its own logfile. It's usually very informative. Anything in /var/log/maillog ? On 10/19/2014 3:31 PM, francis drake wrote: Thanks for getting back to me, Derek. It's a .gz install. I'm using daemontools and checked all the qmail logs. I'm not getting any logs from pop3d. I'll have to look into that. On Sunday, October 19, 2014 12:09 PM, da...@nyi.net da...@nyi.net wrote: How did you install, from source or RPMs? IIRC when I last dealt with qmailadmin/vpopmail, qmailadmin had to be told about vpopmail with a flag. As for logging in, you should be able to log in as any user that vpopmail is aware of. Also, check your logs. Location depends on how you're running qmail (daemontools, etc). On 19.10.2014 14:28, francis drake wrote: Hi all, After more than 10 years my qmail, vpopmail, and qmailadmin setup died catastrophicly. qmailadmin was the core part of administering everything. I now have a new install of that setup. Mail delivery works and I can retrieve email from the postmaster and user accounts. However, loggin into qmailadmin's postmaster account using postmaster my.domain password results in Invalid Login. I also tried postmaster@my.domain but that doesn't work either. I reinstalled both vpopmail and qmailadmin but that didn't fix the problem. Also tried both 1.2.15 and 1.2.16. I checked the mail archives and even poked around in qmailadmin.c but am pretty lost when it comes to c programming. The o/s is fedora 20. Any help with this will be greatly appreciated, especially tips on how to debug this situation (didn't have much luck trying various printf instructions in the source). Looking forward to hearing from you, Mike Wright !DSPAM:544412b326512822510196!
Re: [qmailadmin] unable to login
You should always copy and paste the exact data. vpopmail user not found is different than vpopmail: user not found It would speed up getting a meaningful/helpful reply if you provided relevant (and accurate) info, like snippets from logs, your 'configure' arguments, etc. On 10/19/2014 3:41 PM, francis drake wrote: OK. Never thought to look in log/maillog. It's informative here: vpopmail user not found ... Bob suggested a permission problem with apache. I'll try setting up suid and getting back. I think we're on the right track. On Sunday, October 19, 2014 12:36 PM, Darek M. da...@nyi.net wrote: If you have the compile directory from the old setup, I would look at 'config.log' for the configure script arguments. Maybe you can post your configure command for the current qmailadmin install. Vpopmail should also have its own logfile. It's usually very informative. Anything in /var/log/maillog ? On 10/19/2014 3:31 PM, francis drake wrote: Thanks for getting back to me, Derek. It's a .gz install. I'm using daemontools and checked all the qmail logs. I'm not getting any logs from pop3d. I'll have to look into that. On Sunday, October 19, 2014 12:09 PM, da...@nyi.net da...@nyi.net wrote: How did you install, from source or RPMs? IIRC when I last dealt with qmailadmin/vpopmail, qmailadmin had to be told about vpopmail with a flag. As for logging in, you should be able to log in as any user that vpopmail is aware of. Also, check your logs. Location depends on how you're running qmail (daemontools, etc). On 19.10.2014 14:28, francis drake wrote: Hi all, After more than 10 years my qmail, vpopmail, and qmailadmin setup died catastrophicly. qmailadmin was the core part of administering everything. I now have a new install of that setup. Mail delivery works and I can retrieve email from the postmaster and user accounts. However, loggin into qmailadmin's postmaster account using postmaster my.domain password results in Invalid Login. I also tried postmaster@my.domain but that doesn't work either. I reinstalled both vpopmail and qmailadmin but that didn't fix the problem. Also tried both 1.2.15 and 1.2.16. I checked the mail archives and even poked around in qmailadmin.c but am pretty lost when it comes to c programming. The o/s is fedora 20. Any help with this will be greatly appreciated, especially tips on how to debug this situation (didn't have much luck trying various printf instructions in the source). Looking forward to hearing from you, Mike Wright !DSPAM:544417bb26514350843407!
Re: [qmailadmin] unable to login
I usually just set it to 'permissive'. I imagine you'll have to be making adjustments and allowing things as you discover more and more things not working. On 10/19/2014 5:19 PM, francis drake wrote: Thanks for your help Bob. Messing with suexec made things much worse. A break from the desk and breakfast at 2 this afternoon cleared my head a bit. Turned out to be an selinux restriction. I forgot to ask Derek this. Do you know just what I need to do to get this to fly with selinux set in enforcing mode? !DSPAM:544456dd26511922410443!
Re: [qmailadmin] Re: [SPAM] Whitelist rDNS for a single server
On 8/24/2011 2:03 PM, Rob Wright wrote: Thanks for the reply. It's definitely not spamdyke, as we do not have this installed. When Inter7 did the setup for is SpamAssassin was installed. Here's what I've got in my log file, it's qmail-smtpd doing the rejection. @40004e5539281689fb3c tcpserver: ok 10664 mail.poncacity.net:70.254.229.3:25 :70.254.229.27::53562 @40004e5539281aedc6a4 CHKUSER accepted rcpt: from rwri...@callisto.poncacity.net:unknown: remote callisto.poncacity.net:unknown:70.254 .229.27 rcptrwri...@poncacity.net : found existing recipient @40004e5539281db9851c qmail-smtpd: senders must have valid reverse DNS @40004e5539281dbe47dc tcpserver: end 10664 status 256 Part of the problem here is that I can't figure out what they've hacked to get qmail-smtpd to do the rejection. In my /var/qmail/control directory there is an 'rdns' file with a value of 1; rdns checking is either on or off. Any further ideas? I suppose this may be a lesson for the boss to install your own mail server but that bridge is already crossed. If there's no clear answer I'll just have to call Inter7 for support and let them deal with it. Install postfix as a smarthost? Do network tests there (excluding one IP from the reverse DNS requirement is done in the config file) then pass the message onto Qmail. Something like smtpd_client_restrictions = check_client_access cidr:/etc/postfix/skip_reverse_sender.cidr reject_unknown_reverse_client_hostname Inside the .cidr you'd have 1.2.3.0/29 OK -- Darek Rob On Wednesday 24 August 2011 11:49:44 Eric Shubert wrote: That would take care of things if the rejection is due to an RBL, but the rejection is stated as being due to lack of rDNS, which is different. The only thing I know of that rejects due to missing rDNS (using qmail) is spamdyke (a very good anti-spam tool btw). What specifically is causing the reject? You might post a sample from your smtp log if you can't tell. If it's spamdyke, then the spamdyke config has several ways of whitelisting. http://cr.yp.to/ucspi-tcp/rblsmtpd.html Edit your tcp.smtp file and put the address in and set RBLSMTPD= and it will bypass the RBL check for that IP address. Afterwards, rebuild your tcp.smtp.cdb file (depending on how your built your toaster it'll be as easy as qmailctl cdb, or some other manual command) Hope that helps. On 11-08-24 9:14 AM, Rob Wrightdebian...@poncacity.net wrote: Greetings. I hope this list is still intact and that I'm on-topic. I've searched for a solution and haven't been able to come up with anything. I've got a problem sprung up recently and can't quite figure out how to get around it. While I'm waiting for a bureaucracy to unsnaggle some DNS information on their side, is there anyway for us to whitelist a single mail server that's being rejected for not having rDNS? The mail server is known to us and I feel comfortable with taking this action. Hopefully this won't be a permanent solution but just a dirty hack while I wait for others to do their jobs. We've got a vanilla Inter7 installed vpopmail/qmail system and I have not been able to figure out of this is do-able or not. If it's possible how can I go about doing so? Thanks for any help or pointers. Rob Wright debian...@poncacity.net !DSPAM:4e553f8932715197284813!
Re: [qmailadmin] [SPAM] Incorrect quota usage reported
On 5/13/2011 6:45 PM, Wade Rossmann wrote: I would recommend upgrading vpopmail and qmailadmin. You'll probably also want to switch to Dovecot from Courier-IMAP. The server is quite old and has a tenuous grasp on stability, we cannot have the server/service go down so we are hesitant to perform software upgrades. We've got new servers we're moving to that are based on Postfix/Dovecot, but we're trying to 'gently encourage' users to reduce their disk usage beforehand. The trouble is the quota reporting is telling them they are not over quota at all. Where does qmailadmin pull the quota usage numbers from? vpopmail I am getting spotty results from 'vuserinfo', for the high-volume users will generally report 0% quota usage and rarely 100%. Does vpopmail rely on any sort of caching or internal db for these values? Could this be due to an integer overflow with such a large mailbox? As well, for users under quota usages have been reported differently between the OS/vpopmail and qmailadmin. Is there any caching taking place in qmailadmin? Try deleting the maildirsize file in a user's Maildir/ to force vpopmail to regenerate it. If it works, you could put that in a cron. I've been doing that for a while myself. I've made the move to postfix/postfixadmin/mysql/dovecot on a number of systems and am quite happy. Dovecot can even report quota usage directly to Thunderbird, which is neat. And there are server side filters using sieve that don't require ftp or shell access. It's all very nice and up to date. -- Darek !DSPAM:4dcdde2332719218516197!
