Re: [courier-users] Problems with mails sent by PHP

2007-06-18 Thread Bernd Wurst
Hi. I can confirm what Sam sais, I also didn't get what your problem really is... Am Dienstag, 19. Juni 2007 schrieb Bernd Plagge: > When I set this up I got a >  454 TLS missing certificate: > > error and the solution was to set up a smarthost without TLS. ...but THIS should never be called a

Re: [courier-users] Problems with mails sent by PHP

2007-06-18 Thread Sam Varshavchik
Bernd Plagge writes: Sam, while you're right in saying that the message comes from qmail you are not right in stating that I made something up in 'thin air'. The machine the mail was sent from is running Courier and it is also serving as a backup MX for some domains - although NOT for the doma

[courier-users] Problems with mails sent by PHP

2007-06-18 Thread Bernd Plagge
Sam, while you're right in saying that the message comes from qmail you are not right in stating that I made something up in 'thin air'. The machine the mail was sent from is running Courier and it is also serving as a backup MX for some domains - although NOT for the domain in question. When I

Re: [courier-users] Problems with mails sent by PHP

2007-06-18 Thread Jeff Jansen
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Bernd Plagge wrote: > This should send 1 mail to [EMAIL PROTECTED] and 1 mail to > [EMAIL PROTECTED] > > Jun 15 11:26:22 tokyo courieresmtp: > id=0001044A.4671F8CC.752A,from=<[EMAIL PROTECTED]>,addr=<[EMAIL > PROTECTED]>: > 553 sorry, that doma

Re: [courier-users] Problems with mails sent by PHP

2007-06-18 Thread Sam Varshavchik
Bernd Plagge writes: Sam, I'm not sure why you treat me like that. While I changed domain names I did this in a consistent manner - because it is no good to find all the data in Google. I posted actual PHP code and actual log entries. ... but then again, I can read the code myself - just tak

[courier-users] Problems with mails sent by PHP

2007-06-18 Thread Bernd Plagge
Sam, I'm not sure why you treat me like that. While I changed domain names I did this in a consistent manner - because it is no good to find all the data in Google. I posted actual PHP code and actual log entries. ... but then again, I can read the code myself - just takes me a bit longer. Reg

Re: [courier-users] gdbm on OpenBSD; was "Adding a doma in to Courier"

2007-06-18 Thread Sam Varshavchik
Gordon Messmer writes: Steve Shockley wrote: courieresmtpd: submitclient: EOF from submit. courieresmtpd: error,relay=66.133.182.167,msg="502 ESMTP command error",cmd: DATA courieresmtpd: gdbm fatal: couldn't init cache courieresmtpd: gdbm fatal: couldn't init cache This problem has been r

[courier-users] gdbm on OpenBSD; was "Adding a domain to Courier"

2007-06-18 Thread Gordon Messmer
Steve Shockley wrote: > courieresmtpd: submitclient: EOF from submit. > courieresmtpd: error,relay=66.133.182.167,msg="502 ESMTP command > error",cmd: DATA > courieresmtpd: gdbm fatal: couldn't init cache > courieresmtpd: gdbm fatal: couldn't init cache This problem has been reported a few times

Re: [courier-users] Problems with mails sent by PHP

2007-06-18 Thread Gordon Messmer
Sam Varshavchik wrote: > Gordon Messmer writes: >> >> My guess is that you've modified "esmtpaccess/default", so that >> 127.0.0.1 is no longer a "RELAYCLIENT". > > Wrong guess. It wouldn't be the first time. Especially in the morning. > The above error message is from qmail. > > Do you now u

Re: [courier-users] Log usernames or login names

2007-06-18 Thread Sam Varshavchik
Roger Schreiter writes: Hi, in /var/log/mail I can find a log line for each email sent by courier. Unfortunately I don't see the owner of the emails. I.e. the unix username, when email was sent via courier's sendmail command. Or the login name, when email was delivered via ESMTP. This does ma

[courier-users] Log usernames or login names

2007-06-18 Thread Roger Schreiter
Hi, in /var/log/mail I can find a log line for each email sent by courier. Unfortunately I don't see the owner of the emails. I.e. the unix username, when email was sent via courier's sendmail command. Or the login name, when email was delivered via ESMTP. This does make it very difficult to inv

Re: [courier-users] Problems with mails sent by PHP

2007-06-18 Thread Sam Varshavchik
Gordon Messmer writes: Bernd Plagge wrote: Jun 15 11:26:22 tokyo courieresmtp: id=0001044A.4671F8CC.752A,from=<[EMAIL PROTECTED]>,addr=<[EMAIL PROTECTED]>: 553 sorry, that domain isn't in my list of allowed rcpthosts (#5.5.3 - chkuser) My guess is that you've modified "esmtpaccess/defa

Re: [courier-users] LDAP based aliasing and recursion

2007-06-18 Thread Gordon Messmer
Jürgen Walch wrote: > This kind of 'recursion' doesn't seem to work with LDAP based aliases. > > Is this a feature, a bug or am I missing something here ? ldapaliasd doesn't have code to detect loops in nested aliases, so it's currently not supported. ---

[courier-users] LDAP based aliasing and recursion

2007-06-18 Thread Jürgen Walch
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi! we recently made one of our servers running courier 0.55.1 use LDAP based aliasing. The LDAP server used is Fedora-DS 1.04. Resolving aliases seems to work fine except for one thing: Using aliases set up with 'makealiases' I can do something like

Re: [courier-users] Problems with mails sent by PHP

2007-06-18 Thread Gordon Messmer
Bernd Plagge wrote: > Jun 15 11:26:22 tokyo courieresmtp: > id=0001044A.4671F8CC.752A,from=<[EMAIL PROTECTED]>,addr=<[EMAIL > PROTECTED]>: > 553 sorry, that domain isn't in my list of allowed rcpthosts (#5.5.3 - > chkuser) My guess is that you've modified "esmtpaccess/default", so that 12

Re: [courier-users] Still maildrop

2007-06-18 Thread Rocco Scappatura
> >> How are you using maildrop? Where, in processing your incoming > >> email, is it invoked? Your question doesn't say. > > > > I'm trying to setup Maildrop filtering for many reasons (adding > > disclaimer, put spam email in an ad hoc folder and so on). > > > > I'm using a Postfix+MySQL+Cour

Re: [courier-users] Still maildrop

2007-06-18 Thread Tim Hunter
Rocco Scappatura wrote: >> How are you using maildrop? Where, in processing your >> incoming email, is it invoked? Your question doesn't say. > > I'm trying to setup Maildrop filtering for many reasons (adding > disclaimer, put spam email in an ad hoc folder and so on). > > I'm using a Postfix+My

Re: [courier-users] Still maildrop

2007-06-18 Thread Lindsay Haisley
So you're invoking Maildrop from Postfix, yes? I'm not familiar with Postfix, so I can comment on the correctness of the invocation in your master.cf file. I'd suggest a fallback to a simple debugging setup. Create /tmp/maildrop.log with mode 666 and put the following lines in your /etc/courier/m

Re: [courier-users] Still maildrop

2007-06-18 Thread Rocco Scappatura
> How are you using maildrop? Where, in processing your > incoming email, is it invoked? Your question doesn't say. I'm trying to setup Maildrop filtering for many reasons (adding disclaimer, put spam email in an ad hoc folder and so on). I'm using a Postfix+MySQL+Courier-IMAP platform. I'm u

Re: [courier-users] Still maildrop

2007-06-18 Thread Lindsay Haisley
On Mon, 2007-06-18 at 09:14 +0200, Rocco Scappatura wrote: > The proble is that when I receive an email for one of my mailbox, > that message is not scanned by maildrop How are you using maildrop? Where, in processing your incoming email, is it invoked? Your question doesn't say. -- Lindsay H

Re: [courier-users] Still maildrop

2007-06-18 Thread Rocco Scappatura
> This doesn't appear to be a Courier issue as you've stated > the question. > You're using Courier-IMAP to provide access to stored mail > after it's been delivered, but you don't mention using > maildrop as your delivery agent, except in your subject header. > > If you were using Maildrop and