Re: [vchkpw] Why does Inter7 opt Qmail?
Guys, let me explain why I'm asking this. My boss (not me) has doubts about Qmail. He wants me to search for new mailservers of mail solutions like, for example, outsourcing the mail function. So I'm asking this now to have more arguments to convince him to stay with Qmail. My boss (and me) esteem Inter7 and we'd like to hear from you the answer of this question. Regards, bnegrao Hi Inter7 and everybody, I'd like to know why do you opt Qmail as your mailserver? Why not Postfix? Why not Qmail-ldap? Why not any other that I don't know about? Would you work with some other mailserver? If so, which one? Thank you in advance,
Re: [vchkpw] Why does Inter7 opt Qmail?
does your boss have a rationale for his doubts, or are they based upon a 'gut' feeling? usually doubts arise based upon shortcomings. what shortcoming does your boss see in qmail (note, small 'q' - it is not Qmail). OK. He wants to know if there is a tendency on the market for some other mailserver. He asks me what mailservers the biggest linux/Unix distributors are using on their products. For example, what's the mailserver shipped with RedHat, Solaris, Mandrake, Debian, etc? I really don't know. I believe all of them are shipped only with Sendmail, but I'm not sure on this actually. Do you know that? Thank you very much, Bruno.
Re: [vchkpw] Why does Inter7 opt Qmail?
Hi everybody, Thank you very much for the info. Let me tell more info about us. We already use Qmail in our 6 mailservers for 4 years. I installed all of them. I even wrote http://www.qmailwiki.org/Simscan/Related_Docs/Simscan_ClamAV_Chkuser_Installation_Guide What means I'm used to the Qmail+Inter7-tools+Patches lifestyle, I know it works. Let me tell you some things we(specially him) don't like in Qmail, some of them were already mentioned: 1) the fact that qmail stopped being developed so every improvement has to be made craftily: applying patches, install a bunch of administrative tools, install antivirus, etc. All these procedures are made manually, there's no Super Qmail 2005 package, with all the pieces already gathered. 2) a lot of research is needed to find how to install each improvement. This time could be used for other things, of course. So there is a cost here. 3) We don't have personnel and don't intend to dedicade C programmers to develop patches for qmail by ourselves. My boss actually dreams on making us a mail outsourcer for other companies.We are already a small ISP, but he dreams about our customers stop using their MS Outlook's to use our supposed beautiful webmail/domain-administration solution of his dreams. So he wants to know if there is something already close to it on the open-source market. He wants to know if there is something ready. (don't get mad with me, I'm just researching what he asked) What's bad on inter7 tools? For example, my boss thinks Sqwebmail is ugly, and it really is. But, IMP is a pain in the ass to set it up. We substituted Sqwebmail to IMP, but when I have to update IMP I almost break down and cry. Sqwebmail is easy and ugly, IMP is handsome and very complicated to install. But we're happy with Qmailadmin though. But could be nicer if Sqwebmail and Qmailadmin were integrated and very good looking, providing a continuos look and feel pattern. I want to comment what Kyle said here: But look at it this way: there's nothing in the license that says you can't take qmail, rename it to (mySweetMailserver, for example), and release it under the GPL. That nobody's done that says something. I don't understand about licensing, but I researching on Qmail-ldap, I heard it is licensed under BSD which is DFSG-free - having this licensing, could it be shipped with the distributions? Do you have some opinion on Qmail-ldap? Some ideas with webmail applications and domain administration? Best regards, bnegrao
Re: [vchkpw] Why does Inter7 opt Qmail?
I don't understand about licensing, but I researching on Qmail-ldap, I heard it is licensed under BSD which is DFSG-free - having this licensing, could it be shipped with the distributions? Do you have some opinion on Qmail-ldap? Mmm, not exactly. Qmail-ldap is based on qmail (as I understand, it's a big patch to qmail). The patch itself has a license (BSD) which is separate from qmail-proper. However, I've never used qmail-ldap. Though all my account information is stored in ldap, I've stuck with using vpopmail's ldap support. Yes, qmail-ldap is a big patch to qmail. You just install qmail, apply qmail-ldap and you have qmail+a lot of features including antispam, chkuser, QMAILQUEUE, etc. With ldap backend for everything. In qmail-ldap, every mail account has a mailhost attribute that says in what server the Maildir for that particular user should be. This feature enables you to set up a central MX 0 for your domain who will receive all the e-mail for that domain, and then it will forward the messages to their final destinations in remote qmail-ldap servers, all of them sharing the same domain name. My dream (not of my boss) is if Inter7 started developing its nice tools for qmail-ldap too. So I could create a user account in my central mailserver in new york using vadduser with the following 3 parameters form: vadduser [EMAIL PROTECTED] jonhspassword saopaulo.myenterprise.com.br This means that every email to [EMAIL PROTECTED] goes to the MX 0 in NY and then it's forwarded to the mailserver of the brazilian office. What qmail-ldap lacks now, in my opinion, are the Inter7 tools. And maybe, i don't know, Inter7 can be lacking qmail-ldap too. Well, at least this is my dream... Regards, bruno.
[vchkpw] Why does Inter7 opt Qmail?
Hi Inter7 and everybody, I'd like to know why do you opt Qmail as your mailserver? Why not Postfix? Why not Qmail-ldap? Why not any other that I don't know about? Would you work with some other mailserver? If so, which one? Thank you in advance, - Bruno Negrao - Network Manager Engepel Teleinformática. 55-31-34812311 Belo Horizonte, MG, Brazil
[vchkpw] SOLVED: Re: [vchkpw] Re: Request for new feature: Internal-only accounts
Inter7 launched eMPF. Was eMPF inspired by this thread? Regards, bnegrao
Re: [vchkpw] What causes bounce messages to be sent to forged addresses?
Hi Casey,
I don't know if I understood very well all these evidences you have shown. But
appears to me you are not using the Chkuser patch, right? If not, chkuser is a
patch to qmail-smtpd that enables it to check the existence of a local user
before accepting the message. Without it, qmail-smtpd has to accept every
message destined to its local domains, and try to deliver the messages later. If
the delivery fails, because the user doesn't exist, qmail will try to bounce the
message to the sender, even if it's fake.
Chkuser also adds a lot of other nice features. (it can reject messages from
senders with strange patterns or with inexistent domain names)
It's website is:
http://www.interazioni.it/opensource/chkuser/
A (hopefully) nice installation guide is:
http://www.qmailwiki.org/Simscan/Related_Docs/Simscan_ClamAV_Chkuser_Installation_Guide
regards,
bnegrao
What causes bounce messages to be sent to forged addresses?
server1# qmail-qread | grep remote | wc -l
0
server2# qmail-qread | grep remote | wc -l
754
h
# find /var/qmail/queue/mess/ -type f -exec grep '^[EMAIL PROTECTED]:$' {} \;
| grep -v Binary | cut -d '@' -f 2 | cut -d '' -f 1 | sort | uniq
| wc -l
19
Only 19 domains out of:
# cat /var/qmail/users/assign | wc -l
147
Of these,
# find /var/vpopmail/domains/ -type d -maxdepth 1 -mindepth 1 | wc
-l
97
are real domains, the rest are alias domains. Guessing by the
numbers, this doesn't matter. As a matter of coincidence, none of
the 19 domains trying to send bounces are aliases.
Every single one of these 19 domains was migrated from an *old*
crusty Redhat 7.3 server with whatever version of vpopmail had been
new at the time.
# for i in `find /var/qmail/queue/mess/ -type f -exec grep
'^[EMAIL PROTECTED]:$' {} \; | grep -v Binary | cut -d '@' -f 2 | cut -d ''
-f 1 | sort | uniq`; do grep $i /var/qmail/users/assign | sed -e
s/$i/DOMAIN_NAME/g; done
+DOMAIN_NAME-:DOMAIN_NAME:89:89:/var/vpopmail/domains/DOMAIN_NAME:-::
+DOMAIN_NAME-:DOMAIN_NAME:89:89:/var/vpopmail/domains/DOMAIN_NAME:-::
+DOMAIN_NAME-:DOMAIN_NAME:89:89:/var/vpopmail/domains/DOMAIN_NAME:-::
+REAL_DOMAIN-:DOMAIN_NAME:89:89:/var/vpopmail/domains/DOMAIN_NAME:-::
+DOMAIN_NAME-:DOMAIN_NAME:89:89:/var/vpopmail/domains/DOMAIN_NAME:-::
+DOMAIN_NAME-:DOMAIN_NAME:89:89:/var/vpopmail/domains/DOMAIN_NAME:-::
+DOMAIN_NAME-:DOMAIN_NAME:89:89:/var/vpopmail/domains/DOMAIN_NAME:-::
+DOMAIN_NAME-:DOMAIN_NAME:89:89:/var/vpopmail/domains/DOMAIN_NAME:-::
+DOMAIN_NAME-:DOMAIN_NAME:89:89:/var/vpopmail/domains/DOMAIN_NAME:-::
+DOMAIN_NAME-:DOMAIN_NAME:89:89:/var/vpopmail/domains/DOMAIN_NAME:-::
+DOMAIN_NAME-:DOMAIN_NAME:89:89:/var/vpopmail/domains/DOMAIN_NAME:-::
+DOMAIN_NAME-:DOMAIN_NAME:89:89:/var/vpopmail/domains/DOMAIN_NAME:-::
+DOMAIN_NAME-:DOMAIN_NAME:89:89:/var/vpopmail/domains/DOMAIN_NAME:-::
+REAL_DOMAIN-:DOMAIN_NAME:89:89:/var/vpopmail/domains/DOMAIN_NAME:-::
+DOMAIN_NAME-:DOMAIN_NAME:89:89:/var/vpopmail/domains/DOMAIN_NAME:-::
+DOMAIN_NAME-:DOMAIN_NAME:89:89:/var/vpopmail/domains/DOMAIN_NAME:-::
+DOMAIN_NAME-:DOMAIN_NAME:89:89:/var/vpopmail/domains/DOMAIN_NAME:-::
+DOMAIN_NAME-:DOMAIN_NAME:89:89:/var/vpopmail/domains/DOMAIN_NAME:-::
17 of the 19 are real domains, and the 2 which are aliases both
point to real domains which are in the list of 17.
All accounts look the same as far as I can tell:
# cat /var/vpopmail/domains/*/.qmail-default | sort | uniq
| /var/vpopmail/bin/vdelivermail '' bounce-no-mailbox
No unusual .qmail files:
# for i in `find /var/vpopmail/domains/*/.qmail-* -not -name
'.qmail*owner'`; do cat $i | grep -v '^[EMAIL PROTECTED]' | grep -v
'bounce-no-mailbox' | grep -v ezmlm; done | wc -l
0
# for i in `find /var/vpopmail/domains/*/*/.qmail`; do cat $i |
grep -v '^| /usr/bin/maildrop'; done | wc -l
0
...and nothing unusual that I can spot, no obvious differences
between contents of the different domain directories, or files
contained within.
Every message in the queue looks like this one:
Received: (qmail 17683 invoked for bounce); 17 Jun 2005 09:48:53
+
Date: 17 Jun 2005 09:48:53 +
From: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: failure notice
Hi. This is the qmail-send program at stuart.seattleserver.com.
I'm afraid I wasn't able to deliver your message to the following
addresses.
This is a permanent error; I've given up. Sorry it didn't work out.
[EMAIL PROTECTED]:
Sorry, no mailbox here by that name. (#5.1.1)
Any advice, please?
Cheers,
--
Casey Allen Shobe | http://casey.shobe.info
[EMAIL PROTECTED] | cell 425-443-4653
AIM Yahoo: SomeLinuxGuy | ICQ: 1494523
SeattleServer.com, Inc. | http://www.seattleserver.com
Re: [vchkpw] Help with my Chkuser Installation Guide
Hi Tonino, thanks for answering. Documentation says it works with ezmlm and mailman. Please, read the documentation! Tonino Dude, let me tell you: I ran a 'find ezmlm' in your whole website and the only matches I found were these statements (shown bellow) explaining about settings inside chkuser_settings.h file: CHKUSER_ENABLE_EZMLM_LISTS 2.0.7defined Enables checking of EZMLM mailing lists. In versions 2.0.5 and 2.0.6 it was named CHKUSER_ENABLE_LISTS. CHKUSER_EZMLM_DASH 2.0.5 defined'-' Defines the character used to start the extensions of mailing lists. [must always be defined if CHKUSER_ENABLE_LISTS is defined] Are you saying that one that never heard about chkuser before would read all that documentation and then find these statements in the middle of 50 settings he never had seen so far and then conclude logically: [start logic] Oh! (exclamation of a logical insight); IF I read 30 lines above that chkuser has a CHKUSER_RCPT_FORMAT feature to block strange patterns in the mail addresses; AND now I read that it contains a CHKUSER_ENABLE_EZMLM_LISTS feature to enable ezmlm lists; THEN chkuser's CHKUSER_RCPT_FORMAT won't mess with CHKUSER_ENABLE_EZMLM_LISTS; It's logical!!; [end logic] (are you sure?) I don't think so. I would never grasp this without asking on the mailing list. I think you could and a note on this somewhere close to the CHKUSER_RCPT_FORMAT and CHKUSER_SENDER_FORMAT documentation. Well, it's just my opinion. Also, I'm not asking about just ezmlm and mailman lists. Maybe there are other mailing lists or mail mechanisms that require not common characters on the RCPT and/or SENDER addresses. Do you already know about an issue on this? Best regards, bruno
Re: [vchkpw] Help with my Chkuser Installation Guide
Thanks Matt,
I removed that part from the document. I let this for the experienced
administrators to try by themselves.
Bruno
- Original Message -
From: Matt Brookings [EMAIL PROTECTED]
To: vchkpw@inter7.com
Sent: Friday, June 17, 2005 3:52 PM
Subject: Re: [vchkpw] Help with my Chkuser Installation Guide
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
|
| Also, I'm not asking about just ezmlm and mailman lists. Maybe there are
| other mailing lists or mail mechanisms that require not common
| characters on the RCPT and/or SENDER addresses.
If I remember correctly, the RFCs state that any alphanumeric,
non-control character, and any characters not used in message
structure may be used inside the local portion of an address.
This includes characters such as '*', '', '{', and so on.
While these are not 'common' characters, they certianly should
not be rejected.
- --
/*
~Matt Brookings [EMAIL PROTECTED] GnuPG Key 7D7E5F37
~Software developer Systems technician
~Inter7 Internet Technologies, Inc. (815)776-9465
*/
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.6 (GNU/Linux)
iD8DBQFCsxwD/pZz8n1+XzcRAjHWAJ4yUU5qScnfWDgqFOu1iTWJnBEdAQCdH6Vf
b3mxgZykox8W/PlcG8Gt/MA=
=A4po
-END PGP SIGNATURE-
Re: [vchkpw] Help with my Chkuser Installation Guide
No .??? We have many users who opt for addresses like [EMAIL PROTECTED] Tonino (chkuser developer) said that . and = are being allowed and the documentation is outdated. But, despite of this, the main function of chkuser, that is, checking user existence before accepting any e-mail is perfect and everybody would like to use it. bnegrao
[vchkpw] Re: REQUEST FOR NEW FEATURE: INTERNAL-ONLY ACCOUNTS
Guys, I'd like to know where the vmoduser command stores its information about which user can relay or cannot. To proceed with my idea of internal-only accounts, I'm thinking about using this database as my internal-only users list for the program I'll run using the QMAILQUEUE patch. bnegrao. 'vmoduser -rs' will disable relay *AND* disable SMTP-AUTH ability for given e-mail-address, so even if they set up their MUA to do SMTP-AUTH they'll not be allowed and therefore not gain RELAYCLIENT-privileges.
Re: [vchkpw] how to enable CHKUSER_SENDER_MX check
The one on Source Forge is for Developers (or concerned users and testers, like myself) hence the name vpopmail-devel. Unless you see another sf list that I don't. vpopmail-devel?? Is this list a best place to request for new features? rgds, bnegrao
Re: [vchkpw] how to enable CHKUSER_SENDER_MX check
I discovered I have to uncomment the /* #define CHKUSER_SENDER_MX */ line in chkuser_settings.h file. Should I edit it before applying the chkuser patch of after? Or doesn't matter? I found in chkuser documentation they recommend to edit it after the patch was applied. Sorry guys by not reading chkuser's documentation prior to post these questions. bnegrao
Re: [vchkpw] Re: REQUEST FOR NEW FEATURE: INTERNAL-ONLY ACCOUNTS
Hi Peter, Let me see if I understood your plan. You say that, in order to disable the RELAYCLIENT to just some accounts, and this way, setting them as partially** internal-only, I should: ** remember that just by disabling the RELAYCLIENT variable the account could still receive external e-mail. They just can't send e-mail to external accounts. If so, this configuration still doesn't fully implement the internal-only accounts feature I'm looking for 1 - Disable the pop-before-smtp scheme by recompiling vpopmail. ( OR disable it just to a specific domain by running vmoduser -r domainname. ), AND Remove the RELAYCLIENT variable for the whole network, AND Enable the SMTP-AUTH scheme on the qmail server, AND configure full accounts (not internal-only) to authenticate via SMTP-AUTH. OR 2 - Enable the pop-before-smtp scheme for everybody in the domain, AND Remove the RELAYCLIENT variable for the whole network, AND selectively disable the pop-before-smtp capability of the internal-only accounts by running a vmoduser -r [EMAIL PROTECTED] for each internal-only account. Is this what you planned? I agree that both strategies are much better than putting a lot of IP addresses in the beginning of tcp.smtp file, and I also agree that just by disabling a user from sending e-mail to external accounts will force him to not use his work e-mail to contact his external friends, once he'll never be able the answer their messages. But there's a possibility for him to receive external e-mail, and I don't want this leak opened. So this is not what I'm looking for yet. More ideas? regards, - Bruno Negrao - Network Manager Engepel Teleinformática. 55-31-34812311 Belo Horizonte, MG, Brazil
Re: [vchkpw] REQUEST FOR NEW FEATURE: INTERNAL-ONLY ACCOUNTS
Guys, With the QMAILQUEUE patch it's possible to add a program that scans the passing messages(local and remote) and block some of them, based on certain criteria. Correct? (that's how inter7's simscan software works) With this, I could add a program to filter the passing messages to block the internal-to-external messages only for the internal-only accounts. The program would get the internal-only accounts list from a text file with the list of internal-only accounts. What do you think of this idea? Going on with this idea I see a possibility for vpopmail. If vpopmail start supporting a new user property, INTERNAL, inside vpasswd file, like the prototype bellow: patrick:$1$oza9XaY.qO8uXhlaR701:1:0:patrick is internal only:/var/vpopmail/domains/exampledom.com.br/patrick:60MB:textpasswd:INTERNAL And added a tool like 'vsetinternaluser' to set this parameter inside vpasswd file, And provided this program to be added by QMAILQUEUE variable, which would look for the INTERNAL property inside each vpasswd file, Then we would have this feature fully implemented. Someone agree? Regards, - Bruno Negrao - Network Manager Engepel Teleinformática. 55-31-34812311 Belo Horizonte, MG, Brazil
Re: [vchkpw] REQUEST FOR NEW FEATURE: INTERNAL-ONLY ACCOUNTS
This could also be done with a flag in the vadduser/vmoduser programs? Yes, perfect! KBO (or some vpopmail developer), are you reading this thread? Regards, bnegrao
Re: [vchkpw] Request for new feature: Internal-only accounts
Hi Casey, patrick:$1$oza9XaY.qO8uXhlaR701:1:0:patrick is internal only:/var/vpopmail/domains/exampledom.com.br/patrick:60MB:textpasswd:INTERN AL You'd at least need an extra colon before INTERNAL, because there's already the optional NOQUOTA property. Wouldn't the string NOQUOTA be exactly in the place where there is a 60MB in my example above? I don't work for a large corporation anymore (thank the gods) and I know their opinions on things differ greatly from mine and often what is logical in anyone's mind, but my gut feeling on this is that if you can't trust an employee enough to allow them to send email out, then you shouldn't give that employee a half-arsed E-mail account at all. I understand your point. Makes sense. But this feature is still useful, and there are commercial mail servers providing it, so I want to be able to do this with qmail and vpopmail (or other add-on software that can do this in place of vpopmail) I will try with vpopmail more. The vpopmail developers didn't show up until now to give their opinion, maybe they're too busy. Let's wait. regards, - Bruno Negrao - Network Manager Engepel Teleinformática. 55-31-34812311 Belo Horizonte, MG, Brazil
Re: [vchkpw] Re: REQUEST FOR NEW FEATURE: INTERNAL-ONLY ACCOUNTS
Hi Peter,
'vmoduser -rs' will disable relay *AND* disable SMTP-AUTH ability for
given e-mail-address, so even if they set up their MUA to do SMTP-AUTH
they'll not be allowed and therefore not gain RELAYCLIENT-privileges.
when we use vmoduser command, where does it store the information of which user
can do what?
This can for sure be made dynamic and used by creating a template
.qmail and (sym)linking the other .qmail files against it, so a
change affects all at the same time.
The script checking for external incoming can e.g. inspect
$ENV{SENDER} for internal domain and if not 'exit(100)' to bounce
the message. If the mail is internal simply 'exit(0)' and have
|vdelivermail '' bounce-no-mailbox in .qmail file.
Did you read my idea(posted some messages ago) about making a script to be run
with QMAILQUEUE patch to filter all the passing messages?
With this idea we wouldn't even have that problem of the possibility of sending
e-mails from one local domain to other local domain - the program could block if
From: and To: are not on the same domain.
Can you comment about this idea?
-
Bruno Negrao - Network Manager
Engepel Teleinformática. 55-31-34812311
Belo Horizonte, MG, Brazil
Re: [vchkpw] REQUEST FOR NEW FEATURE: INTERNAL-ONLY ACCOUNTS
Hi Nick, Sounds not terribly difficult, and does actually sound pretty useful. Similar functionality exists in commercial servers like Exchange and Domino, so obviously other folks find it useful. Good to know that other mailservers already implement this feature. Maybe this helps to motivate the developers to run for a solution. Also, now I know what servers I can install if that director crazily wants this feature NOW!! Regards, - Bruno Negrao - Network Manager Engepel Teleinformática. 55-31-34812311 Belo Horizonte, MG, Brazil
Re: [vchkpw] Best way to inject qmail+vpopmail with pop3 domain mailbox
I perform this using a DJB's small software called serialmail. It is designed to do exactly this. bruno. - Original Message - From: Michiels Tom [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Friday, August 27, 2004 8:15 AM Subject: [vchkpw] Best way to inject qmail+vpopmail with pop3 domain mailbox Hi, All of my domain mail is delivered to a pop3 mailbox on the internet, what is the best way to empty this mailbox and inject this in my qmail+vpopmail system ? Is there some sort of howto or other doc ? Thx Tom
Re: [vchkpw] How to Split a domain into 2 machines?
I can't see how you could actually want this. Are you planning on then putting some sort of imap proxy in front of the box to direct logins to the correct place? What does this do for you that a cluster with shared storage doesn't? Hi Nick, What a "cluster with shared storage" means? Where can i learn moreabout this topic? bruno
Re: [vchkpw] How to Split a domain into 2 machines?
Nick, The qmail-ldap patch appears to offer a clean solution for this problem since it creates an ldap for the email accounts that can be share amongst the corporate email servers. When qmail-ldap wants to deliver a message to a local user, it checks in the ldap database for the properti "mailhost" of that user. The mailhost property sets the host where the maildir of that account is physically configured. Then, the e-mail is forwarded to that host. There is a document called "Life with Qmail-Ldap", in http://www.lifewithqmail.org/ldap/, that makes an introduction about the new capabilities gained when integrating qmail + an ldap database. Bellow, i cut and pasted this introduction: "Lightweight Directory Access Protocol, or LDAP, is a very useful tool in administration of large networks and organizations. It is a database that is highly optimized for read operations, up to ten times faster than SQL database systems. One of the best features of LDAP is the ability to store user accounts. A single account entry can be used for logging in to unix workstations, imap servers, access controlled web pages, and email account storage. With the qmailUser schema and user accounts loaded into an LDAP server, Qmail-LDAP can be configured so that all mail servers in an organization can share this same account data. Qmail-LDAP supports message routing to the mailhost specified in each users account entry, even when all internal email accounts use business card style addresses such as [EMAIL PROTECTED] There is no need to use internal addresses like [EMAIL PROTECTED] and convert them to [EMAIL PROTECTED] when mail leaves the intranet. Using LDAP to store Qmail-LDAP email accounts requires either building an LDAP directory, or modifying your existing directory. Since Qmail-LDAP requires the administrator to have a prior understanding of LDAP, this section of the HOWTO does not deal with basic LDAP or unix topics. For those who are completely unfamiliar with LDAP directory construction and administration, there are excellent books available and there are searchable mailing list archives at http://www.openldap.org. 1. The first part of setting up the directory server to work with Qmail-LDAP is to add the schema. This is not required if you have disabled schema checking, however running an LDAP server with schema checking disabled is highly discouraged. How the schema is loaded depends on the server you are using." Regards, bruno
Re: [vchkpw] How to Split a domain into 2 machines?
Hi Itamar, Pra que voce quer fazer isto Bruno ? (he is asking me why would I want to do this) To answer it i'll have to explain a little about my network. Here where i'm working is the central node of a big network. We are the mailserver for some companys that are connected to us through leased lines. Some of these links are slow 64K links. There is a company connected to us using a 64K link that wants the mailserver for their domain installed directly in their LAN, to speed up the mail transition and to avoid the internal mail traffic passing through this link every time a local employee send a message to other local employee. The problem about moving their mailserver from here (the central node) to their local network is that they have a big filial in another state that is also connected to us. When we move their MX box to their LAN, everybody in the filial will have to pass throught their 64KB link to send and receive e-mail, thus, consuming their bandwidth again. So, to avoid this, i want the filial maildirs to stay configured here in the central node of the network. And the maildirs of the biggest office will be configured in their own local mailserver. Could you understand me? Regards, bruno.
Re: [vchkpw] How to Split a domain into 2 machines?
How about 2 qmail installs? After you install qmail once, change conf-qmail to have a qmail2. make setup check again, and you have a 2nd qmail install. In there, change smtproutes to point your domain to your 2nd server. Then for each user that exists on the 2nd server, make a .qmail-default with: |/var/qmail2/bin/forward [EMAIL PROTECTED] (remember to run your qmail-send process from the 2nd install, or nothing will go out - Yes yes.. It got me :) Rick, are you currently using this? It seems you omitted that I would have to make the same thing in the second server, creating .qmail files forwarding messages to the users configured in the 1st server. I think this configuration isn't scalable. What would happen if I'd like to split the domain through 3 or more machines? Or if I'd like to split other domains through other servers? It would became an administration nightmare... don't you think? The qmail-ldap still appears to be the best solution. The only disadvantage is, besides I'll be obligated to understand all about LDAP concepts, qmail-ldap seems to be difficult to install and configure at a first look. This gonna be a lot of work... Regards, bruno.
Re: [vchkpw] How to Split a domain into 2 machines?
Hi Rick, Rick, are you currently using this? For a whole domain. Not per user. I can't get you, what you mean for a whole domain, not per user? I want to split a whole domain... (??) You told you have to create a .qmail file on the 1st server for every account that is configured on the 2nd server. Isn't it per user configuration too? It seems you omitted that I would have to make the same thing in the second server, creating .qmail files forwarding messages to the users configured in the 1st server. No, if you create a .qmail-default for each user that needs to be forwarded, you only need to create THOSE users on the 2nd server. But what happens when a user of the second server send an email to a user of the first server? the seconds server would bounce an error message this account doesn't exist if it is not configured to forward the e-mails for unexistent accounts for the fisrt server. I think this configuration isn't scalable. What would happen if I'd like to split the domain through 3 or more machines? Or if I'd like to split other domains through other servers? It would became an administration nightmare... don't you think? Then I'd set a flag, or create a field in MySQL - and look at using maildrop for the redirection, after a perl script checks for the routing information. This was too interesting. Can you write this with more detail? I never used vpopmail integrated with MySQL, and I don't master databases or SQL. What program would check the mysql database to discover where the maildir is installed? If qmail-ldap already addresses this problem, do you believe it is worth to reimplement this using an mysql database? Wouldn't it be reinventing the wheel? Regards, bruno.
Re: [vchkpw] RedHatLinux 9 compatibility
Hi dude, We were just talking about it on this list few days ago. search for "good howto" an you gonna find a lot of information. Anyway, www.qmairocks.org is perfect. bruno - Original Message - From: [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Thursday, July 22, 2004 4:40 AM Subject: [vchkpw] RedHatLinux 9 compatibility Hi,I want to install QMAIL + Vpopmail + courier-imap + Qmailadmin + LDAP + MySql + Spamassassin + clamav + Squirrelmail + stats (Isoqlog qmail MRTG) under Linux 9. Is every thing compatable with linux 9 where can i get good howto. I need step by step installation. also i want to host multiple mail sites on a single server. please help me in this regardRegards,Venu--This Message and any attachments is intended solely for the addresses and is confidential.If you receive this message in error or if you are not the intended recipient, please delete the mail.Any use not in accord with its purpose, any dissemination or disclosure, either whole or partial, is prohibited.Please inform us in case of erroneous delivery, thanks for your cooperation.
Re: [vchkpw] www.qmailrocks.org - was: Re: [vchkpw] RE: good howto
I like http://sylvestre.ledru.info/howto/howto_qmail_vpopmail.php; how to also. It has some utils qMail Rocks lacks. I recently combined it with qMailRock's how to and now my server really ROCKS! Which utilities you're saying qmailrocks site is missing? Why they are so good? bruno.
[vchkpw] www.qmailrocks.org - was: Re: [vchkpw] RE: good howto
www.qmailrocks.org Hey, this website is incredible useful! Awesome!!! How isn't it mentioned on www.qmail.org website?! bruno That's all you need. -Original Message- From: Michiels Tom (Uptime) [mailto:[EMAIL PROTECTED] Sent: 15 July 2004 10:38 To: [EMAIL PROTECTED] Subject: good howto Can somebody point me to a good howto for installing and configuring vpopmail together with squirrelmail/qmail/antispam/antivirus on a Debian machine ? thx in advance! regards Tom Michiels
Which were my configure options?
Hy all, Iinstalled a vpopmail 4.8.9in my system last year. I'd like to know what ./configure options is my vpopmail running now. Is there some way to do this? (I still have the installation directory here) Specifically I want to know if I enabled the --enable-roaming-users=y option. (i'm having a problem in relaying e-mailsfor a person using sqwebmail from out of our network). thanks. --- Bruno Negrão -- Suporte-- Plugway Acesso Internet Ltda.-- (31)34812311-- [EMAIL PROTECTED]
Sqwebmail: passwd accounts
Hi all, Does sqwebmail deal with /etc/passwd accounts? Could it change these passwords? DoMaildirs stay in the unix user's home directory? thanks, |---|--Bruno Negrão |--Engepel Teleinformática -|---
