[qmailtoaster] Add White Horse repos for QTP updates?
Could someone possibly post a simple walkthrough to add the White Horse repos for QTP updates on CentOS 6? Diana Calder, Automation Technician 360 Fairview Ave. West Suite 101, Essex, Ontario N8M 1Y3 T: 519-776-5241 ext. 131F: 519-776-6851 dcal...@essexcountylibrary.ca This email may contain confidential information. If you are not one of the intended recipients, if you receive this email or if it is forwarded to you without the express authorization of Essex County Library, please destroy this email and contact us immediately. P Please consider the environment before printing this e-mail
Re: [qmailtoaster] Re: One user account can't login to Squirrelmail
Hello Eric,
Friday, July 25, 2014, 7:13:21 PM, you wrote:
On 07/25/2014 10:45 AM, Diana Calder wrote:
Thursday, July 24, 2014, 6:57:21 PM, Eric wrote:
On 07/24/2014 06:39 AM, Diana Calder wrote:
I have an odd problem with one user account. When trying to login to
Squirrelmail, the login will hang for several seconds then result in:
ERROR: Connection dropped by IMAP server.
Query: LOGOUT
This is now happening with more than one user account. The problem has
returned on the one that I *thought* I had fixed plus it's showing up
on multiple other accounts. Yet some still work.
snip
Anybody have any suggestions? I'm just about ready to give in and do a
fresh install of CentOS and Qmail, then import all of my old messages.
Except that I'm not entirely certain that the problem won't follow the
old messages to a new box.
Please post result of:
# doveconf -n
[root@qmail ~]# doveconf -n
# 2.2.7: /etc/dovecot/dovecot.conf
# OS: Linux 2.6.32-431.20.3.el6.x86_64 x86_64 CentOS release 6.5 (Final) ext4
auth_cache_size = 32 M
auth_mechanisms = plain login digest-md5 cram-md5
debug_log_path = /var/log/dovecot-debug.log
default_client_limit = 1024
disable_plaintext_auth = no
first_valid_gid = 89
first_valid_uid = 89
log_path = /var/log/dovecot.log
login_greeting = Dovecot toaster ready.
mail_debug = yes
mail_location = maildir:/home/vpopmail/domains/essexcountylibrary.ca/%n/Maildir
mail_plugins = quota
namespace {
inbox = yes
location =
mailbox Drafts {
auto = subscribe
special_use = \Drafts
}
mailbox Sent {
auto = subscribe
special_use = \Sent
}
mailbox Sent Messages {
auto = no
special_use = \Sent
}
mailbox Spam {
auto = create
special_use = \Junk
}
mailbox Trash {
auto = subscribe
special_use = \Trash
}
prefix =
separator = .
type = private
}
passdb {
args = cache_key=%u webmail=127.0.0.1
driver = vpopmail
}
plugin {
quota = maildir:ignore=Trash
quota_rule = ?:storage=0
}
protocols = imap pop3
service imap-login {
process_limit = 300
process_min_avail = 5
service_count = 0
}
service pop3-login {
service_count = 0
}
ssl_cert = /var/qmail/control/servercert.pem
ssl_key = /var/qmail/control/servercert.pem
userdb {
args = cache_key=%u quota_template=quota_rule=*:backend=%q
driver = vpopmail
}
protocol imap {
imap_capability = IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE IDLE
SORT SORT=DISPLAY THREAD=REFERENCES THREAD=REFS MULTIAPPEND UNSELECT CHILDREN
NAMESPACE UIDP LUS LIST-EXTENDED I18NLEVEL=1 ESEARCH ESORT SEARCHRES WITHIN
CONTEXT=SEARCH LIST-STATUS
imap_client_workarounds = delay-newmail
mail_max_userip_connections = 0
mail_plugins = quota imap_quota
}
protocol pop3 {
pop3_client_workarounds = outlook-no-nuls oe-ns-eoh
pop3_fast_size_lookups = yes
pop3_lock_session = yes
}
Also, how many SM users are there, and how many IMAP that are not SM?
All users (about 94 total) have access to Squirrelmail. Of those 94,
most only sign in maybe once a week, if that, and 27 accounts would
only rarely sign in to Squirrelmail - usually when out of office.
Non-SM IMAP - the 27 accounts that I already mentioned - will
eventually all be on non-SM IMAP but five or six are currently still
on POP3.
--
Best regards,
Diana Calder mailto:dcal...@essexcountylibrary.ca
Automation Technician(519) 776-5241 x.131
Essex County Library
Essex, ON
-
To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com
Re: [qmailtoaster] Re: One user account can't login to Squirrelmail
Thursday, July 24, 2014, 6:57:21 PM, Eric wrote: On 07/24/2014 06:39 AM, Diana Calder wrote: Hello Angus, Wednesday, July 23, 2014, 2:20:45 PM, you wrote: Diana Calder wrote: I have an odd problem with one user account. When trying to login to Squirrelmail, the login will hang for several seconds then result in: ERROR: Connection dropped by IMAP server. Query: LOGOUT This is now happening with more than one user account. The problem has returned on the one that I *thought* I had fixed plus it's showing up on multiple other accounts. Yet some still work. Here's what the Dovecot log shows: Jul 25 13:30:08 imap-login: Info: Aborted login (auth failed, 1 attempts in 2 secs): user=pacad...@essexcountylibrary.ca, method=CRAM-MD5, rip=::1, lip=::1, secured, session=2x6i7Af/NwAB All accounts still work with either POP3 or IMAP from a client (The Bat!), they only have issues in Squirrelmail. Having said, that, I will occasionally see an IMAP account hang in The Bat! - it will hang up on accessing the account for hours until the user manually tells The Bat! to abort the connection. It logs in okay: 25/07/2014, 13:21:02: IMAP - Connecting to IMAP server in.essexcountylibrary.ca on port 143 25/07/2014, 13:21:02: IMAP - Connected to IMAP server (in.essexcountylibrary.ca) 25/07/2014, 13:21:02: IMAP - Dovecot toaster ready. 25/07/2014, 13:21:02: IMAP - Authenticating (user: pacad...@essexcountylibrary.ca, method: LOGIN)... 25/07/2014, 13:21:02: IMAP - IMAP server authentication OK, server says Logged in But that's where it hangs - it simply stays connected to the server forever without ever updating the mailboxes OR erroring out. Here's what Dovecot shows in this case: Jul 25 13:32:23 imap-login: Info: Login: user=pacadm...@essexcountylibrary.ca, method=PLAIN, rip=205.207.189.15, lip=205.207.189.144, mpid=3558, session=b9TM9Af/gQDNz70P This looks exactly like the first log entry for a fully successful connection via The Bat!: Jul 25 13:34:36 imap-login: Info: Login: user=dcal...@essexcountylibrary.ca, method=PLAIN, rip=205.207.189.15, lip=205.207.189.144, mpid=3707, session=ccS3/Af/mwDNz70P Jul 25 13:34:41 imap(dcal...@essexcountylibrary.ca): Info: Disconnected: Disconnected in IDLE in=4199 out=76924 I haven't observed any SM specific problems with large mailboxes. There were problems with Courier IMAP and large mailboxes, but Dovecot should have no problems with them. This is one of the reasons we're using dovecot instead of courier now. I wouldn't hesitate to let users have 1G mailboxes, so long as you have the disk space. Yes, we have the disk space. I already had the headache of having to increase the partition size once, so I made sure to make it ridiculously huge when I did that. Also, be sure to use the dirindex option if you use the ext3/4 filesystem. Not having that turned on can cause performance problems with folders which have a large number of messages. Yep, that was already on. I also went in and enabled noatime but, considering that it didn't help with the problem, I'm debating turning that back off. Anybody have any suggestions? I'm just about ready to give in and do a fresh install of CentOS and Qmail, then import all of my old messages. Except that I'm not entirely certain that the problem won't follow the old messages to a new box. -- Best regards, Diana Calder mailto:dcal...@essexcountylibrary.ca Automation Technician(519) 776-5241 x.131 Essex County Library Essex, ON - To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com
Re: [qmailtoaster] One user account can't login to Squirrelmail
Hello Angus, Wednesday, July 23, 2014, 2:20:45 PM, you wrote: Diana Calder wrote: I have an odd problem with one user account. When trying to login to Squirrelmail, the login will hang for several seconds then result in: ERROR: Connection dropped by IMAP server. [ ... snip ... ] A possible symptom or secondary issue is that the problem account is using 78% of its 1Gb quota ... He has about 700 messages in his Inbox ... That might be the issue. I've seen SquirrelMail serve up blank pages, apparently due to timeout issues, when trying to open mail folders that contained very large numbers of messages. I'd give serious consideration to the possibility that something like that is happening here. snip Rather than mucking about with the directories on the server as admin, I decided to just use his The Bat! POP3 account to Dispatch Mail on Server - All Messages. I'm not quite sure when or how but, at some point, his POP3 settings had obviously been changed to leave everything on the server, then changed back to delete from server when deleted from The Bat! but NOT changed back to delete everything else from the server after a set length of time - he had messages on there dating back to about a year after he started working here. Not only did he have messages going back 3 years, he also had messages with huge attachments. I somewhat arbitrarily decided that, since he was using POP3, anything that was previously downloaded was fair game, and deleted everything more than 90 days old from the server. While that took him down to only using 16% of his 1Gb quota, it did not immediately correct the login issue. However, when I tested again this morning, I was able to login with his account via Squirrelmail. So, whether it was really the messages that I cleared out or something else entirely, I don't know. We'll see what happens over the next little while. Especially when I move his The Bat! account over to IMAP, as we've been slowly but steadily migrating all of our user accounts from POP3 (client) IMAP (webmail) to IMAP only. Considering the way that his account has been acting, I'll probably hold off on it till the very end. I'm also reconsidering that 1Gb quota that some staff members were given. Realistically speaking, if large numbers of messages may cause Squirrelmail issues, it might be best to drop that down to 500Mb. -- Best regards, Diana Calder mailto:dcal...@essexcountylibrary.ca Automation Technician(519) 776-5241 x.131 Essex County Library Essex, ON - To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com
Re: [qmailtoaster] Qmail's handling of same account in both TO: and CC: headers
Wednesday, July 23, 2014, 3:45:47 PM, Angus wrote: If memory serves correctly, MTAs like qmail do not read the 'To' and 'Cc' headers at all. The 'To' and 'Cc' fields are written by the MUA (i.e. the email client) and constitute part of the message text delivered to the server by the DATA command. The server doesn't look inside that text at all. The thing that tells it where to deliver the message is an RCPT command which is sent as part of the SMTP session. snip Thank you for that very clear explanation of what's going on behind the scenes! I hadn't really considered the fact that the mail server doesn't actually look at the To: and Cc: headers directly. They're all just RCPT TO: as far as Qmail is concerned. The first question that comes to my mind is why he's adding the same email to both 'To' and 'Cc'. That just seems sloppy to me. Leaving that aside -- maybe he has a reason I have yet to be offered an actual reason for the behaviour. I'm thinking laziness. Or, as you suggested, a lack of knowledge. -- I did a manual telnet session to both a qmail server and to Gmail to see how they'd handle the case where successive RCPT commands name the same recipient. Qmail didn't blink when I told it to deliver to the same recipient three times, and did indeed deliver three messages. Gmail, on the other hand, said: 250 2.1.5 OK, duplicate recipients will be consolidated I haven't found any RFC's at all that specify that this is a required or even optional behavior. Implementing it does not seem to violate the RFCs (so long as the server sends a 250 response), but not implementing it doesn't seem to violate any either. I couldn't seem to find anything either but I'll freely admit to not being as familiar with the RFCs as I probably should be. That's the hazard of being a one-person IT department - when you have to swap out malfunctioning photocopier coin boxes, troubleshoot misbehaving receipt printers, maintain Win7 workstations, etc., etc., in addition to looking after all of the in-house Windows Linux servers, both real virtual, you tend to know a little bit about a lot of things but not nearly as much about any one thing as you'd like and sometimes need. Thank goodness for mailing lists and Google. I think he's correct that Gmail et all are smart enough to consolidate duplicate addresses, but that this is not a required behavior and Qmail is perfectly compliant. Well, at least Qmail isn't at fault in the sense of not complying with any RFCs. I'm of mixed feelings whether I agree with Gmail et al in deciding to consolidate duplicate recipients. Part of me thinks that it's a mail server's job to deliver exactly what it's instructed to deliver, as Qmail currently does, not to second-guess the sender and make its own decision regarding what to deliver. The rest of me thinks that it makes sense to consolidate duplicates because mistakes happen and, after all, who really needs 4 copies of the same message? I do, however, feel quite strongly that the sending program is very definitely at fault in addressing the messages redundantly in the first place and there's no good reason why it shouldn't be fixed. It manages to correctly send every other automated message just once to each recipient. I might be tempted to point out that other developers are smart enough not to address their messages redundantly, but that might lead to violence. You read my mind on that one. Now to figure out a way to more diplomatically imply the same thing. If, by chance, the developer proves unwilling or unable to fix the problem, does anyone know if there's any way to configure Qmail to follow Gmail's example and combine duplicate recipients? I've already talked to my supervisor about this and confirmed that neither one of us is going to agree to switch to Exchange or another smart server just to resolve this but HR thinks that it will be too confusing for staff to receive two copies of the email. -- Best regards, Diana Calder mailto:dcal...@essexcountylibrary.ca Automation Technician(519) 776-5241 x.131 Essex County Library Essex, ON - To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com
[qmailtoaster] One user account can't login to Squirrelmail
I have an odd problem with one user account. When trying to login to Squirrelmail, the login will hang for several seconds then result in: ERROR: ERROR: Connection dropped by IMAP server. Query: LOGOUT All other accounts that have been tested can login to Squirrelmail just fine. The problem user account can check mail in The Bat! (email client) via POP3 or via IMAP. I have used vuserinfo to compare the account settings against other, correctly working, accounts and there are no differences in the flags or limits. A possible symptom or secondary issue is that the problem account is using 78% of its 1Gb quota, despite the fact that the user has cleared out most of his old mail via the POP3 client (that's the same percentage as before he cleared out the old email). He has about 700 messages in his Inbox and about 500 in his Sent, which really doesn't seem like enough to add up to ~780Mb, even if some have attachments. I have double that many messages and it only comes out to 9% (90 Mb) of a 1Gb quota. As a side note - when we moved to a CentOS6 VM with the compatible version of Qmailtoaster, we made the switch from Courier to Dovecot at the same time. That appears to have left a number of Courier directories behind in each account's Maildir. Does anyone have a cleanup script to get rid of these obsolete directories? -- Best regards, Diana Calder mailto:dcal...@essexcountylibrary.ca Automation Technician(519) 776-5241 x.131 Essex County Library Essex, ON - To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com
[qmailtoaster] Qmail's handling of same account in both TO: and CC: headers
We are implementing a new piece of software to handle vacation requests. The program connects directly to our Qmail server's SMTP - no other mail servers are involved. Said software sends an email to the requester and their supervisor when the supervisor okays the vacation request. The requester currently receives the same email twice because the program puts the requester's email address in both the TO: and the CC: headers. The software developer and I are having a bit of a discussion regarding this. My position is that Qmail is doing its job correctly by delivering the email exactly as it is addressed and the problem lies in his program which is clearly incorrect in the way that it addresses the message. The developer's position is that our email server is at fault. He proved this by sending an email with his address in it 5 times (once in TO: and 4x in CC:). He claims that Qmail is at fault because other email servers (like Exchange and Gmail) are, and I quote, smart enough to recognize that all copies are for one person therefore instead of 5 emails only one copy is in my inbox. Because of this, getting him to fix his broken program is becoming somewhat of an issue. Just to confirm here - anybody have a handy RFC to prove that Qmail is actually doing what it should by delivering email as addressed and the other mail servers are actually behaving in a non-standard way by deciding that the emails are all the same and only delivering one copy? Or am I wrong and Qmail is indeed in the wrong by delivering exactly what the headers tell it to? -- Best regards, Diana Calder mailto:dcal...@essexcountylibrary.ca Automation Technician(519) 776-5241 x.131 Essex County Library Essex, ON - To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com
Re: [qmailtoaster] One user account can't login to Squirrelmail
Wednesday, July 23, 2014, 2:53:08 PM, Kelly wrote: Is the disable web access box checked if you look at the account in vqadmin? No, it isn't. I tried checking it, modifying the account, then unchecking and modifying the account again, just to make sure. No change. On 07/23/2014 13:57, Diana Calder wrote: I have an odd problem with one user account. When trying to login to Squirrelmail, the login will hang for several seconds then result in: ERROR: ERROR: Connection dropped by IMAP server. Query: LOGOUT -- Best regards, Diana Calder mailto:dcal...@essexcountylibrary.ca Automation Technician(519) 776-5241 x.131 Essex County Library Essex, ON - To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com
Re: [qmailtoaster] Re: /tmp/clamd.socket is in use by another process was Re: supervise: fatal: unable to start log/run: file does not exist
Hello Eric, Wednesday, July 2, 2014, 1:09:03 PM, you wrote: Sorry about the clamd/clamav confusion. The package name is clamav. You have the latest version from .qt., but I'm curious as to how you got the testing version, if that repo is disabled (as it should be now in most setups). I double-checked and it was disabled BUT I don't remember whether I ran a yum clean all after I changed it (nor do I remember exactly when I changed it), so I did a yum clean all and ran another yum update (there weren't any). That's where the the problem lies though. The testing version is the first version to include the init.d file for clamd instead of the supervise setup. I thought that rpm would remove the old supervise run file since it's not part of the package any more, but it appears I'll need to put some code in the rpm spec file to do that 'manually'. Ah. Okay, that makes sense. I think the best fix for you at this point will be to simply get rid of the /var/qmail/supervise/clamd/ directory. You might move it to /root/ as a backup rather than simply deleting it. It'd be safest to do this with qmail/supervise stopped, so that supervise doesn't get confused. You might then need to service clamd start to get clamd running before starting qmail back up. I did a reboot after moving the directory yesterday afternoon, just to make sure that everything works cleanly. That should fix it for you. Yes, the toaster ran happily overnight and was still fine this morning, so it looks like all is well. Thanks for testing this out, even though it was apparently inadvertent. We all appreciate your help. Well, at least we found the problem and resolved it relatively quickly. Thanks for the assistance! When you're a one-gal IT department, outside help is greatly appreciated when running into these sorts of situations. There's too many things on the server side of things that only come up once in a blue moon and I just don't remember exactly how to resolve them without a little assistance. Sometimes my Google-fu suffices but, for the times when it doesn't, lists like this one are essential! -- Best regards, Diana Calder mailto:dcal...@essexcountylibrary.ca Automation Technician(519) 776-5241 x.131 Essex County Library Essex, ON - To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com
Re: [qmailtoaster] Re: /tmp/clamd.socket is in use by another process was Re: supervise: fatal: unable to start log/run: file does not exist
Monday, June 30, 2014, 6:03:11 PM, Eric wrote: Yeah, it's trying to run from both supervise and init.d. That's what I thought - the question is, how do I fix this without accidentally making things worse? (Well, the *other* question is, what caused the problem in the first place, but at the moment I'm more interested in solving it.) Which clamd version is installed? [root@qmail ~]# yum list clamd Loaded plugins: fastestmirror, priorities, refresh-packagekit Loading mirror speeds from cached hostfile * base: less.cogeco.net * extras: less.cogeco.net * qmailtoaster-current: mirror2.qmailtoaster.com * qmailtoaster-current-nodist: mirror2.qmailtoaster.com * remi: rpms.famillecollet.com * rpmforge: ftp.heanet.ie * updates: mirror.science.uottawa.ca 162 packages excluded due to repository priority protections Available Packages clamd.x86_64 0.98.4-1.el6.rf rpmforge Okay, that was odd. One clamd package available but none installed. So, try a slight variation... [root@qmail ~]# yum list clam* Loaded plugins: fastestmirror, priorities, refresh-packagekit Loading mirror speeds from cached hostfile * base: less.cogeco.net * extras: less.cogeco.net * qmailtoaster-current: mirror2.qmailtoaster.com * qmailtoaster-current-nodist: mirror2.qmailtoaster.com * remi: rpms.famillecollet.com * rpmforge: ftp.heanet.ie * updates: mirror.science.uottawa.ca 162 packages excluded due to repository priority protections Installed Packages clamav.x86_64 0.98.4-0.qt.el6@qmailtoaster-testing Available Packages clamav-db.x86_640.98.4-1.el6.rfrpmforge clamav-devel.x86_64 0.98.4-1.el6.rfrpmforge clamav-milter.x86_640.98.4-1.el6.rfrpmforge clamd.x86_640.98.4-1.el6.rfrpmforge clamtk.noarch 4.25-1.el6.rf rpmforge Okay, looks like the package is actually clamav not clamd and I have version 0.98.4-0 installed. As for my qmailtoaster itself: Installed Packages qmailtoaster-release.noarch 2.0-1.qt.nodist installed Installed Packages qmailtoaster-util.noarch 2.0-1.qt.nodist @qmailtoaster-current-nodist qmailtoaster-testing is disabled in my repos and qmailtoaster-current is enabled (and set to a slightly higher priority than the testing repo back when I changed over from testing to current, just in case that made any difference). -- Best regards, Diana Calder mailto:dcal...@essexcountylibrary.ca Automation Technician(519) 776-5241 x.131 Essex County Library Essex, ON - To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com
[qmailtoaster] supervise: fatal: unable to start log/run: file does not exist
I'm running Qmailtoaster utilities on CentOS6 VM on a XenServer. Data is stored on NFS. Over the weekend, the VM went into Read-Only file system due to a lag in communication. I had to manually run FSCK (there were errors and I told it to fix them) and reboot after restoring it to Read-Write mode. After doing so, I had errors from supervise. I managed to find information in the archives to let me fix the clamd/run error but the other one still persists and I have no idea what else I can do to fix it. I get a continuous stream of supervise: fatal: unable to start log/run: file does not exist. Running qmailctl stat results in the following: clamd: up (pid 12127) 6 seconds log: up (pid 12138) 1 seconds send: up (pid 8239) 1037 seconds smtp: up (pid 8245) 1037 seconds spamd: up (pid 11877) 96 seconds submission: up (pid 8244) 1037 seconds clamd/log: up (pid 8240) 1037 seconds send/log: up (pid 8277) 1032 seconds smtp/log: up (pid 8246) 1037 seconds spamd/log: up (pid 12139) 1 seconds submission/log: up (pid 8273) 1032 seconds Mail appears to be working okay inbound and outbound but the stream of error messages continues. I'm stumped. I really don't want to have to backup the database, rollback to an old snapshot, and restore the database but I might have to. I've tried starting up a copy of an old snapshot on another VM to check for differences but can't find anything obvious. Suggestions? -- Best regards, Diana Calder mailto:dcal...@essexcountylibrary.ca Automation Technician(519) 776-5241 x.131 Essex County Library Essex, ON - To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com
Re: [qmailtoaster] Re: supervise: fatal: unable to start log/run: file does not exist
-- shows status of queue
alrm -- same as doqueue
hup -- same as reload
HELP
;;
*)
echo Usage: $0
{start|stop|restart|doqueue|reload|stat|pause|cont|cdb|queue|help}
exit 1
;;
esac
exit 0
I must be missing something but I can't figure out what. I don't see
anything here that should be causing the problem.
I've never paid very close attention to qmailctl stat results other
than up or not, but it looks to me like maybe clamd and spamd are
repeatedly stopping and restarting? They never seem to go above a few
(less than 10) seconds.
[root@qmail ~]# qmailctl stat
clamd: up (pid 12991) 1 seconds
send: up (pid 12874) 46 seconds
smtp: up (pid 12877) 46 seconds
spamd: up (pid 12878) 46 seconds
submission: up (pid 12879) 46 seconds
clamd/log: up (pid 12873) 46 seconds
send/log: up (pid 12876) 46 seconds
smtp/log: up (pid 12872) 46 seconds
spamd/log: up (pid 12992) 0 seconds
submission/log: up (pid 12880) 46 seconds
[root@qmail ~]# supervise: fatal: unable to start log/run: file does not exist
supervise: fatal: unable to start log/run: file does not exist
So, I have a server throwing a hissy fit and a holiday tomorrow.
Hopefully, it doesn't melt down before I find a fix.
Note for posterity, clamav and spamd are very soon to be changed to use
syslogd and initd instead of supervise and multilog. This is in
preparation for COS7, which will be using systemd, at which point
daemontools and ucscp-tcp will no longer be used by QMT.
The less custom stuff that has to be added to a system for QMT, the
better, as far as I'm concerned.
--
Best regards,
Diana Calder mailto:dcal...@essexcountylibrary.ca
Automation Technician(519) 776-5241 x.131
Essex County Library
Essex, ON
-
To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com
Re: [qmailtoaster] /tmp/clamd.socket is in use by another process was Re: supervise: fatal: unable to start log/run: file does not exist
Monday, June 30, 2014, 3:05:30 PM, Eric wrote: Unfortunately, the error message doesn't appear to say which log file it's having a problem with. I'm going to guess it's clamav, since that's being moved. I probably need to have the clamav package remove some leftover stuff. First, verify that clamav is logging to /var/log/maillog. If it's not, then I wonder which clamav package you have installed. It was installed by the qmailtoaster install script when the one for COS6 was still running from the testing repos. It is logging to /var/log/maillog. This should fix you up: # cd /var/qmail/supervise/clamd # mv log log.old Done. But... I'm guessing that'll take care of things. Nope, no such luck. Same error. However, once I removed log.old it cleared up the error when I did a qmailctl start - so, that's one problem solved. Unfortunately, now it's throwing an error: ERROR: LOCAL: Socket file /tmp/clamd.socket is in use by another process. Closing the main socket. Tried rebooting the VM and I spotted this in the bootup messages: Starting qmail-toaster: svscan. Starting sshd: [ OK ] Starting xinetd: [ OK ] Starting ntpd: [ OK ] Starting Clam AntiVirus Daemon: ERROR: LOCAL: Socket file /tmp/clamd.socket is in use by another process. Closing the main socket. [ OK ] Starting freshclam: [ OK ] Starting mysqld: [ OK ] Starting Dovecot Imap: [ OK ] Starting vusaged: started Starting httpd: [ OK ] Starting crond: [ OK ] Renamed /tmp/clamd.socket and started qmailctl - looked okay. Rebooted to check and the socket file in use error is back. So, is clamd trying to start twice? Once via svscan and once on its own? I did run a yum update when I first saw the errors, on the offchance that it would fix the problem - maybe something odd happened there? More testing... [root@qmail ~]# /etc/init.d/clamd stop ERROR: LOCAL: Socket file /tmp/clamd.socket is in use by another process. Closing the main socket. ERROR: LOCAL: Socket file /tmp/clamd.socket is in use by another process. Closing the main socket. [root@qmail ~]# /etc/init.d/clamd stop Stopping Clam AntiVirus Daemon: [ OK ] [root@qmail ~]# qmailctl stop Stopping qmail-toaster: svscan qmail logging. [root@qmail ~]# qmailctl start Starting qmail-toaster: svscan. [root@qmail ~]# ERROR: LOCAL: Socket file /tmp/clamd.socket is in use by another process. Closing the main socket. ERROR: LOCAL: Socket file /tmp/clamd.socket is in use by another process. Closing the main socket. qmailctl stop Stopping qmail-toaster: svscan qmail logging. [root@qmail ~]# /etc/init.d/clamd stop Stopping Clam AntiVirus Daemon: [ OK ] [root@qmail ~]# qmailctl start Starting qmail-toaster: svscan. [root@qmail ~]# ERROR: LOCAL: Socket file /tmp/clamd.socket is in use by another process. Closing the main socket. qmailctl stat clamd: up (pid 2678) 8 seconds send: up (pid 2562) 82 seconds smtp: up (pid 2569) 82 seconds spamd: up (pid 2571) 82 seconds submission: up (pid 2566) 82 seconds send/log: up (pid 2568) 82 seconds smtp/log: up (pid 2570) 82 seconds submission/log: up (pid 2567) 82 seconds So, clamd keeps starting and stopping and restarting. *sigh* Now what? -- Best regards, Diana Calder mailto:dcal...@essexcountylibrary.ca Automation Technician(519) 776-5241 x.131 Essex County Library Essex, ON - To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com
Re: [qmailtoaster] Re: Out of memory error sending from Squirrelmail on CentOS6
Hello Eric, Friday, April 11, 2014, 4:31:19 PM, you wrote: On 04/11/2014 01:02 PM, Diana Calder wrote: The Barracuda email firewall also forwards to port 25 - which ironically continued working fine despite getting absolutely hammered with checks for nonexistent accounts for a couple of hours earlier today. On a side note, I expect that spamdyke isn't doing you much good since you have an email firewall in front of it. I'd wager that you could remove the Barracuda firewall and do just as well with spamdyke on the perimeter. You've probably got bigger fish to fry right now though. Frankly, we'd probably be further ahead turning off spamdyke - the Barracuda is much easier to admin. A non-techie staff person monitors it and releases from quarantine any legitimate email that gets caught, whether for attachments or false positives. Spamdyke isn't nearly as slick to manage. Having said that, yes, I still have bigger fish to fry - and the squirrelmail issues are the least of my problems at the moment. I think we're on our second set of bad things happening in threes at the moment... -- Best regards, Diana Calder mailto:dcal...@essexcountylibrary.ca Automation Technician(519) 776-5241 x.131 Essex County Library Essex, ON - To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com
[qmailtoaster] Out of memory error sending from Squirrelmail on CentOS6
System is a CentOS6 x64 running the testing qmailtoaster (DK disabled) (in a VM on Citrix XenServer 6.2) This toaster has been up and running for a few weeks now and, to the best of my knowledge (I almost never use the webmail interface), outgoing mail from Squirrelmail WAS working fine up until yesterday. Yesterday, staff started seeing the following when trying to send an email from Squirrelmail: ERROR: Message not sent. Server replied: Service not available, closing channel 421 out of memory (#4.3.0) I've already tried increasing the softlimit - it didn't help. I've also tried increasing storage (from 8 to 16GB) and RAM (from 2 to 4GB) on the VM - also didn't help (didn't really expect it to but it was worth a shot). Sending messages works fine from a mail client, so the problem appears to be specific to Squirrelmail and/or port 587. Testing via telnet from the webserver confirms that port 587 is the culprit: [root@qmail tcprules.d]# telnet localhost 587 Trying ::1... telnet: connect to address ::1: Connection refused Trying 127.0.0.1... Connected to localhost. Escape character is '^]'. 220 qmail.essexcountylibrary.ca - Welcome to Qmail Toaster Ver. 1.3 SMTP Server ESMTP mail from:dcal...@essexcountylibrary.ca 421 out of memory (#4.3.0) Connection closed by foreign host. Here's the contents of /var/qmail/supervise/submission/run #!/bin/sh QMAILDUID=`id -u vpopmail` NOFILESGID=`id -g vpopmail` MAXSMTPD=`cat /var/qmail/control/concurrencyincoming` SMTPD=/var/qmail/bin/qmail-smtpd TCP_CDB=/etc/tcprules.d/tcp.smtp.cdb HOSTNAME=`hostname` VCHKPW=/home/vpopmail/bin/vchkpw export REQUIRE_AUTH=0 exec /usr/bin/softlimit -m 7500 \ /usr/bin/tcpserver -v -R -H -l $HOSTNAME -x $TCP_CDB -c $MAXSMTPD \ -u $QMAILDUID -g $NOFILESGID 0 587 \ $SMTPD $VCHKPW /bin/true 21 Suggestions?? -- Best regards, Diana Calder mailto:dcal...@essexcountylibrary.ca Automation Technician(519) 776-5241 x.131 Essex County Library Essex, ON - To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com
Re: [qmailtoaster] Out of memory error sending from Squirrelmail on CentOS6
I'm not sure whether this is related or not, however... Squirrelmail will not accept usern...@domain.com plus password for login - it will only accept username plus password: ERROR: ERROR: Connection dropped by IMAP server. Query: LOGOUT Connecting with a mail client, either format (usern...@domain.com or username) works. Obviously, I'd like to fix this as well but it's less urgent than the lack of ability to send email from Squirrelmail. I'm just not sure whether one may perhaps have something to do with the other... Diana Friday, April 11, 2014, 2:28:46 PM, you wrote: System is a CentOS6 x64 running the testing qmailtoaster (DK disabled) (in a VM on Citrix XenServer 6.2) This toaster has been up and running for a few weeks now and, to the best of my knowledge (I almost never use the webmail interface), outgoing mail from Squirrelmail WAS working fine up until yesterday. Yesterday, staff started seeing the following when trying to send an email from Squirrelmail: ERROR: Message not sent. Server replied: Service not available, closing channel 421 out of memory (#4.3.0) I've already tried increasing the softlimit - it didn't help. I've also tried increasing storage (from 8 to 16GB) and RAM (from 2 to 4GB) on the VM - also didn't help (didn't really expect it to but it was worth a shot). Sending messages works fine from a mail client, so the problem appears to be specific to Squirrelmail and/or port 587. Testing via telnet from the webserver confirms that port 587 is the culprit: [root@qmail tcprules.d]# telnet localhost 587 Trying ::1... telnet: connect to address ::1: Connection refused Trying 127.0.0.1... Connected to localhost. Escape character is '^]'. 220 qmail.essexcountylibrary.ca - Welcome to Qmail Toaster Ver. 1.3 SMTP Server ESMTP mail from:dcal...@essexcountylibrary.ca 421 out of memory (#4.3.0) Connection closed by foreign host. Here's the contents of /var/qmail/supervise/submission/run #!/bin/sh QMAILDUID=`id -u vpopmail` NOFILESGID=`id -g vpopmail` MAXSMTPD=`cat /var/qmail/control/concurrencyincoming` SMTPD=/var/qmail/bin/qmail-smtpd TCP_CDB=/etc/tcprules.d/tcp.smtp.cdb HOSTNAME=`hostname` VCHKPW=/home/vpopmail/bin/vchkpw export REQUIRE_AUTH=0 exec /usr/bin/softlimit -m 7500 \ /usr/bin/tcpserver -v -R -H -l $HOSTNAME -x $TCP_CDB -c $MAXSMTPD \ -u $QMAILDUID -g $NOFILESGID 0 587 \ $SMTPD $VCHKPW /bin/true 21 Suggestions?? -- Best regards, Diana Calder mailto:dcal...@essexcountylibrary.ca Automation Technician(519) 776-5241 x.131 Essex County Library Essex, ON - To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com
Re: [qmailtoaster] Re: Out of memory error sending from Squirrelmail on CentOS6
Friday, April 11, 2014, 3:26:42 PM, Eric wrote: Any reason why you have REQUIRE_AUTH=0 for submission? I'm guessing you just tried this to see if it remedied the error. Be sure to change it back. Hmm, I think that was actually in there by default. I don't recall changing it - and it's the same in the /var/qmail/supervise/smtp/run so I think it was the default. Either that or it was the setting on the old qmail server - would the backup and restore script have copied that across? Please try doubling softlimit, just for yuks. I doubt that will fix things though, as value for smtp on 64-bit appears to be 6400. Yes, it is. I tried that and it didn't help, so I pushed it up higher and it still didn't help. Just tried doubling it to 12800 - and yes, it's working. That's a pretty ridiculous number to need, considering how few people would actually be trying to send via squirrelmail at any given moment - maybe 2 or 3 messages on average? Can you authenticate successfully on port 25? You should be able to, (though it's not recommended). Yes, because port 25 is where the email clients connect to and those work just fine. Also tried via telnet - yes, port 25 works. And if I switch the email client to connect on 587, that doesn't work. The Barracuda email firewall also forwards to port 25 - which ironically continued working fine despite getting absolutely hammered with checks for nonexistent accounts for a couple of hours earlier today. The Barracuda bounced the spam but it still contacts the Qmail server to check for a valid recipient. So, that's working, at least for now - but I have a feeling there must be something else going on there. -- Best regards, Diana Calder mailto:dcal...@essexcountylibrary.ca Automation Technician(519) 776-5241 x.131 Essex County Library Essex, ON - To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com
Re: [qmailtoaster] Re: Out of memory error sending from Squirrelmail on CentOS6
Hello Eric, Friday, April 11, 2014, 3:28:10 PM, you wrote: Did you change anything from stock to be able to log in with only username? I don't recall off hand how that mechanism (default domain) works. Yes, I did. That's one of those sort of legacy things that came across from the previous setup - we had a lot of mail clients configured to use username only and I had to turn on access for either format until I get a chance to get out and change all of them (which will happen when I convert everyone over from POP3 to IMAP, which is being gradually rolled out as we see how well the system holds up to the change). The weird thing is that the old squirrelmail install required usern...@domain.com to work and this one requires the opposite. I suppose this could be related to the other problem. We'll see soon enough. ;) Apparently, it's not directly related as the ridiculously high bump on the softlimit fixed the other problem, at least for the time being. We'll see if things are still behaving on Monday. -- Best regards, Diana Calder mailto:dcal...@essexcountylibrary.ca Automation Technician(519) 776-5241 x.131 Essex County Library Essex, ON - To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com
[qmailtoaster] Problems with qtp-restore on CentOS6 x64
I don't think the problems that I ran into with qtp-restore actually have anything to do with CentOS6 x64 as they seem to be typos within the script but I'm mentioning the platform just in case. The server was set up using Dan's CentOS6 script a few months ago. I've just finally gotten around to copying the live server's info over for final testing prior to going live with the new server and discovered the issues with qtp-restore. After I got my backup file in the right place and ran the script, I ended up with some files missing. I couldn't login to Squirrelmail (still not resolved - looks like it's IMAP-related as can't connect to IMAP via client either - switching to Dovecot and we'll see if that resolves the problem) so I started poking around its (Squirrelmail's) config, then discovered the missing plugins. So I started investigating, realized that while they *were* part of the backup files, they hadn't been restored. So I started going through the qtp-restore script line-by-line. I discovered that, pretty much wherever there was a tar command, there were mistakes. For example, if the --directory option was used, there was a space rather than an = between --directory and the directory that it was supposed to restore to, while a lot of the other options (such as xjvf) were missing the leading - and so were throwing an error instead of restoring. Once I edited the script to correct the tar commands, it seems to have properly restored - I'm not missing any files anymore, at any rate - though I still don't have IMAP/Squirrelmail working, so we'll see...). -- Best regards, Diana mailto:dcal...@essexcountylibrary.ca - To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com
Re: [qmailtoaster] Squirrelmail alternatives? Looking for recs
Title: Re: [qmailtoaster] Squirrelmail alternatives? Looking for recs Friday, December 7, 2012, 7:33:18 PM, Carlos wrote: +1 afterlogic El dic 7, 2012 3:01 p.m., "David Bray" da...@brayworth.com.au escribió: after logic is my choice - I use the lite -http://www.afterlogic.org/ Its equally as easy as round cube to setup David Bray http://www.brayworth.com.au da...@brayworth.com.au Doneis better thanPerfect Can users do password changes and vacation responses within AfterLogic Lite? I already have that functionality working in Squirrelmail and can't very well *remove* functionality. (Password reset/reminder would be great too, but I don't think I've seen that working for any of the options, including Squirrelmail.) Thanks, Diana On 7/12/2012 3:24 AM, Diana Calder wrote: Anyone using something other than Squirrelmail for webmail with Qmailtoaster? I'm working my way through researching the options listed in the Wiki but I'd like to get some feedback from someone who's actually using one of the alternative webmail packages. So far, it looks like atmail is gone (the free community version, at least), and AfterLogic lite, eGroupware, Horde, and RoundCube all look like they're worth taking a deeper look at. I'd prefer something that looks a little less dated than Squirrelmail and that has a good mobile interface. Our Intranet is a hosted Noodle instance, so I'm not really interested in extra bells and whistles like calendars and such - just good solid email features like a decent address book (though a nice shared one in addition to personal ones would be nice), the ability to set a vacation response, basic filtering, and allowing individual users to change their password. eGroupware is probably overkill for our needs and even Horde may be a little over the top - but they're also the two nicest looking. I'll be continuing to research but some helpful comments from the Qmailtoaster community would be greatly appreciated. Hoping for some good recommendations, Diana -- Best regards, Diana mailto:dcal...@essexcountylibrary.ca - To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com
Re: [qmailtoaster] Re: Squirrelmail alternatives? Looking for recs
Thursday, December 6, 2012, 9:35:08 PM, Eric wrote: ES Why wouldn't you use the native mail program on an Ipad? Our staff can only reach their email from within our externally hosted Intranet. A link from there goes through a pass-through authentication proxy (which we run anyway for patron access to subscription databases) to reach our LAN and thence to Squirrelmail. That puts most of the burden of security on the outsourced Intranet rather than on our webmail server. Our firewall blocks outside SMTP and POP access to the Qmail server (as well as HTTP requests heading for anything other than the EZProxy server); incoming mail passes through the firewall to a Barracuda anti-spam device which then passes it off to the Qmail server. So, native mail programs on mobile devices aren't an option. Thus, the need for a solid webmail offering that works reasonably well on mobile devices. Most of our library staff only receive a handful of messages at their work address in a week - mostly shifts available and the occasional HR-related inquiry. Staff can access their mail adequately through webmail; there's no overwhelming *need* for them to have direct POP/IMAP/SMTP access, therefore it's highly unlikely that we'd open up the firewall to give that to them. The situation would most likely change if we were dealing with a high volume of messages per staff member. -- Best regards, Dianamailto:dcal...@essexcountylibrary.ca - To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com
[qmailtoaster] Squirrelmail alternatives? Looking for recs
Anyone using something other than Squirrelmail for webmail with Qmailtoaster? I'm working my way through researching the options listed in the Wiki but I'd like to get some feedback from someone who's actually using one of the alternative webmail packages. So far, it looks like atmail is gone (the free community version, at least), and AfterLogic lite, eGroupware, Horde, and RoundCube all look like they're worth taking a deeper look at. I'd prefer something that looks a little less dated than Squirrelmail and that has a good mobile interface. Our Intranet is a hosted Noodle instance, so I'm not really interested in extra bells and whistles like calendars and such - just good solid email features like a decent address book (though a nice shared one in addition to personal ones would be nice), the ability to set a vacation response, basic filtering, and allowing individual users to change their password. eGroupware is probably overkill for our needs and even Horde may be a little over the top - but they're also the two nicest looking. I'll be continuing to research but some helpful comments from the Qmailtoaster community would be greatly appreciated. Hoping for some good recommendations, Diana -- Best regards, Diana mailto:dcal...@essexcountylibrary.ca - To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com
Re: [qmailtoaster] QMT-CentOS6-12010.07.sh
Tuesday, December 4, 2012, 4:09 PM, Dan wrote:
G Greetings all...
G I've received a few requests lately from people wanting the latest
G QMT-CentOS6 script... the latest of which is attached (with the
G file extension changed to avoid being blocked by spam/av filters).
G Save the file, remove the .TXT from the name and run it as a bash
G script (as root: bash QMT-CentOS6-12.10.28.sh)
G Please provide feedback as to how well it works for you!
First attempt at the script: Started off fine, but quit with the
message No package courier-authlib-toaster-0.59.2-1.3.10.src.rpm
available.
So, I tried the script again with the -a option to see if I could
get more details. This time, it quit much sooner:
# bash QMT-CentOS6-12.10.28.sh -a
QMailToaster UNOFFICIAL Build/Update for RHEL/CentOS 6 - Version 2012.10.27
Building for x86_64 on CentOS release 6.3 (Final)
Removing conflicting mail packages... [ DONE ]
Updating existing packages...Loaded plugins: fastestmirror, priorities,
refresh-packagekit
Determining fastest mirrors
* base: less.cogeco.net
* centosplus: less.cogeco.net
* extras: less.cogeco.net
* updates: less.cogeco.net
base | 3.7 kB 00:00
base/primary_db | 4.5 MB 00:03
centosplus | 3.5 kB 00:00
centosplus/primary_db| 1.8 MB 00:01
extras | 3.5 kB 00:00
extras/primary_db| 23 kB 00:00
updates | 3.5 kB 00:00
updates/primary_db | 4.1 MB 00:03
56 packages excluded due to repository priority protections
Setting up Update Process
No Packages marked for Update [ DONE ]
Checking for EPEL repository... [ DONE ]
Checking for RPMforge/RepoForge... [ DONE ]
Verifying CentOS Dependencies... [ -OK- ]
Verifying Perl Dependencies in EPEL...Loaded plugins: fastestmirror,
priorities, refresh-packagekit
Loading mirror speeds from cached hostfile
* base: less.cogeco.net
* centosplus: less.cogeco.net
* epel: mirror.steadfast.net
* extras: less.cogeco.net
* updates: less.cogeco.net
146 packages excluded due to repository priority protections
Setting up Install Process
No package razor-agents available.
Error: Nothing to do
QMT-CentOS6-12.10.28.sh: Exiting from YUM error
Used RPMBone to search for razor-agents - turned out that it's on
RPMForge, but not EPEL. Edited the script accordingly and ran it again.
Checking for EPEL repository... [ DONE ]
Checking for RPMforge/RepoForge... [ DONE ]
Verifying CentOS Dependencies... [ -OK- ]
Verifying Perl Dependencies in EPEL... [ -OK- ]
Verifying Perl Dependencies in RepoForge...Loaded plugins: fastestmirror,
priorities, refresh-packagekit
Loading mirror speeds from cached hostfile
* base: less.cogeco.net
* centosplus: less.cogeco.net
* extras: less.cogeco.net
* rpmforge: mirror.us.leaseweb.net
* updates: less.cogeco.net
rpmforge | 1.9 kB 00:00
69 packages excluded due to repository priority protections
Setting up Install Process
Resolving Dependencies
-- Running transaction check
--- Package razor-agents.x86_64 0:2.85-1.el6.rf will be installed
-- Processing Dependency: perl-Razor-Agent = 2.85-1.el6.rf for package:
razor-agents-2.85-1.el6.rf.x86_64
-- Finished Dependency Resolution
Error: Package: razor-agents-2.85-1.el6.rf.x86_64 (rpmforge)
Requires: perl-Razor-Agent = 2.85-1.el6.rf
Installed: perl-Razor-Agent-2.85-6.el6.x86_64 (@epel)
perl-Razor-Agent = 2.85-6.el6
Available: perl-Razor-Agent-2.84-1.el6.rf.x86_64 (rpmforge)
perl-Razor-Agent = 2.84-1.el6.rf
Available: perl-Razor-Agent-2.85-1.el6.rf.x86_64 (rpmforge)
perl-Razor-Agent = 2.85-1.el6.rf
You could try using --skip-broken to work around the problem
** Found 4 pre-existing rpmdb problem(s), 'yum check' output follows:
qmailadmin-toaster-1.2.16-1.4.0.x86_64 has missing requires of
control-panel-toaster = ('0', '0.2', None)
qmailmrtg-toaster-4.2-1.3.7.x86_64 has missing requires of
control-panel-toaster = ('0', '0.2', None)
ucspi-tcp-toaster-0.88-1.3.9.x86_64 has missing requires of daemontools-toaster
= ('0', '0.76', '1.2.2')
vqadmin-toaster-2.3.7-1.4.1.x86_64 has missing requires of
control-panel-toaster = ('0', '0.2', None)
QMT-CentOS6-12.10.28.sh: Exiting from YUM error
So - yum remove to get rid of perl-Razor-Agent with the problematic
version number, edited the script again to use RPMForge for
perl-Razor-Agent as well. Re-ran the script. All is well until:
Checking courier-authlib-toaster-0.59.2-1.3.10.src.rpm [FAILED]
Check /tmp/courier-authlib-toaster-0.59.2-1.3.10.log
[root@qmail2012 ~]# cat
Re: [qmailtoaster] QMT-CentOS6-12010.07.sh
Okay, now I'm really confused. It failed on missing dependencies that were actually listed in the script and therefore shouldn't have been missing. Wednesday, December 5, 2012, 1:11:39 PM, Diana wrote: DC All is well until: DC Checking courier-authlib-toaster-0.59.2-1.3.10.src.rpm [FAILED] DC Check /tmp/courier-authlib-toaster-0.59.2-1.3.10.log DC [root@qmail2012 ~]# cat /tmp/courier-authlib-toaster-0.59.2-1.3.10.log DC warning: line 452: buildprereq is deprecated: BuildPreReq: /usr/include/ltdl.h DC warning: line 453: buildprereq is deprecated: DC BuildPreReq:libtool, mysql-devel, zlib-devel, gdbm-devel, expect, gcc-c++ DC warning: line 454: buildprereq is deprecated: DC BuildPreReq:qmail-toaster = 1.03-1.3.15 DC error: Failed build dependencies: DC libtool is needed by courier-authlib-toaster-0.59.2-1.3.10.x86_64 DC expect is needed by courier-authlib-toaster-0.59.2-1.3.10.x86_64 DC Installing courier-authlib-toaster-0.59.2-1.3.10.src.rpm DC *Sigh*. Back to the original source of the script failure. At least DC this time I got the details that I was looking for - now I just have DC to figure out how to deal with them. Both libtool and expect are already listed in the script under dependencies - so why aren't they being installed? I'll leave figuring that one out to someone else. Did a manual yum install for both libtool and expect, then ran the script again. Took a really, really, *really* long time building courier-imap-toaster but finally succeeded. The next place that the script died was: Installing QMail Toaster Plus scriptsQMT-CentOS6-12.10.28.sh: unable to get qmailtoaster-plus repo - fix re-try Waited a half hour or so then re-ran the script with and this time it worked. All-in-all, a few glitches, but utimately successful. Thanks Dan! -- Best regards, Dianamailto:dcal...@essexcountylibrary.ca - To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com
Re: [qmailtoaster] Re: qtp-newmodel failing
Friday, November 30, 2012, 10:50:33 AM, Eric Shubert wrote: ES On 11/06/2012 01:31 PM, Diana Calder wrote: I'm trying to run qtp-newmodel on CentOS 4.9 (originally set up a few years ago from a QMail Toaster ISO). Unfortunately, it's not working. ES For starters, please check the date/time on your computer. It appears to ES be about 3 weeks slow. ;) No, actually the date/time issue is because the first time that I sent this, it was rejected by the list due to a reverse DNS issue that we've been having. Very weird - the records all looked fine and even passed *some* of the online mx record checking tools but failed others. After running a batch of yum updates (including some BIND-related ones) on our CentOS 6 external DNS server, the reverse DNS magically started working. At which point, I resent this message and it finally went through. When I rebuild our new QMail Toaster, it's definitely getting PowerDNS, not BIND. And I'm seriously considering switching our actual DNS servers over to PowerDNS as well - I've seen too many weird and inexplicable BIND issues magically appear on previously perfectly-working boxes (and, sometimes, just as magically disappear again) to be completely satisfied with continuing to use it. ES Please update your qmailtoaster-plus.repo package. I think that's where ES your problem lies. ES http://qtp.qmailtoaster.com/trac/wiki/WikiStart#a1-InstallQTPRepository ES After that, you should also do ES # yum update qmailtoaster-plus ES to be sure that's up to date. Done. However, now I'm getting this when I run qtp-newmodel: Issuing command: qtp-newmodel qtp-newmodel v0.3.18 starting Tue Dec 4 10:07:21 EST 2012 qtp-whatami v0.3.8 Tue Dec 4 10:07:21 EST 2012 REAL_DIST=CentOS DISTRO=CentOS OSVER=4.9 QTARCH=i686 QTKERN=2.6.9-103.ELsmp BUILD_DIST=cnt40 BUILD_DIR=/usr/src/redhat This machine's OS is supported and has been tested Let's get on with it! The following packages have already been selected: daemontools-toaster-0.76-1.3.6.src.rpm ucspi-tcp-toaster-0.88-1.3.9.src.rpm vpopmail-toaster-5.4.33-1.4.0.src.rpm qmail-toaster-1.03-1.3.22.src.rpm courier-authlib-toaster-0.59.2-1.3.10.src.rpm courier-imap-toaster-4.1.2-1.3.10.src.rpm autorespond-toaster-2.0.5-1.4.0.src.rpm control-panel-toaster-0.5-1.4.0.src.rpm qmailadmin-toaster-1.2.16-1.4.0.src.rpm qmailmrtg-toaster-4.2-1.3.7.src.rpm spamassassin-toaster-3.3.2-1.4.3.src.rpm simscan-toaster-1.4.0-1.4.0.src.rpm vqadmin-toaster-2.3.7-1.4.1.src.rpm Do you want to process this selection? Shall we continue? (yes, no|skip, batch, quit) [y] / n|s / b / q : y Getting source packages ...(this may take a while) daemontools-toaster-0.76-1.3.6.src.rpm is already downloaded, bypassed ucspi-tcp-toaster-0.88-1.3.9.src.rpm is already downloaded, bypassed vpopmail-toaster-5.4.33-1.4.0.src.rpm is already downloaded, bypassed qmail-toaster-1.03-1.3.22.src.rpm is already downloaded, bypassed courier-authlib-toaster-0.59.2-1.3.10.src.rpm is already downloaded, bypassed courier-imap-toaster-4.1.2-1.3.10.src.rpm is already downloaded, bypassed autorespond-toaster-2.0.5-1.4.0.src.rpm is already downloaded, bypassed control-panel-toaster-0.5-1.4.0.src.rpm is already downloaded, bypassed qmailadmin-toaster-1.2.16-1.4.0.src.rpm is already downloaded, bypassed qmailmrtg-toaster-4.2-1.3.7.src.rpm is already downloaded, bypassed spamassassin-toaster-3.3.2-1.4.3.src.rpm is already downloaded, bypassed simscan-toaster-1.4.0-1.4.0.src.rpm is already downloaded, bypassed vqadmin-toaster-2.3.7-1.4.1.src.rpm is already downloaded, bypassed qtp-dependencies v0.3.2 qtp-install-rpmforge v0.4.0 - getting latest version of rpmforge-release ... qtp-install-rpmforge - https://raw.github.com/repoforge/rpms/master/specs/rpmfor ge-release/rpmforge-release.spec not found, please try again later. qtp-dependencies - installing compat-gcc-34 compat-gcc-34-c++ compat-glibc comp at-glibc-headers compat-libf2c compat-libgcc compat-libstdc++-296 compat-libsdc+ +-33 libtool-ltdl libtool-ltdl-devel php-ldap ... Loading priorities plugin Setting up Install Process Setting up repositories Reading repository metadata in from local files 274 packages excluded due to repository priority protections Parsing package install arguments No Match for argument: compat-gcc-34 No Match for argument: compat-gcc-34-c++ No Match for argument: compat-libf2c No Match for argument: compat-libgcc No Match for argument: compat-libsdc++-33 No Match for argument: libtool-ltdl No Match for argument: libtool-ltdl-devel Resolving Dependencies -- Populating transaction set with selected packages. Please wait. --- Package php-ldap.i386 0:4.3.9-3.36 set to be updated --- Package compat-glibc-headers.i386 1:2.3.2-95.30 set to be updated --- Package compat-libstdc++-296.i386 0:2.96-132.7.2 set to be updated --- Package compat-glibc.i386 1:2.3.2-95.30 set to be updated -- Running transaction check -- Processing Dependency: php = 4.3.9-3.36 for package: php-ldap -- Finished Dependency Resolution Error: Missing
Re: [qmailtoaster] Re: qtp-newmodel failing
Hello Eric, Tuesday, December 4, 2012, 11:02:26 AM, you wrote: ES On 12/04/2012 08:21 AM, Diana Calder wrote: -- Running transaction check -- Processing Dependency: php = 4.3.9-3.36 for package: php-ldap -- Finished Dependency Resolution Error: Missing Dependency: php = 4.3.9-3.36 is needed by package php-ldap qtp-dependencies - installation of base dependencies failed, exiting qtp-newmodel - dependent packages processing failed, exiting --- Hit ENTER to return to menu --- When I do a yum list php I get: Loading priorities plugin Setting up repositories Reading repository metadata in from local files 274 packages excluded due to repository priority protections Installed Packages php.i386 4.3.11-2.8 installed Available Packages php.i386 4.3.9-3.36 update So, in other words, I would need to downgrade php, right? Urgh. That won't be fun. ES I've no idea what php-ldap is doing in the dependency list. QTP doesn't ES use it at all that I'm aware of. It's not on my system. I'd try removing ES qtp-ldap from the qtp-dependencies script, then re-try qtp-newmodel. Let ES us know how this works. Removing qtp-ldap from the qtp-dependencies script let qtp-newmodel run successfully. (Finally!) So far, everything looks okay. Maybe I'll just have to leave this Qmail server as-is and cross my fingers that being on different versions won't cause any issues when I migrate over to the new Qmail server... ES Perhaps, but I'd try getting QTP upgraded if possible. It'll make your ES migration simpler (fewer variables). There are a couple recent vpopmail ES database changes that I'd be cautious of. Vpopmail in general would be ES my biggest concern migrating from previous QTP versions. Yeah, I really didn't want to migrate between different versions if I could avoid it. I wasn't sure whether there wasy anything in there that would matter but I figured that Murphy's Law would rule if there was the slightest chance of a problem. Speaking of which - where does the CentOS6 Qmailtoaster situation stand? Is official support for Qmailtoaster on CentOS6 close or still some months off? I'd rather use CentOS6 instead of CentOS5 but the new hardware is here and I need to get it set up, so if CentOS6 support is still more than a week or two away, I'll have to go with 5. ES I'm swamped until January at least, so don't expect the official COS6 ES release before 13Q1. Busy time of year for everyone, I think, so I'm not exactly surprised that it's going to be a bit before the official release. ES That being said, I would go ahead with COS6 in your situation. There are ES several folks here that are running QMT on production COS6 hosts. Dan ES even has a script that takes care of things that need to be changed. ES There's not much difference really. I was hoping to be able to use COS6 as I hopefully won't need to rebuild the Qmail server for a very, very long time since this time it's going in a VM on Citrix Xenserver rather than on a physical box. It will be the first of our servers to make that switch. I've sent Dan an offlist email regarding his script since both mirror4.qmailtoaster.com and mirror9 (the two locations he'd said that the script could be downloaded from) seem to no longer exist. So, unless someone has a copy of it that they can make available, I'll have to wait to hear back from him before I can get too far with the new Qmail server. ES Please keep us posted on your progress. Well, the qmailtoaster on the old server is now up to date and I'm getting started on the CentOS6 minimal install on the new server. With a little luck and a quick response regarding Dan's script, I hope to get the new server at least as far as the testing phase by the end of the week. If I'm really lucky, I might even manage to get the migration done (there's less than 100 accounts on the Qmail install, so it shouldn't take too long to back up and migrate). Thanks for the assistance, Diana -- Best regards, Dianamailto:dcal...@essexcountylibrary.ca - To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com
[qmailtoaster] qtp-newmodel failing
I'm trying to run qtp-newmodel on CentOS 4.9 (originally set up a few years ago from a QMail Toaster ISO). Unfortunately, it's not working. Here's what I'm getting: [root@qmail ~]# qtp-newmodel qtp-newmodel v0.3.18 starting Tue Nov 6 15:26:25 EST 2012 qtp-whatami v0.3.8 Tue Nov 6 15:26:25 EST 2012 REAL_DIST=CentOS DISTRO=CentOS OSVER=4.9 QTARCH=i686 QTKERN=2.6.9-89.0.20.ELsmp BUILD_DIST=cnt40 BUILD_DIR=/usr/src/redhat This machine's OS is supported and has been tested Let's get on with it! The following packages have already been selected: daemontools-toaster-0.76-1.3.6.src.rpm ucspi-tcp-toaster-0.88-1.3.9.src.rpm vpopmail-toaster-5.4.33-1.4.0.src.rpm qmail-toaster-1.03-1.3.22.src.rpm courier-authlib-toaster-0.59.2-1.3.10.src.rpm courier-imap-toaster-4.1.2-1.3.10.src.rpm autorespond-toaster-2.0.5-1.4.0.src.rpm control-panel-toaster-0.5-1.4.0.src.rpm qmailadmin-toaster-1.2.16-1.4.0.src.rpm qmailmrtg-toaster-4.2-1.3.7.src.rpm spamassassin-toaster-3.3.2-1.4.3.src.rpm simscan-toaster-1.4.0-1.4.0.src.rpm vqadmin-toaster-2.3.7-1.4.1.src.rpm Do you want to process this selection? Shall we continue? (yes, no|skip, batch, quit) [y] / n|s / b / q : y Getting source packages ...(this may take a while) daemontools-toaster-0.76-1.3.6.src.rpm is already downloaded, bypassed ucspi-tcp-toaster-0.88-1.3.9.src.rpm is already downloaded, bypassed vpopmail-toaster-5.4.33-1.4.0.src.rpm is already downloaded, bypassed qmail-toaster-1.03-1.3.22.src.rpm is already downloaded, bypassed courier-authlib-toaster-0.59.2-1.3.10.src.rpm is already downloaded, bypassed courier-imap-toaster-4.1.2-1.3.10.src.rpm is already downloaded, bypassed autorespond-toaster-2.0.5-1.4.0.src.rpm is already downloaded, bypassed control-panel-toaster-0.5-1.4.0.src.rpm is already downloaded, bypassed qmailadmin-toaster-1.2.16-1.4.0.src.rpm is already downloaded, bypassed qmailmrtg-toaster-4.2-1.3.7.src.rpm is already downloaded, bypassed spamassassin-toaster-3.3.2-1.4.3.src.rpm is already downloaded, bypassed simscan-toaster-1.4.0-1.4.0.src.rpm is already downloaded, bypassed vqadmin-toaster-2.3.7-1.4.1.src.rpm is already downloaded, bypassed qtp-dependencies v0.3.2 qtp-install-rpmforge v0.4.0 - getting latest version of rpmforge-release ... qtp-install-rpmforge - https://raw.github.com/repoforge/rpms/master/specs/rpmfor ge-release/rpmforge-release.spec not found, please try again later. qtp-dependencies - installing perl(Archive::Tar) perl(Encode::Detect) perl(IO:: Socket::INET6) perl(IO::Socket::SSL) perl(IP::Country::Fast) perl(Mail::DKIM) pe rl(Mail::SPF) perl(Net::Ident) perl(NetAddr::IP) perl(Razor2::Client::Agent) ... Loading priorities plugin Setting up Install Process Setting up repositories http://qtp.qmailtoaster.com/repos/repodata/repomd.xml: [Errno 14] HTTP Error 404 : Not Found Trying other mirror. Cannot open/read repomd.xml file for repository: qmailtoaster-plus failure: repodata/repomd.xml from qmailtoaster-plus: [Errno 256] No more mirrors to try. Error: failure: repodata/repomd.xml from qmailtoaster-plus: [Errno 256] No more mirrors to try. qtp-dependencies - installation of dependent packages failed, exiting qtp-newmodel - dependent packages processing failed, exiting Help?! I'm aware that support for CentOS 4 has ended and I want to get the current CentOS 4.9 and Qmail fully updated in preparation for backup and migration to either CentOS 5 or 6 (depending on whether Qmail Toaster is quite ready for CentOS 6 by the time that I'm ready to make the move). -- Best regards, Diana mailto:dcal...@essexcountylibrary.ca - To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com
