Jake Vickers wrote:
Dan McAllister wrote:
Jake...
I DO have a bad habit of reading the documentation -- I use the
vqadmin program solely for retrieving passwords when idiot users
"forget" them -- usually the day after they have reset them for some
odd reason.
I have no doubt, and hope you do read the sparse docs we've put
together. The number 217-whatever is just one that I can reproduce
consistently with vqadmin.
If you created the domains via the CLI (and I'm assuming the values
are correct at that time) and they change later.... That's an
interesting one. Is the mysql DB on a different machine as well? I'm
starting to suspect something awry with either a DB being on a
different machine, or the filesystems being on a different machine. I
know there was an issue with MySQL5 when it came out, and I think the
end-result patch just "pings" the DB every so often to keep the
connection alive. Before that everyone was getting cannot connect to
DB messages.
Most clients have just the one server (most are dual-core Opterons, some
dual-CPU/dual-core (4 total cores) Opterons -- most are spec'd to 2GB
RAM per core). Those that have multiple servers have added an MS Windoze
Server 2000 or 2003 SBS. Even in those instances, the MySQL remains on
the Linux server. (My QMail Toasters are running on a Fedora Core 5
derivative -- loads of my own customizations that allow me to sell the
server as a service, and remotely administer the system as if it is just
1 instance of the same server over and over again. (Keeps me sane).
When a client asks for a new domain to be hosted on their system,
they submit a request via email. At that time, we add the domain to
their DNS, create a space for the web pages to be hosted, create an
admin account group for the new domain (who are able to edit the web
pages), and lastly create the email domain (vadddomain).
If you're PHP savvy this could be scripted. I have a bash script I
use to create new domains for my clients. It asks for the name, number
of mailboxes, quota, etc. and then creates it for me.
I'm an old-time UNIX guy -- I actually do all those steps in a
custom-built BASH script. As such, I'm inclined to leave it as-is now.
Make clients call in to add domains so I have more hands-on with them.
I actually then add a couple of items:
1) I set the postmaster account to point to MY postmaster account --
I read the postmaster mail for all domains I administer, whether on
my own server or a client's
2) I create an admin user mailbox (usually the owner of the company)
and set the password to something we've agreed upon earlier
3) I create webmaster and abuse aliases for my own webmaster and
abuse email mailboxes (on my own domain) -- same reason as for
postmaster
4) I email the client a PDF document that tells them how to log into
qmailadmin on their new webpage, how to use THEIR account (not
postmaster) and a brief primer on how to create each type of account
(mailbox, alias, responder, and list). They can always call for
additional support -- but the issues that new users bring up are
usually added to our PDF document so we don't have to answer it again!
Good ideas. I leave it up to the clients for their bounce messages and
what-not. 'Course I also set up and maintain their in-house networks,
networks in other states to connect back to the home office, VoIP
phone systems, I also do custom projects (http://thebuildercam.com/ as
an example, which I built from the ground up in my garage), etc., so I
don't feel guilty watching over their stuff as much. My biggest
problem right now is AOL. They recently changed their servers, and I
chase phantom-bounces all the time for 1 client who "checks the mail
server" for me - 50 times a day. 2 weekends ago he only got 50 emails
on a Sunday and was sending me text messages to my phone because he
said the email server was broke. He normally averages 150-200 messages
a day and figured that 100 or so had "gotten lost somewhere". It was
just a light day. He didn't know of any emails that actually bounced,
but he figured there had to be some. <sigh>
AOL is a pain -- but that's their history! "Why run ON the Internet when
you can build your own, internally housed, completely customized, uniq
Internet all right here! That way you're not hampered by anything like
/standards!/" (I think they thought they could out-Microsoft Microsoft
-- you know: "The E3 Strategy - Embrace, Extend, Exterminate"! :-)
I also offer a broad range of programs, mostly tailored to small to
mid-sized businesses, and specializing in non-centric environments (lots
of VPN clients, VoIP phone systems that allow users to roam across the
world and still make and receive "local" calls from the "Main Office"
and the like) all needing high availability and high data security.
Which brings me back to my current issue... this client is STILL
without email this evening, and I'm looking like an idiot because
I've checked everything I know how to check...
Are there NO CLI diagnostics that can try to find out why (or just as
importantly) WHERE qmail-smtp is failing to find the account???
You can use recordio to see what qmail-smtp is doing, and maybe see
where the break is. I've been traveling the last few days so I haven't
kept up on the threads much. What OS and version? Behind a NAT
firewall or public? Are just the /home and /backup dirs on NFS?
Thanks.
Turns out the error is now coming from qmail-send (earlier it was
qmail-smtp, but the MySQL fix seems to have gotten it thru qmail-smtp
and on to qmail-send.
The exact error message in QMLOG send is:
2007-07-17 10:06:40.201173500 new msg 2261131
2007-07-17 10:06:40.201177500 info msg 2261131: bytes 1551 from
<[EMAIL PROTECTED]> qp 21254 uid 89
2007-07-17 10:06:40.211859500 starting delivery 9: msg 2261131 to local
[EMAIL PROTECTED]
2007-07-17 10:06:40.211864500 status: local 1/10 remote 0/60
2007-07-17 10:06:40.215288500 delivery 9: failure:
Sorry,_no_mailbox_here_by_that_name._(#5.1.1)/
2007-07-17 10:06:40.215294500 status: local 0/10 remote 0/60
2007-07-17 10:06:40.229608500 bounce msg 2261131 qp 21257
2007-07-17 10:06:40.229613500 end msg 2261131
You're not that far from me. My office is in Orlando, but I'm moving
to North Carolina this month. I'll still be in Orlando a couple days a
month though, since that's where the bulk of my clients are right now.
I realized that a few months back... so you're evacuating to NC like all
the rest, eh? My parents left for NC about 10 years ago (outside of
Cashiers, NC these days). So many ex-Floridians in NC, they're going to
have to build a new Disney up there! :-)
