No bounces, all mail goes to postmaster.
Hi, I'm a qmail + vpopmail beginner. I now using qmail1.03 and vpopmail4.9.10 with mysql.. Examply, # vadddomain test.com test # vadduser [EMAIL PROTECTED] test and I loged in test user and, send mail to [EMAIL PROTECTED] But, bounce message was return to only [EMAIL PROTECTED] How can I get bounce message to virtual user. _ Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com.
how to _delay_ failed authentication
Anybody know how to delay failed authentication attempts to prevent brute force pwd cracking on POP3 server using qmail & vpopmail? Sorry for cross posting. Thanks -kittiwat
RE: Mail Bomb
I don't know why it's being forwarded to itself but it is, somehow. Two things: You don't need to vadduser, you can create .qmail-testgroup in the domain directory. You can also supply the full path to [EMAIL PROTECTED]'s maildir instead of a forwarder, which may prevent any loops from happening. Could you post the headers of one of the later messages? Perhaps the Delivered-To or Received: headers could provide some information. -Original Message- From: Kit Halsted [mailto:[EMAIL PROTECTED]] Sent: Monday, April 23, 2001 12:47 PM To: [EMAIL PROTECTED] Subject: RE: Mail Bomb At 1:04 AM -0600 4/23/01, Chris Bolt wrote: >Logs? And why didn't you just use ezmlm? I don't have ezmlm installed, & I didn't really think it was worthwhile for 6 users or so. Here's a small chunk of logfile from the test message I sent: Apr 22 19:11:28 yabox qmail: 987981088.433470 new msg 889608 Apr 22 19:11:28 yabox qmail: 987981088.434715 info msg 889608: bytes 516 from qp 876 uid 2850 Apr 22 19:11:28 yabox qmail: 987981088.446427 starting delivery 76: msg 889608 t o local [EMAIL PROTECTED] Apr 22 19:11:28 yabox qmail: 987981088.448392 status: local 1/10 remote 0/20 Apr 22 19:11:28 yabox qmail: 987981088.717678 new msg 889609 Apr 22 19:11:28 yabox qmail: 987981088.727411 info msg 889609: bytes 627 from qp 12343 uid 1001 Apr 22 19:11:28 yabox qmail: 987981088.743928 starting delivery 77: msg 889609 t o local [EMAIL PROTECTED] Apr 22 19:11:28 yabox qmail: 987981088.746177 status: local 2/10 remote 0/20 Apr 22 19:11:28 yabox qmail: 987981088.803890 delivery 77: success: did_0+0+1/ Apr 22 19:11:28 yabox qmail: 987981088.819627 status: local 1/10 remote 0/20 Apr 22 19:11:28 yabox qmail: 987981088.821432 end msg 889609 Apr 22 19:11:29 yabox qmail: 987981089.061270 new msg 889610 Apr 22 19:11:29 yabox qmail: 987981089.062297 info msg 889610: bytes 627 from qp 16741 uid 1001 Apr 22 19:11:29 yabox qmail: 987981089.143986 starting delivery 78: msg 889610 t o remote [EMAIL PROTECTED] Apr 22 19:11:29 yabox qmail: 987981089.145720 status: local 1/10 remote 1/20 Apr 22 19:11:29 yabox qmail: 987981089.188166 new msg 889609 Apr 22 19:11:29 yabox qmail: 987981089.189370 info msg 889609: bytes 626 from qp 9295 uid 1001 Apr 22 19:11:29 yabox qmail: 987981089.332014 starting delivery 79: msg 889609 t o remote [EMAIL PROTECTED] Apr 22 19:11:29 yabox qmail: 987981089.333721 status: local 1/10 remote 2/20 Apr 22 19:11:29 yabox qmail: 987981089.783989 new msg 889611 Apr 22 19:11:29 yabox qmail: 987981089.785207 info msg 889611: bytes 627 from qp 15196 uid 1001 Apr 22 19:11:29 yabox qmail: 987981089.904753 starting delivery 80: msg 889611 t o remote [EMAIL PROTECTED] Apr 22 19:11:29 yabox qmail: 987981089.906240 status: local 1/10 remote 3/20 Apr 22 19:11:29 yabox qmail: 987981089.907911 delivery 76: success: did_0+0+1/ Apr 22 19:11:29 yabox qmail: 987981089.910667 status: local 0/10 remote 3/20 Apr 22 19:11:29 yabox qmail: 987981089.913438 end msg 889608 Apr 22 19:11:30 yabox qmail: 987981090.026662 new msg 889612 Apr 22 19:11:30 yabox qmail: 987981090.027701 info msg 889612: bytes 627 from qp 29833 uid 1001 Apr 22 19:11:30 yabox qmail: 987981090.060486 starting delivery 81: msg 889612 t o local [EMAIL PROTECTED] Apr 22 19:11:30 yabox qmail: 987981090.062457 status: local 1/10 remote 3/20 Apr 22 19:11:30 yabox qmail: 987981090.181689 delivery 78: success: 166.84.157.1 31_accepted_message./Remote_host_said:_250_2.6.0_message_received_OK/ Apr 22 19:11:30 yabox qmail: 987981090.185858 status: local 1/10 remote 2/20 Apr 22 19:11:30 yabox qmail: 987981090.187104 end msg 889610 Apr 22 19:11:30 yabox qmail: 987981090.215670 new msg 889608 Apr 22 19:11:30 yabox qmail: 987981090.216718 info msg 889608: bytes 738 from qp 22181 uid 1001 Apr 22 19:11:30 yabox qmail: 987981090.276914 starting delivery 82: msg 889608 t o local [EMAIL PROTECTED] Apr 22 19:11:30 yabox qmail: 987981090.279185 status: local 2/10 remote 2/20 Apr 22 19:11:30 yabox qmail: 987981090.430513 new msg 889610 Apr 22 19:11:30 yabox qmail: 987981090.431762 info msg 889610: bytes 738 from qp 18712 uid 1001 Apr 22 19:11:30 yabox qmail: 987981090.516405 starting delivery 83: msg 889610 t o remote [EMAIL PROTECTED] Apr 22 19:11:30 yabox qmail: 987981090.518114 status: local 2/10 remote 3/20 Apr 22 19:11:30 yabox qmail: 987981090.702296 delivery 82: success: did_0+0+1/ Apr 22 19:11:30 yabox qmail: 987981090.705919 status: local 1/10 remote 3/20 Apr 22 19:11:30 yabox qmail: 987981090.707154 end msg 889608 Apr 22 19:11:31 yabox qmail: 987981091.037664 new msg 889613 Apr 22 19:11:31 yabox qmail: 987981091.039118 info msg 889613: bytes 736 from qp 177 uid 1001 Apr 22 19:11:31 yabox qmail: 987981091.142510 delivery 81: success: did_0+0+1/ Apr 22 19:11:31 yabox qmail: 987981091.145945 status: local 0/10 remote 3/20 Apr 22 19:11:31 yabox qmail: 987981091.147719 starting delivery 84: msg 889613 t o remote [EMAIL PROTECTED] Apr 22 19:11:31 yabox qmail: 987981091.148194 status: local 0/10 re
convert sendmail to qmail
hi I want to convert sendmail to qmail, sendmail is installed on NEC unix with alias, and qmail is installed on Solaris 2.6, Can you tell me how to do it ? thank you ! zhjin
RE: Mail Bomb
At 1:04 AM -0600 4/23/01, Chris Bolt wrote: >Logs? And why didn't you just use ezmlm? I don't have ezmlm installed, & I didn't really think it was worthwhile for 6 users or so. Here's a small chunk of logfile from the test message I sent: Apr 22 19:11:28 yabox qmail: 987981088.433470 new msg 889608 Apr 22 19:11:28 yabox qmail: 987981088.434715 info msg 889608: bytes 516 from qp 876 uid 2850 Apr 22 19:11:28 yabox qmail: 987981088.446427 starting delivery 76: msg 889608 t o local [EMAIL PROTECTED] Apr 22 19:11:28 yabox qmail: 987981088.448392 status: local 1/10 remote 0/20 Apr 22 19:11:28 yabox qmail: 987981088.717678 new msg 889609 Apr 22 19:11:28 yabox qmail: 987981088.727411 info msg 889609: bytes 627 from qp 12343 uid 1001 Apr 22 19:11:28 yabox qmail: 987981088.743928 starting delivery 77: msg 889609 t o local [EMAIL PROTECTED] Apr 22 19:11:28 yabox qmail: 987981088.746177 status: local 2/10 remote 0/20 Apr 22 19:11:28 yabox qmail: 987981088.803890 delivery 77: success: did_0+0+1/ Apr 22 19:11:28 yabox qmail: 987981088.819627 status: local 1/10 remote 0/20 Apr 22 19:11:28 yabox qmail: 987981088.821432 end msg 889609 Apr 22 19:11:29 yabox qmail: 987981089.061270 new msg 889610 Apr 22 19:11:29 yabox qmail: 987981089.062297 info msg 889610: bytes 627 from qp 16741 uid 1001 Apr 22 19:11:29 yabox qmail: 987981089.143986 starting delivery 78: msg 889610 t o remote [EMAIL PROTECTED] Apr 22 19:11:29 yabox qmail: 987981089.145720 status: local 1/10 remote 1/20 Apr 22 19:11:29 yabox qmail: 987981089.188166 new msg 889609 Apr 22 19:11:29 yabox qmail: 987981089.189370 info msg 889609: bytes 626 from qp 9295 uid 1001 Apr 22 19:11:29 yabox qmail: 987981089.332014 starting delivery 79: msg 889609 t o remote [EMAIL PROTECTED] Apr 22 19:11:29 yabox qmail: 987981089.333721 status: local 1/10 remote 2/20 Apr 22 19:11:29 yabox qmail: 987981089.783989 new msg 889611 Apr 22 19:11:29 yabox qmail: 987981089.785207 info msg 889611: bytes 627 from qp 15196 uid 1001 Apr 22 19:11:29 yabox qmail: 987981089.904753 starting delivery 80: msg 889611 t o remote [EMAIL PROTECTED] Apr 22 19:11:29 yabox qmail: 987981089.906240 status: local 1/10 remote 3/20 Apr 22 19:11:29 yabox qmail: 987981089.907911 delivery 76: success: did_0+0+1/ Apr 22 19:11:29 yabox qmail: 987981089.910667 status: local 0/10 remote 3/20 Apr 22 19:11:29 yabox qmail: 987981089.913438 end msg 889608 Apr 22 19:11:30 yabox qmail: 987981090.026662 new msg 889612 Apr 22 19:11:30 yabox qmail: 987981090.027701 info msg 889612: bytes 627 from qp 29833 uid 1001 Apr 22 19:11:30 yabox qmail: 987981090.060486 starting delivery 81: msg 889612 t o local [EMAIL PROTECTED] Apr 22 19:11:30 yabox qmail: 987981090.062457 status: local 1/10 remote 3/20 Apr 22 19:11:30 yabox qmail: 987981090.181689 delivery 78: success: 166.84.157.1 31_accepted_message./Remote_host_said:_250_2.6.0_message_received_OK/ Apr 22 19:11:30 yabox qmail: 987981090.185858 status: local 1/10 remote 2/20 Apr 22 19:11:30 yabox qmail: 987981090.187104 end msg 889610 Apr 22 19:11:30 yabox qmail: 987981090.215670 new msg 889608 Apr 22 19:11:30 yabox qmail: 987981090.216718 info msg 889608: bytes 738 from qp 22181 uid 1001 Apr 22 19:11:30 yabox qmail: 987981090.276914 starting delivery 82: msg 889608 t o local [EMAIL PROTECTED] Apr 22 19:11:30 yabox qmail: 987981090.279185 status: local 2/10 remote 2/20 Apr 22 19:11:30 yabox qmail: 987981090.430513 new msg 889610 Apr 22 19:11:30 yabox qmail: 987981090.431762 info msg 889610: bytes 738 from qp 18712 uid 1001 Apr 22 19:11:30 yabox qmail: 987981090.516405 starting delivery 83: msg 889610 t o remote [EMAIL PROTECTED] Apr 22 19:11:30 yabox qmail: 987981090.518114 status: local 2/10 remote 3/20 Apr 22 19:11:30 yabox qmail: 987981090.702296 delivery 82: success: did_0+0+1/ Apr 22 19:11:30 yabox qmail: 987981090.705919 status: local 1/10 remote 3/20 Apr 22 19:11:30 yabox qmail: 987981090.707154 end msg 889608 Apr 22 19:11:31 yabox qmail: 987981091.037664 new msg 889613 Apr 22 19:11:31 yabox qmail: 987981091.039118 info msg 889613: bytes 736 from qp 177 uid 1001 Apr 22 19:11:31 yabox qmail: 987981091.142510 delivery 81: success: did_0+0+1/ Apr 22 19:11:31 yabox qmail: 987981091.145945 status: local 0/10 remote 3/20 Apr 22 19:11:31 yabox qmail: 987981091.147719 starting delivery 84: msg 889613 t o remote [EMAIL PROTECTED] Apr 22 19:11:31 yabox qmail: 987981091.148194 status: local 0/10 remote 4/20 Apr 22 19:11:31 yabox qmail: 987981091.148890 end msg 889612 Apr 22 19:11:31 yabox qmail: 987981091.177610 new msg 889608 Apr 22 19:11:31 yabox qmail: 987981091.178866 info msg 889608: bytes 738 from qp 20918 uid 1001 Apr 22 19:11:31 yabox qmail: 987981091.263483 starting delivery 85: msg 889608 t o remote [EMAIL PROTECTED] Apr 22 19:11:31 yabox qmail: 987981091.264972 status: local 0/10 remote 5/20 Apr 22 19:11:31 yabox qmail: 987981091.441239 new msg 889614 Apr 22 19:11:31 yabox qmail: 987981091.442458 info msg 889614: bytes 738 from qp 12203 uid 10
Re: courier imap roaming
on 4/23/01 9:13 AM, Lu at [EMAIL PROTECTED] wrote: > Does --enable-roaming option for vpopmail covers courier imap as well ? > Or do I have to use something like relay-ctrl package ? > > If the latter, does it interfere with the roaming functionality of vpopmail > ? It does work. But last as of 1.3.5, you had to comment out the lines: #ifdef HAVE_OPEN_SMTP_RELAY and the corresponding #endif in authlib/preauthvchkpw.c This is because the ./configure script wasn't working properly. It may be fixed in later versions, though. -Bill
Re: courier imap roaming
courier imap is "supposed" to pick this up automatically, but it doesn't so here's the fix, after your configure, cd courier-imap-1.3.7/authlib grep RELAY config.h make sure it says #define HAVE_OPEN_SMTP_RELAY 1 if it doesn't, well change it... :) Lu writes: > Does --enable-roaming option for vpopmail covers courier imap as well ? > Or do I have to use something like relay-ctrl package ? > > If the latter, does it interfere with the roaming functionality of vpopmail > ? > > Thanks. > > Lu >
courier imap roaming
Does --enable-roaming option for vpopmail covers courier imap as well ? Or do I have to use something like relay-ctrl package ? If the latter, does it interfere with the roaming functionality of vpopmail ? Thanks. Lu
