Postfix Majordomo problem
in [Postfix]
|
Prev: SOLVED: rbl check being skipped - Postfix logs no error onNXDOMAIN, does on SERVFAIL
Next: smtp auth over ssl for smartrelay configuration
From: Ruben Safir on 22 Jan 2010 20:07 > It would help if you posted the log messages you receive along with the information provided here: http://www.postfix.org/DEBUG_README.html. > > After you do that then we can try and help you. > > Thanks, > Daniel > > > > Thanks Daniel The relevant log area says this: an 22 17:49:47 www2 postfix/local[17734]: 0CD789C2B7: to=<hangout(a)mrbrklyn.com>, relay=local, delay=1049, delays=1048/0.05/0/0.71, dsn=4.3.0, status=deferred (temporary failure) Jan 22 17:49:47 www2 postfix/local[17739]: 043719C2BC: to=<hangout(a)nylxs.com>, relay=local, delay=376, delays=375/0.18/0/0.58, dsn=4.3.0, status=deferred (temporary failure) Jan 22 17:49:47 www2 postfix/local[17744]: 556449C284: to=<majordomo(a)nylxs.com>, relay=local, delay=2284, delays=2283/0.01/0/0.57, dsn=4.3.0, status=deferred (temporary failure) Jan 22 17:49:47 www2 postfix/local[17742]: 129A09C25B: to=<majordomo(a)nylxs.com>, relay=local, delay=4728, delays=4727/0.13/0/0.59, dsn=4.3.0, status=deferred (temporary failure) Jan 22 17:49:47 www2 postfix/cleanup[17556]: CB4A49629E: message-id=<20100122224947.CB4A49629E(a)www2.mrbrklyn.com> Jan 22 17:49:47 www2 postfix/bounce[17757]: 129A09C25B: sender delay notification: CB4A49629E Jan 22 17:49:47 www2 postfix/qmgr[2295]: CB4A49629E: from=<>, size=2396, nrcpt=1 (queue active) Jan 22 17:49:47 www2 postfix/trivial-rewrite[17733]: warning: do not list domain mrbrklyn.com in BOTH mydestination and virtual_alias_domains Jan 22 17:49:48 www2 postfix/local[17739]: 98A379C25D: to=<hangout(a)mrbrklyn.com>, relay=local, delay=4551, delays=4550/0.42/0/0.2, dsn=4.3.0, status=deferred (temporary failure) Jan 22 17:49:48 www2 postfix/cleanup[17556]: 017C19C258: message-id=<20100122224948.017C19C258(a)www2.mrbrklyn.com> Jan 22 17:49:48 www2 postfix/local[17744]: 7AFB89C25A: to=<majordomo(a)mrbrklyn.com>, relay=local, delay=4690, delays=4689/0.6/0/0.27, dsn=4.3.0, status=deferred (temporary failure) Jan 22 17:49:48 www2 postfix/cleanup[17783]: 1A3179C260: message-id=<20100122224948.1A3179C260(a)www2.mrbrklyn.com> Jan 22 17:49:48 www2 postfix/local[17742]: 94E5D9C259: to=<majordomo(a)nylxs.com>, relay=local, delay=4745, delays=4744/0.44/0/0.41, dsn=4.3.0, status=deferred (temporary failure) Jan 22 17:49:48 www2 postfix/local[17734]: C1FCE56E8A: to=<hangout(a)mrbrklyn.com>, relay=local, delay=22800, delays=22800/0.35/0/0.41, dsn=4.3.0, status=deferred (temporary failure) Jan 22 17:49:48 www2 postfix/cleanup[17787]: 3F9379C2AF: message-id=<20100122224948.3F9379C2AF(a)www2.mrbrklyn.com> Jan 22 17:49:48 www2 postfix/bounce[17760]: 98A379C25D: sender delay notification: 017C19C258 Jan 22 17:49:48 www2 postfix/local[17767]: CB4A49629E: to=<ruben(a)mrbrklyn.com>, relay=local, delay=0.53, delays=0.09/0/0/0.44, dsn=2.0.0, status=sent (delivered to command: exec /usr/bin/procmail) Jan 22 17:49:48 www2 postfix/local[17739]: DEED79C25F: to=<hangout(a)nylxs.com>, relay=local, delay=4540, delays=4539/0.53/0/0.37, dsn=4.3.0, status=deferred (temporary failure) Jan 22 17:49:48 www2 postfix/bounce[17759]: 7AFB89C25A: sender delay notification: 1A3179C260 Jan 22 17:49:48 www2 postfix/qmgr[2295]: 1A3179C260: from=<>, size=2806, nrcpt=1 (queue active) Jan 22 17:49:48 www2 postfix/qmgr[2295]: CB4A49629E: removed Jan 22 17:49:48 www2 postfix/local[17744]: BC32D56E6D: to=<majordomo(a)mrbrklyn.com>, relay=local, delay=13182, delays=13181/0.65/0/0.35, dsn=4.3.0, status=deferred (temporary failure) Jan 22 17:49:48 www2 postfix/cleanup[17556]: 6A8059629E: message-id=<20100122224948.6A8059629E(a)www2.mrbrklyn.com> Jan 22 17:49:48 www2 postfix/qmgr[2295]: 3F9379C2AF: from=<>, size=2396, nrcpt=1 (queue active) Jan 22 17:49:48 www2 postfix/trivial-rewrite[17733]: warning: do not list domain mrbrklyn.com in BOTH mydestination and virtual_alias_domains Jan 22 17:49:48 www2 postfix/bounce[17758]: 94E5D9C259: sender delay notification: 3F9379C2AF Jan 22 17:49:48 www2 postfix/qmgr[2295]: 017C19C258: from=<>, size=2742, nrcpt=1 (queue active) Jan 22 17:49:48 www2 postfix/local[17739]: 3F9379C2AF: to=<ruben(a)mrbrklyn.com>, relay=local, delay=0.27, delays=0.19/0.06/0/0.02, dsn=2.0.0, status=sent (delivered to command: exec /usr/bin/procmail) Jan 22 17:49:48 www2 postfix/local[17742]: D922A9C2BA: to=<hangout(a)mrbrklyn.com>, relay=local, delay=483, delays=482/0.77/0/0.29, dsn=4.3.0, status=deferred (temporary failure) Jan 22 17:49:48 www2 postfix/local[17734]: F12499C282: to=<majordomo(a)nylxs.com>, relay=local, delay=2286, delays=2285/0.74/0/0.29, dsn=4.3.0, status=deferred (temporary failure) Not I just mucked with the majordomo.cf file and change the load allowance from 10 to 90: You can force Majordomo to delay any processing if the system load is too # high by uncommenting the following lines. THIS ONLY WORKS if your "uptime" # command (usually found in /usr/bin/uptime or /usr/bsd/uptime) # returns a string like: # 5:23pm up 5:51, 9 users, load average: 0.19, 0.25, 0.33 # $max_loadavg = 90; # Choose the maximum allowed load # $uptime = `/usr/bin/uptime` if -x '/usr/bin/uptime'; # Get system uptime #$uptime = `/usr/bsd/uptime` if -x '/usr/bsd/uptime'; # or uptime is over here. # ($avg_1_minute, $avg_5_minutes, $avg_15_minutes) = $uptime =~ /average:\s+(\S+),\s+(\S+),\s+(\S+)/; print STDERR $uptime; print STDERR $avg_15_min; print STDERR $max_loadavg; # exit 75 if ($avg_15_minutes >= $max_loadavg); # E_TEMPFAIL # And now it seems to be working And this is what I was afraid of. I'm thinking this is almost like a denial of service attack so it is a combination of issues involving both postfix and majordomo. I'm sorry for being such a green newbie to postfix, but I've worked with sendmail for nearly the last decade, and while never really mastering M4's, I got used to getting around it. postfix seems like just a completely different animal and it's taking some time for me to get my dense head through its basic set up. But one thing I think I need to do right away is get SORBS or something like it to deny access from blackholed domains? What is the most straight forward way of doing that. It seems that there is more than one approach. In sendmail I used to just add it to the access database. Once I slow down the spambots, I think I'll end a large number of problems. Ruben > > > . > >
From: Ruben Safir on 22 Jan 2010 20:15
On 01/22/2010 07:58 PM, Wietse Venema wrote: > Majordomo is a Perl script, so you can debug it with all the standard > Perl debugging features. > > This discussion is no longer appropriate for the Postfix mailing > list, so this is my last post. > Thanks for the help. What you've told me has been very helpful to getting this debugged. FWIW, I finally, even before this interact, just removed the mdomo packages and reinstalled them. Because, who knows? Maybe I'm overlooking something. It didn't help. I tried to run mail directly through majordomo, as you also pointed out, and it seems to function. That was weird. FWIW...my hard earned experience has taught me that packages aren't the be all of everything, like mana from heaven. There are a lot things I've had to install be hand to get rid of bugs in packages. This isn't intended to get into a flame war on packages, I'm just stating my experience. What do you do when packages don't work? You roll up your sleeves, do a lot of reading, comb though source code, and if your lucky, someone smarter than you, someone like yourself, can give you a moment of their free time and point you in the right direction. And for that, I'm grateful and thank you for your time! Ruben |