| |
| |
| |
|
Page: 1 2 3 4 5 6
Comments:
<0> morgajel: I just ended up using postcat on each of them and manually feeding them back in via `sendmail`
<0> quite painful :/
<1> agaffney: less painful: postsuper -r ALL
<2> agaffney: eep.
<3> warning: SASL authentication failure: Could not open db => i am getting this, despite having the right permissions on the db, and having saslauthd in pwcheck_method
<3> any other reason i could investigate?
<1> DeathWolf: which mechanism are you using in your saslauthd configuration?
<3> /usr/local/lib/sasl2/smtpd.conf => pwcheck_method: saslauthd
<3> or are you talking of something else?
<1> DeathWolf: saslauthd means the "SASL authentication daemon" which is an additional process running on your system.
<1> DeathWolf: the saslauthd has several possible ways to check the username/p***word of the user. so it depends on how the saslauthd is set up
<3> pam then
<3> that's how the demon is started atm (-a pam)
<1> Okay. So the sasldb isn't used (properly).
<3> what do i check?
<1> Are you sure you put the smtpd.conf into the right location? Is /usr/local/lib/sasl2 the location on your distribution?
<3> yes
<1> You are checking PAM. Depends on your PAM config.
<3> i used freebsd ports, and that's where everything is
<0> ChrisH: bah! and you couldn't have said that earlier when I asked? :P
<1> Does FreeBSD use PAM? I thought it was a Linux invention.
<1> agaffney: Nah... I wanted to keep the tension. :)
<0> that would have "fixed" the broken transport type on them?
<3> freebsd has pam iirc
<3> is there a way to get more verbose info
<1> agaffney: Yes. It reapplies the current content_filter on the mails in the queue.
<1> DeathWolf: Do you want to check your /etc/p***wd or a seperate sasldb2?
<3> a separate sasldb2
<0> ChrisH: that would have been useful information 45 minutes ago :) I'll remember for next time (hopefully there isn't a next time), though :P
<1> DeathWolf: then it's probably "pwcheck_method: pwcheck"
<1> DeathWolf: also see http://www.postfix.org/SASL_README.html#server_cyrus
<3> i am getting the same error, i'll check that readme now
<3> i'm not getting the error anymore after changing to pwcheck_method: auxprop and mech_list: plain login
<3> now it's just rejecting the relay
<3> without any reason
<3> how do i check the reason it's rejecting it?
<3> i get the connect, and next line it's the reject RCPT
<3> (NOQUEUE: reject: RCPT etc)
<3> hum... very weird
<3> how do i tell to accept mails from any origin to any destination?(as long as the authentification is good)
<3> i thought 'all' would work
<3> but obviously it isnt i think
<1> DeathWolf: http://www.postfix.org/SASL_README.html#server_sasl
<3> yeah, all of that is in
<3> i'm not getting anymore sasl errors anyway
<3> hum, maybe sasl isnt working at all
<3> how do i tell the log to be more verbose and show which method it tried and failed?
<3> okay def. nothing even with -vvv
<3> great... the error is back:(
<3> hum... is there actually a simple way to just have postfix use the normal users, no need for tls/ssl, no need for sasl, just simple as hell
<4> saslauthd -a pam|saslauthd -a shadow?
<3> it's already running with -a pam
<5> Uhm... what exactly is Postfix doing on port 10025?
<6> jMCg: listening for resubmission from a content filter?
<7> I am trying to set up my SMTP server with a relayhost using SASL to authenticate with the remote server
<7> however
<7> I am getting this error in /var/log/mail.log
<7> May 30 19:02:27 nighthawk postfix/smtp[4552]: fatal: open database /etc/postfix/sasl_p***wd.db: No such file or directory
<5> lunaphyte, makes sense.
<7> I don't understand how to create the sasl_p***wd.db file, I have /etc/postfix/sasl_p***wd, and it's set to look for that
<3> ok it's working now, but i'm still having a weird prob:
<7> why is it saying it is trying to find /etc/postfix/sasl_p***wd.db
<7> ?
<3> When someone tries to use tls: May 31 01:05:12 arcueid postfix/smtpd[42523]: warning: TLS library problem: 42523:error:14094419:SSL routines:SSL3_READ_BYTES:tlsv1 alert access denied:/iusr/src/secure/lib/libssl/../../../crypto/openssl/ssl/s3_pkt.c:1052:S
<3> (regular works)
<0> brohism: you need to use postmap, I believe
<0> brohism: postmap /etc/postfix/sasl_p***wd
<0> is there a way to exempt hosts from the local network and mail submitted via the commandline from content filtering (via content_filter=)?
<7> agaffney, that got rid of the error...now i just need to see if the mail comes through successfully :)
<0> brohism: any time you make a modification to that file, you need to run postmap on it
<7> ok
<0> same with any file referred to with hash: in your main.cf
<7> thanks for the info, i didn't see that in the postfix docs
<7> ok
<0> such as aliases and transport
<7> ok
<7> good to know
<0> yes, it is :P
<7> lol
<7> it seems to be working fine no
<7> w
<7> thanks
<8> what's Razor2 ?
<9> Jax: used when doing spam filtering
<8> should i activate this in AS ?
<8> *SA
<9> Jax: if you have it installed
<8> it seems to be a SA module
<10> if anyone has postfixadmin on their system could you tell me if theres any mailing list thing in it? i dont have it installed so cant check here
<8> hm do i have to have spamd running if i use SA through amavis?
<11> Jax: Nope
<8> thanks hparker
<11> jnoon_: I had to setup another subdomain and manage mailman with the aliases file
<8> time for bed, gnite
<10> hparker, theres no easy way to do mail lists like if mail is sent to list@domain.com it goes to email1, email2, email3 etc. i dont want all the list managmenet bulk of mailman you know?
<11> Aliases
<11> Though, it's a spammers haven... Anyone can send mail to the alias and spam everyone.. I'm migrating all of mine to lists
<10> ya.. i just want it to verify its from the authenticated person who owns the list... i dont want others to be able to send to it... i guess mailman is the only thing that does that and works with postfix?
<11> afaik, yes
<12> The Postfix mailing lists are Majordomo, but Mailman is the market leader these days.
<11> Well, yeah.. Some mailing list software
<10> maybe ill give it another shot then... it just seems more than i really need but maybe thats fine
<13> how do I configure the retry times to match my own schedule?
<13> say I want the system to retry after 1 minute on the first failure, 10 minutes on the second, 10 minutes on the third?
<4> you can't
<13> o.k. well, if anyone can think of a hack....
<4> write your own MTA?
<4> replace qmgr?
<13> Considering it.
<4> why would you want to do something like that anyway?
<13> I would rather contribute to postfix
<13> Well, I'm not sure I do.
<13> Right now we have an app that needs to control how much mail is stuffed down it's throat, and postfix sits in front of it.
<13> So I'm trying to figure out how to tell postfix that I'm busy and can only handle a few connections right now. Stuff like that.
<4> ah
<4> use a custom transport and transport_maps
<13> I don't really want unnecessary connects and retries.
<14> I'd like to implement a spam******in + postfix scanner. In the past, I'd used a sendmail milter - what do people here like to use?
<4> amavisd-new
<13> f3ew, I don't yet see the connection between transports and control of postfix's output. I might be missing something.
<4> Ahewes make a custom transport in master.cf (clone smtp to make a "slow" transport with limited concurrency
<13> Ahhhh.....
<4> you define the transport in master.cf
<13> very interesting.
<4> then tell Postfix to use it in main.cf via transport_maps
<13> I didn't know you could make a "slow" transport.
<13> Sounds like it has a lot of potential.
<13> thanks. looking into it...
<15> When using sasldb to manage my user's, do I need to actually have physical users in the system, or does it work sort of like using a mysql backend for postfix?
<4> your choice
<15> f3ew: so if I would like to have an account to log in to and send/receive mail on (but don't want to create a user on the system), I could just add the user to the sasldb and everything would work out? (without a mysql backend?)
<12> !virtual
<16> rob0: 'virtual' : a way to configure additional domains and user accounts (that do not need to exist in your /etc/p***wd). See: http://www.postfix.org/VIRTUAL_README.html
<15> rob0: thanks. I'll give it a read :)
<4> birdfish you might want to use Cyrus-IMAP with sasldb
<15> f3ew: I'll also look into Cyrus-IMAP. I've always used Cyrus-SASL before, but I'm not sure what the difference is.
<15> Tonight looks like a learning night!
<4> SASL is the authentication library
<4> IMAP is the POP3/IMAP server
<17> Hi all, I'm having a problem with postfix + mailman. It seems as though postfix will not accept email for a mailman account. any ideas?
<15> When I execute "make WITH_BDB_4 install" I get an error that it doesn't know how to execute the command, but that is what make config told me to do.
<15> What might I be doing incorrectly?
<17> does anyone know if mailman works with virtual domains?
<12> lancealtar, earlier you gave us nothing to go on. Now you've hinted that you're trying to use a virtual (alias or mailbox, not specified) domain. Simplest thing to do with mailman is to use a local(8) domain ($mydestination).
<17> rob0: thanks for your reply.
<12> That can also be done by means of virtual aliasing to something like listname@localhost.
<17> hmm
<17> well, I'm using mysql to do virtual domains
<12> (You would need a Unix account or alias for "listname".)
<17> say I'm hosting virt-domain.com
Return to
#postfix
or
Go to some related
logs:
arris tm502g driver
deviation vedeos
oracle nsubstr
definition of gigahurtz
#php
pyv4l ubuntu
python2.6
#perl
#perl
gentoo x11-drm needs unknown symbol pci_pretty_name
|
|