[vchkpw] [semi-OT] Problem with qconfirm
Hi folks, I post my problem here, because probably it's a wrong delivery. I've configured qconfirm for [EMAIL PROTECTED], where domain1.dom is a domain in my vpopmail system (exactly the main domain). In .qconfirm/conf there's the QCONFIRM_PREPEND configured for 'domain1.dom-' When I send a message to [EMAIL PROTECTED], receive a response from qconfirm (request confirm). Example: From qconfirm ([EMAIL PROTECTED]) To Me ([EMAIL PROTECTED]) That's ok, but ... When I respond, the message with sender Me from qconfirm ([EMAIL PROTECTED]) arrives in my qmail-vpopmail system. In /home/vpopmail/domains/domain1.dom/user1 there's a special .qmail file created by qconfirm: .qmail-user1-qconfirm-5e9ba6a4fd25f57f97d2d6c0f74b43f4 that obviously may check the message and accept that (|qconfirm-accept 'domain2:dom=-user2' '/home/vpopmail/domains/domain1.dom/user1/.qconfirm'). The problem is that user1-qconfirm-5e9ba6a4fd25f57f97d2d6c0f74b43f4 isn't a domain1.dom account, then the message is forwarded to [EMAIL PROTECTED] Where is my mistake? Could you help me? Have you ever been using qconfirm with vpopmail? Thanks for your patience and support Regards Andrea
[vchkpw] Maintaining vlog in mysql
I noticed that my vlog table+index in vpopmail with MySQL enabled is up to around 30MB. Is there a maintenance procedure to cull records from this table? I can just start deleting oldest records, BUT.. D.
[vchkpw] Enable-roaming-users tests
Hi folks, Probably there's a mistake. SITUATION - Domain1.dom is an internal domain, IP: no server LAN Domain2.dom is an internal domain, IP: same LAN as server Domain3.dom is an external domain Domain4.dom is another external domain My tcp.smtp: # No Qmail-Scanner at all for mail from 127.0.0.1 127.:allow,RELAYCLIENT=,RBLSMTPD=,QMAILQUEUE=/var/qmail/bin/qmail-queue # Use Qmail-Scanner without SpamAssassin on any mail from the LAN 192.168.:allow,RELAYCLIENT=,RBLSMTPD=,TCPREMOTEIP=Protected,QMAILQUEUE =/var/qmail/bin/qmail-queue # Use Qmail-Scanner with SpamAssassin on any mail from the rest of the world :allow,DENYMAIL=DNSCHECK,QMAILQUEUE=/var/qmail/bin/qmail-scanner-queue.pl TESTS - With --enable-roaming-users=n: Domain1.dom -- domain3.dom NO (right, 553 not allowed rcphost) Domain2.dom -- domain3.dom YES (right, for tcp.smtp) Domain3.dom -- domain4.dom NO (right, isn't an open relay) With --enable-roaming-users=y: Domain2.dom -- domain3.dom YES (right, for tcp.smtp) Domain3.dom -- domain4.dom NO (right, isn't an open relay) The problem is: Domain1.dom -- domain3.dom NO (553 not allowed rcphost) why? In /home/vpopmail/bin I've tcp.smtp, but open-smtp too. In open-smtp I can see one entry: 192.168.10.13:allow,RELAYCLIENT=,RBLSMTPD= 1072273753 (ip from LAN) In open-smtp we have the communications permitted from tcp.smtp? Where's the db that I could clean with the command /home/vpopmail/bin/clearopensmtp? I don't understand exactly the mechanism of --enable-roaming-users, could you figure it out? Where's probably my mistake? Thanks for patience and support Regards Andrea
Re: [vchkpw] Enable-roaming-users tests
On Dec 24, 2003, at 7:08 AM, Andrea Riela wrote: Probably there's a mistake. When you enable-roaming-users, you're enabling a POP before SMTP feature. That means you need to authenticate via POP and pick up email before attempting to send. With a properly configured system, you'll be able to send from your IP address for 30 minutes after you establish a POP connection. Keep in mind that if you're using courier-imap you need to recompile it after building vpopmail with enable-roaming-users since it links directly to libvpopmail instead of calling vchkpw. -- Tom Collins - [EMAIL PROTECTED] QmailAdmin: http://qmailadmin.sf.net/ Vpopmail: http://vpopmail.sf.net/ Info on the Sniffter hand-held Network Tester: http://sniffter.com/
[vchkpw] R: [vchkpw] Enable-roaming-users tests
Thank you very much, Tom When you enable-roaming-users, you're enabling a POP before SMTP feature. That means you need to authenticate via POP and pick up email before attempting to send. With a properly configured system, you'll be able to send from your IP address for 30 minutes after you establish a POP connection. Ya, ok, that's clear. Keep in mind that if you're using courier-imap you need to recompile it after building vpopmail with enable-roaming-users since it links directly to libvpopmail instead of calling vchkpw. That's not clear. I use qmail for pop3, and I will use Courier only for pop3 with ssl. Now I'm testing the enable-roaming-users only with qmail and vpopmail (vchkpw). The problem is: when I use --enable-roaming-users=no, I haven't possibilities to send an email from no-LAN ip to no-LAN ip. And that's right. But when I use --enable-roaming-users=yes, nothing, and I don't undestand why. My steps: 1- ./configure ... --enable-roaming-users=n make make install That works fine 2- qmailctl stop (rm /home/vpopmail/bin/vchkpw) make clean ./configure ... --enable-roaming-users=y make make install qmailctl cdb /home/vpopmail/bin/clearopensmtp qmailctl start Send email from [EMAIL PROTECTED] (internal account) to other external account via different connection (dialup) -- 553, not allowed rcphost I've forgotten something? Thanks Andrea
RE: [vchkpw] R: [vchkpw] Enable-roaming-users tests
This sounds like the domain is trying to be relayed into your lan system, but it doesn't exist in the rcpthost/morercpthosts file. Maybe you should check the mx records? Where is the rcpthost denied message coming from, the server your relaying through or the remote system? If its coming from your own server, then there is your problem. Shane -Original Message- From: Andrea Riela [mailto:[EMAIL PROTECTED] Sent: Thursday, 25 December 2003 1:22 AM To: [EMAIL PROTECTED] Subject: [vchkpw] R: [vchkpw] Enable-roaming-users tests Thank you very much, Tom When you enable-roaming-users, you're enabling a POP before SMTP feature. That means you need to authenticate via POP and pick up email before attempting to send. With a properly configured system, you'll be able to send from your IP address for 30 minutes after you establish a POP connection. Ya, ok, that's clear. Keep in mind that if you're using courier-imap you need to recompile it after building vpopmail with enable-roaming-users since it links directly to libvpopmail instead of calling vchkpw. That's not clear. I use qmail for pop3, and I will use Courier only for pop3 with ssl. Now I'm testing the enable-roaming-users only with qmail and vpopmail (vchkpw). The problem is: when I use --enable-roaming-users=no, I haven't possibilities to send an email from no-LAN ip to no-LAN ip. And that's right. But when I use --enable-roaming-users=yes, nothing, and I don't undestand why. My steps: 1- ./configure ... --enable-roaming-users=n make make install That works fine 2- qmailctl stop (rm /home/vpopmail/bin/vchkpw) make clean ./configure ... --enable-roaming-users=y make make install qmailctl cdb /home/vpopmail/bin/clearopensmtp qmailctl start Send email from [EMAIL PROTECTED] (internal account) to other external account via different connection (dialup) -- 553, not allowed rcphost I've forgotten something? Thanks Andrea
Re: [vchkpw] R: [vchkpw] Enable-roaming-users tests
On Wed, 24 Dec 2003, Andrea Riela wrote: [snip] Keep in mind that if you're using courier-imap you need to recompile it after building vpopmail with enable-roaming-users since it links directly to libvpopmail instead of calling vchkpw. That's not clear. I use qmail for pop3, and I will use Courier only for pop3 with ssl. Now I'm testing the enable-roaming-users only with qmail and vpopmail (vchkpw). I have to ask. Why not use stunnel to create the SSL tunnel and just use the standard qmail POP3 like you're doing for non-SSL? My line to start this is: env - PATH=/var/qmail/bin:/usr/local/bin:/usr/sbin \ tcpserver -H -R -u 89 -g 89 0 pop3s \ stunnel -T pop3s -p /var/qmail/control/servercert.pem \ -l /var/qmail/bin/qmail-popup vengeance.tokimi.net \ /home/vpopmail/bin/vchkpw /var/qmail/bin/qmail-pop3d Maildir This uses a 3.x version of stunnel. A version 4.x stunnel requires something completely different. But, to answer the issue with Courier pop3... The problem is: when I use --enable-roaming-users=no, I haven't possibilities to send an email from no-LAN ip to no-LAN ip. And that's right. But when I use --enable-roaming-users=yes, nothing, and I don't undestand why. My steps: 1- ./configure ... --enable-roaming-users=n make make install That works fine 2- qmailctl stop (rm /home/vpopmail/bin/vchkpw) make clean ./configure ... --enable-roaming-users=y make make install qmailctl cdb /home/vpopmail/bin/clearopensmtp qmailctl start Send email from [EMAIL PROTECTED] (internal account) to other external account via different connection (dialup) -- 553, not allowed rcphost I've forgotten something? If I've followed this conversation correctly... Rather than removing /home/vpopmail/bin/vchkpw at the beginning of step two, shouldn't you be renaming it to a different path so that you can use it for use with plain POP3 (with should not authenticate IPs)? Or am I confused? After rebuilding vpopmail with --enable-roaming-users=y in step 2, you should then recompile Courier to ensure that it is linking against the new (and proper) version of libvpopmail.a Changing the vchkpw binary will not affect Courier since, as Mr. Collins says, Courier links directly against the library and does not ever deal with the vchkpw binary. I hope this helps. Sincerely, Chris Ess System Administrator / CDTT (Certified Duct Tape Technician)
Re: [vchkpw] Enable-roaming-users tests
On Dec 24, 2003, at 10:22 AM, Andrea Riela wrote: 2- qmailctl stop (rm /home/vpopmail/bin/vchkpw) make clean ./configure ... --enable-roaming-users=y make make install qmailctl cdb /home/vpopmail/bin/clearopensmtp qmailctl start Send email from [EMAIL PROTECTED] (internal account) to other external account via different connection (dialup) -- 553, not allowed rcphost I've forgotten something? Yes. After qmailctl start, from the IP you're trying to send mail from, telnet to port 110 on the server and do a POP login (USER [EMAIL PROTECTED], PASS password, LIST). After the POP connection, you should be able to send the email. -- Tom Collins - [EMAIL PROTECTED] QmailAdmin: http://qmailadmin.sf.net/ Vpopmail: http://vpopmail.sf.net/ Info on the Sniffter hand-held Network Tester: http://sniffter.com/
