Re: [vchkpw] chkuser on relay server , part II
On Mon, 15 Jan 2007, David Chaplin-Loebell wrote: Miki wrote: - so after spending weekend over google ;) I want kindly ask TONIX if he is willing to add smal feature into chkuser 2.0.8, I have idea something like CHECK_EXTERNAL_FILE = 0/1 EXTERNAL_FILE = /bla/bla/list.txt (or even cdb) I second this request-- having this functionality in chkuser would save me a world of trouble. David I have been off the list for a few days and missed this discussion. We have 3 E-Mail servers, 2 of which are backup MX's and 1 master, I wrote a small chkuser-style-server on the master server and a chkuser-style-client for both the MX's. This for us works perfectly and no files have to be migrated from the master to the backup's. The server is very simple (it does not actually use chkuser, but just chkuser style functionality), and the client communicates with this server to validate destination addresses. The client is called using a qmail-check-recipient patch (not sure where it came from, I might have even written it). It may be possible to write the server to use chkuser and have clients on the relay machines.
Re: [vchkpw] chkuser on relay server , part II
At 15.52 15/01/2007, you wrote: Hello All especially tonix ;) , well, I see discussion running here ;) but I want move little forward. just my2 cent: qmail is good example of proof of concept which make its own way. Bad luck is that DJB is not working on it, so this nifty features will be slowly lost as more and more patches will come, which is main point of all complaints. Its is nice that we have all the patches, but most of them are incompatible or hard to implement into others so until someone really Im mean really need them (so spending days on them), it will switch to something else, which is not good as qmail, but these days is almost everything good as qmail. If there is no progress,blind by own feeling how it is perfect , no matter that it is best of the best it will become soon or later overcome by others. Remember OS/2 or BeOS ? ;) As qmail server is used as front-relay , there is problem with chkuser to check real rcpt. from discussion I see few aproaches how it can be done: - copy/mount vpopmail (not all files, just needed) to relay server and delete from virtualdomains - well, kinda ugly but working ;) problem is that If I have some offices behind firewall and even on exchange, I cant go this way - using of validrcptto patch - nice, but problem implement into rest of patches (bill shupp/big ISP...), when I use it, im loosing chkuser features ;) and others - so after spending weekend over google ;) I want kindly ask TONIX if he is willing to add smal feature into chkuser 2.0.8, I have idea something like CHECK_EXTERNAL_FILE = 0/1 EXTERNAL_FILE = /bla/bla/list.txt (or even cdb) Let me publish 2.0.9, then I will make you a surprise with 2.0.10! ;) Ciao, Tonino in this case is much easier make list of mailboxes , for example script from David Duserre from fehcom.de can make list of all even aliases and ezmlm lists it will be really helpfull to have something like this, and as I saw code for validrcptto it should be not so much coding ;) thank you very much even if you will not do it ;) Miki (Peter Mikeska)
[vchkpw] which files truly determine relay into a qmail server
I've been asked to admin an old, jumbled install of qmail/vpopmail (many are local users, many are vpopmail users with .cdb). I'm having a brain cramp because the install has domains splattered all over the following files: /var/qmail/control: locals rctphosts morercpthosts virtualdomains My exercise is to identify ONLY those domains that the server will actually accept delivery for from the Internet so that we can start pruning away the domains that seems to be lingering with no customers/accounts/purpose/etc. My intention/belief was that ONLY 'rcpthosts' and 'morerctphosts' govern which domains the server will accept delivery/relay for from the outside. Thus, I felt that if I built a master list from these two files, any other domains I might find are automatically unused. However this install has a number of domains that are aliases in the 'locals' file to a single local account and the domains only seem to appear in 'locals'. Does 'locals' (or 'virtualdomains') in any way influence the relay decision to accept incoming mail? Or am I right that ONLY 'rcpthosts' and 'morercpthosts' define the permitted domains. Sorry for the long explanation, validation/help is much appreciated! Dave.
[vchkpw] everyone seen this?
http://wiki.ctyme.com/index.php/Qmail_Sucks -- Cheers, Steve -- -- Cheers, Steve
Re: [vchkpw] everyone seen this?
Steve Cole wrote: http://wiki.ctyme.com/index.php/Qmail_Sucks Perkel, he announced his intentions awhile back. -- Three years now I've asked Google why they don't have a logo change for Memorial Day. Why do they choose to do logos for other non-international holidays, but nothing for Veterans? Maybe they forgot who made that choice possible.
Re: [vchkpw] which files truly determine relay into a qmail server
locals: Domains that the server should deliver as local rather than sending off to other people. When you send mail to your own domain, it knows to not deliver it to the MX of that domain by its presence in the locals file rcpthosts / morercpthosts: Domains that the SMTP daemon should receive mail for (allow) without the presence of RELAYCLIENT as set in tcp.smtp or by SMTP authentication. Domains in here will always be accepted, and domains not in here will be rejected unless relaying is allowed. morercpthosts is just a continuation, with your most popular domains to be in rcpthosts, just for speed of lookup. In modern fast systems, it doesn't matter. virtualdomains: A list of the prepended strings by domains, allowing the system to prepend an identifier based on the domain in question. This converts [EMAIL PROTECTED] to [EMAIL PROTECTED] for later processing. smtproutes: A list of domains and their artificial MX server to send mail to. Domains in here should also be in rcpthosts, but not treated as local. Use this if you are delivering mail to another MX for select domains, or if you have a smarthost. For domains that your mail server will accept mail from the Internet, see `cat rcpthosts morercpthosts`. -M - Original Message From: Dave Richardson [EMAIL PROTECTED] To: vchkpw@inter7.com Sent: Thursday, January 18, 2007 10:39:27 AM Subject: [vchkpw] which files truly determine relay into a qmail server I've been asked to admin an old, jumbled install of qmail/vpopmail (many are local users, many are vpopmail users with .cdb). I'm having a brain cramp because the install has domains splattered all over the following files: /var/qmail/control: locals rctphosts morercpthosts virtualdomains My exercise is to identify ONLY those domains that the server will actually accept delivery for from the Internet so that we can start pruning away the domains that seems to be lingering with no customers/accounts/purpose/etc. My intention/belief was that ONLY 'rcpthosts' and 'morerctphosts' govern which domains the server will accept delivery/relay for from the outside. Thus, I felt that if I built a master list from these two files, any other domains I might find are automatically unused. However this install has a number of domains that are aliases in the 'locals' file to a single local account and the domains only seem to appear in 'locals'. Does 'locals' (or 'virtualdomains') in any way influence the relay decision to accept incoming mail? Or am I right that ONLY 'rcpthosts' and 'morercpthosts' define the permitted domains. Sorry for the long explanation, validation/help is much appreciated! Dave.
Re: [vchkpw] which files truly determine relay into a qmail server
Michael, let me ask a true/false question or two of you/the list based upon your response (which I REALLY appreciate!): Q: ONLY the content of the 'rcpthosts' and 'morercpthosts' (and any special cases in tcp.smtp) defines which domains' incoming mail will be accepted by SMTPd. True or False? Q: Domains that appear in 'locals' or 'virtualdomains' (for presumed delivery on the local box) but DO NOT appear in rcpthosts/morercpthosts/tcp.smtp (and have no smtphosts controls) CANNOT receive mail directly under normal circumstances. True or False? In summary, domains that appear in local/virtualdomains but do not appear in rcpthosts/etc have a VERY high probability of being misconfigured - with a likely root cause of improper/incomplete deletion of a domain from the system. True or False? (speculative answer, I understand) THANKS A TON! Dave. Michael Krieger wrote: locals: Domains that the server should deliver as local rather than sending off to other people. When you send mail to your own domain, it knows to not deliver it to the MX of that domain by its presence in the locals file rcpthosts / morercpthosts: Domains that the SMTP daemon should receive mail for (allow) without the presence of RELAYCLIENT as set in tcp.smtp or by SMTP authentication. Domains in here will always be accepted, and domains not in here will be rejected unless relaying is allowed. morercpthosts is just a continuation, with your most popular domains to be in rcpthosts, just for speed of lookup. In modern fast systems, it doesn't matter. virtualdomains: A list of the prepended strings by domains, allowing the system to prepend an identifier based on the domain in question. This converts [EMAIL PROTECTED] to [EMAIL PROTECTED] for later processing. smtproutes: A list of domains and their artificial MX server to send mail to. Domains in here should also be in rcpthosts, but not treated as local. Use this if you are delivering mail to another MX for select domains, or if you have a smarthost. For domains that your mail server will accept mail from the Internet, see `cat rcpthosts morercpthosts`. -M - Original Message From: Dave Richardson [EMAIL PROTECTED] To: vchkpw@inter7.com Sent: Thursday, January 18, 2007 10:39:27 AM Subject: [vchkpw] which files truly determine relay into a qmail server I've been asked to admin an old, jumbled install of qmail/vpopmail (many are local users, many are vpopmail users with .cdb). I'm having a brain cramp because the install has domains splattered all over the following files: /var/qmail/control: locals rctphosts morercpthosts virtualdomains My exercise is to identify ONLY those domains that the server will actually accept delivery for from the Internet so that we can start pruning away the domains that seems to be lingering with no customers/accounts/purpose/etc. My intention/belief was that ONLY 'rcpthosts' and 'morerctphosts' govern which domains the server will accept delivery/relay for from the outside. Thus, I felt that if I built a master list from these two files, any other domains I might find are automatically unused. However this install has a number of domains that are aliases in the 'locals' file to a single local account and the domains only seem to appear in 'locals'. Does 'locals' (or 'virtualdomains') in any way influence the relay decision to accept incoming mail? Or am I right that ONLY 'rcpthosts' and 'morercpthosts' define the permitted domains. Sorry for the long explanation, validation/help is much appreciated! Dave.
