| |
| |
| |
|
Page: 1 2 3 4 5
Comments:
<0> .ignore Netsnipe
<0> er
<1> *sigh*
<1> I'm using postfix for the first time (been using exim for years now)
<0> hackeron: but if said address DOES send mail, you'd not do that
<1> and I've googled already, read the docs
<1> and nothing is clicking in my head as to what trivial detail I may have left out
<0> Netsnipe: i for one dislike people who insist on their questions to be answered.. right away, or, put it simple as: who're annoying.
<0> nothing to do with you being newbie or not
<1> I've been waiting for help for 30 mins now...and not even one acknowledgement
<1> and I haven't been rude about it either
<1> I don't see how you could call me annoying for that.
<0> 17:59 < Netsnipe> anyone?
<0> 18:11 < Netsnipe> could someone please help me troubleshoot why my maildir setup isn't working?
<0> 18:14 < Netsnipe> hello?
<0> was it you?
<2> mjt: so is this right? http://rafb.net/paste/results/8YWFSk73.html
<0> Netsnipe: while we're at it, show a log line for your successeful delivery
<1> mjt: is there some unwritten rule that states I can't ping for help?
<0> ok. scratch that.
<0> no need to show logs.. to me at least.
<1> Jan 31 02:21:04 espresso postfix/local[24124]: D71CE1D41004: to=<netsnipe@localhost>, relay=local, delay=0, status=sent (delivered to command: /usr/bin/procmail)
<0> hackeron: almost
<2> mjt: heh, whats missing?
<1> main.cf: mailbox_command = procmail -a "$EXTENSION"
<0> smtpd_check_bounce = check_recipient_access hash:/etc/postfix/disallow_bounce
<1> and I've tried "mailbox_command = /usr/bin/procmail -a "$EXTENSION" DEFAULT=$HOME/Maildir/ MAILDIR=$HOME/Maildir" as well
<0> that should be one statement
<2> mjt: oh, crap, lol -- indeed
<0> and the last step you forgot
<0> 18:12 < mjt> ofcourse smtpd_check_bounce should be added to smtpd_restriction_cl***es.
<2> mjt: before or after check_sender_access pcre:/etc/postfix/check_bounce, ?
<0> restriction_cl***es, not recipient_restrictions
<0> as you don't use restriction_cl***es it seems, just add
<0> smtpd_restriction_cl***es = smtpd_check_bounce
<2> heh, yeah
<0> to main.cf
<2> ok, added
<2> and that wont kill my mailserver? :)
<0> also, you may try w/o the pcre map
<0> you may add it to /etc/postfix/blocked_senders, as
<0> <> smtpd_check_bounce
<0> but i'm not sure the latter will work correctly
<0> worth a try... after it works with pcre.
<0> btw, for testing you can move it before permit_mynetworks
<0> and sure it will kill your mailserver and your dog! You've been warned!
<2> heh
<2> but it works for you, right?
<0> not exactly this way but yes
<2> heh, well, here goes nothing
<0> do you understand what's going on with all those rules?
<2> yes, but that did kill my mailserver, lol
<0> how?
<2> restarted with the new config commented out
<0> what's the problem?
<2> not sure yet, restarted but then just connection refused
<0> show logs!
<2> we get hundreds of connections a second, trying to locate the lines
<0> gah. why didn't you tell me before? ;)
<0> search for 'started'
<2> Jan 30 15:29:41 infra postfix/smtpd[9803]: fatal: open database /etc/postfix/disallow_bounce.db: No such file or directory
<2> bah, lol
<2> my bad
<0> are those all legitimate connections, or are you being hammered by spammers or a backscatter?
<0> hundreds/sec is quite a few...
<2> both, got 2 reports from co-workers that mailserver is ****ed :)
<2> ok, 10s a sec more like it but still
<0> btw.. which postfix version do you use?
<2> 2.1.5-9 - on debian stable (sarge)
<0> what does `postconf smtpd_null_access_lookup_key' say?
<0> just to be sure the feature is supported by your postfix version.. it should but i'm not sure.
<2> smtpd_null_access_lookup_key = <>
<0> excellent.
<2> hasnt died yet ;)
<0> hint: that's the lookup key for null sender/recipient -- that /^<>$/ thing
<1> mjt: I figured out my problem
<1> mjt: I hadn't declared both DEFAULT and MAILDIR in /etc/procmailrc
<0> and yes it should work in a hash: map too (your 'bad sender' map)
<3> hello
<1> mjt: if only the documentation had hinted that = /
<0> hackeron: btw, sbl-xbl.spamhaus.org, includes cbl.abuseat.org
<1> what's the purpose of the home_mailbox directive if procmail is the one that's actually doing the file writing?
<0> s/,//
<4> Netsnipe: procmail is optional, local(8) is the default delivery agent
<2> mjt: really? -- ok, removed
<0> blah. Netsnipe is still here? ;)
<1> mjt: you must be my bad karma returning to haunt me for all the years I opped #debian
<0> 17:47 < Netsnipe> I've disabled systemwide procmail
<0> 18:22 < Netsnipe> main.cf: mailbox_command = procmail -a "$EXTENSION"
<4> Netsnipe, if you don't need procmail for filtering, don't use it.
<1> mjt: by disabling I meant I renamed /etc/procmailrc and ~/.procmailrc
<1> rob0: so how else can I make my mail end up in ~/Maildir?
<4> comment out the mailbox_command line, home_mailbox = Maildir/ ... done.
<1> rob0: will that disable ~/.procmailrc then?
<1> s/disable/ignore/
<0> btw, it's all available in the docs (postconf(5) in particular)
<0> The precedence of local(8) delivery features from high to low is:
<0> aliases, .forward files, mailbox_transport_maps, mailbox_transport,
<0> mailbox_command_maps, mailbox_command, home_mailbox, mail_spool_direc-
<0> tory, fallback_transport_maps, fallback_transport and luser_relay.
<0> it's repeated at least 5 times.
<4> If nothing invokes procmail, ~/.procmailrc is ignored. Individual users can use ~/.forward of course ... that's what I do.
<0> 7 times to be exact
<1> heh. I forgot about ~/.forward
<4> I'm the only procmail user on my system.
<1> here I was spending the last hour thinking that exim4 magically called procmail for me and wondering wtf postfix wasn't doing the same
<1> when in fact I was calling procmail from ~/.forward all along
<1> thanks for your help rob0
<1> rob0: I understand postfix a lot better now
<4> yw :)
<4> mjt: did you see that or are you on /ignore ? As it turns out, Netsnipe was using .forward too. :)
<0> i've him on /ignore
<0> but that's not unusual anyway. if postconf says mailbox_command isn't set, the next suspect is ~/.forward.
<0> after the logline of successeful delivery, which mentions postfix/local
<5> dumb question: in master.cf, for commands with command name pipe (like cyrus/uucp), theres no actual process started as with smtp, its sent to the file right? like there is no "pipe" process running when that line gets used
<5> (i'mworking on a NRPE script for nagios)
<0> i can't parse that.
<5> my question?
<0> pipe IS the actual process which is started
<0> it's in /usr/lib/postfix/pipe
<5> ok, so if i did a ps when that was running i'd see pip
<5> ahh, ok
<5> thanks
<0> and it will be shown by ps
<0> but it's not running all the time
<0> only when actually used
<6> warning: SASL authentication failure: cannot connect to Courier authdaemond: Connection refused
<6> anyone? :P
<7> permissions? chroot?
<4> mb_: "Connection refused" usually mean that a process isn't running, in this case, Courier authdaemond.
<4> or chroot yes :)
<6> well
<6> if postfix is in the chroot
<6> how can i do th at?
<6> or how can i disable the chroot?
<7> that isn't a Postfix error
<4> mb_, see DEBUG_README.html#no_chroot
<0> hackeron: so how it works, finally?
<2> mjt: well, the bounces just stopped so I dont know if it works or not, lol -- how do I simulate a bounce?
<0> you can grep that error message in your logs
<0> to simulate a bounce.. well.. use telnet? MAIL FROM:<>, RCPT TO:<sales@...>
<0> but not from $mynetworks, obviously
<0> maybe they disappeared just because of this very stuff? ;)
<6> any clue why i can use the crypted p***word in the mysql db for pop3 but not for smtp?
<6> im using courier
<0> which auth method you're using?
<0> "crypted" p***word (it's actually hashed, not crypted) can only be used with LOGIN mechanism
<6> well, i mean the MD5 Hash
<6> pwcheck method is auxprop
<0> it has nothing to do with your pwcheck method
Return to
#postfix
or
Go to some related
logs:
fedora ruby2 gnome
#perl
#web
gentoo fam gam
gentoo FATAL: module nvidia not found
translate fegad
amd64 vesa-ng
dhcp3D
webmin ubuntu 6
libperl++
|
|