Re: [toaster] qmail maillog

[David]

- Original Message - 
From: "List" <[EMAIL PROTECTED]>
To: 
Sent: Monday, April 04, 2005 4:20 PM
Subject: Re: [toaster] qmail maillog


List wrote:
Hi List,
I had install a fresh toaster and everything is running fine except that 
the incoming connections are not logged into /var/log/maillog. How can i 
make the connections log into the maillog file? I am running the lastest 
toaster with FC3.
You need to use splogger instead of multilog if you want to log to 
syslog. See the qmail docs for how to set that up.  This toaster uses 
multilog.
Hi,
Another question. How can I log vpopmail connections into 
/var/log/maillog? I have a RH9 running toaster 0.61 and have a log like
Apr  4 14:56:17 advanced vpopmail[16375]: vchkpw-pop3: (PLAIN) login 
success [EMAIL PROTECTED]:220.225.58.53
I believe the latest version of the toaster does that.
From a Shupp 0.7.9 toaster - /var/log/maillog:
Apr  4 16:33:45 ns vpopmail[20286]: vchkpw-pop3: (PLAIN) login success 
[EMAIL PROTECTED]:192.168.1.102
Apr  4 16:33:45 ns vpopmail[20288]: vchkpw-pop3: (PLAIN) login success 
[EMAIL PROTECTED]:192.168.1.102

etc.
David.
regards
!DSPAM:4250e3b8111719412120352!

Re: [toaster] qmail maillog

[List]

List wrote:
Hi List,
I had install a fresh toaster and everything is running fine except 
that the incoming connections are not logged into /var/log/maillog. How 
can i make the connections log into the maillog file? I am running the 
lastest toaster with FC3.
You need to use splogger instead of multilog if you want to log to 
syslog. See the qmail docs for how to set that up.  This toaster uses 
multilog.
Hi,
Another question. How can I log vpopmail connections into 
/var/log/maillog? I have a RH9 running toaster 0.61 and have a log like
Apr  4 14:56:17 advanced vpopmail[16375]: vchkpw-pop3: (PLAIN) login 
success [EMAIL PROTECTED]:220.225.58.53
I believe the latest version of the toaster does that.
From a Shupp 0.7.9 toaster - /var/log/maillog:
Apr  4 16:33:45 ns vpopmail[20286]: vchkpw-pop3: (PLAIN) login success 
[EMAIL PROTECTED]:192.168.1.102
Apr  4 16:33:45 ns vpopmail[20288]: vchkpw-pop3: (PLAIN) login success 
[EMAIL PROTECTED]:192.168.1.102

I am using the lastest which is 0.7.9 but i dont seem to log anything to 
maillog.
I believed vpopmail is properly configure.

$ 
./configure --enable-roaming-users --enable-learn-passwords --enable-domainquotas 
--enable-logging=v

But it is still not logging.
Help?! 

[toaster] TLS connect failed

[Ingo Claro]

Hello all,

i've encountered the following bounce from my server:

<[EMAIL PROTECTED]>:
TLS connect failed; connected to xxx.xxx.xxx.xxx.
I'm not going to try again; this message has been in the queue too long.

anyone knows why it happens?

regards,
Ingo

Re: [toaster] qmail maillog

[Bill Shupp]

List wrote:
I am using the lastest which is 0.7.9 but i dont seem to log anything to 
maillog.
I believed vpopmail is properly configure.

$ ./configure --enable-roaming-users --enable-learn-passwords 
--enable-domainquotas --enable-logging=v

But it is still not logging.
Figure out where Syslog is logging your MAIL facility.  Perhaps it's not 
maillog.  T
he configuration above will log to the MAIL facility.

Regards,
Bill

[toaster] TLS connect failed

[Pollack, David]

> There are a couple of things to check here. 
> 
> * Look in /var/log/qmail/qmail-send/current - are you seeing
> permissions errors for "clientcert.pem" and /or "servercert.pem"?
> * Make sure you have servercert.pem and clientcert.pem in
> /var/qmail/control, and that they are readable by the user that is running
> qmail.  The simplest thing to do is to chown the files so that the qmail
> group is the owner - this way you're sure that all the qmail users can
> read it. 
> * If this is happening with only ONE host on the intenet - like, it
> always fails to "domain.com" - there's a chance that the remote server is
> not configured correctly for TLS, but is saying that it is. 
> 
> You can test this like this: 
> 
> slimy:~> telnet mx1.domain.com 25 
> Trying 216.251.32.71... 
> Connected to mx1.domain.com. 
> Escape character is '^]'. 
> 220 mail107.domain.com ESMTP Sendmail 8.13.1/8.13.1; Thu, 31 Mar 2005
> 12:01:12 -0500 
> ehlo domain.com 
> 250-mail107.domain.com Hello slimy.dreamhost.com [205.196.208.18], pleased
> to meet you 
> 250-ENHANCEDSTATUSCODES 
> 250-PIPELINING 
> 250-8BITMIME 
> 250-SIZE 52428800 
> 250-DSN 
> 250-AUTH PLAIN LOGIN 
> 250-STARTTLS 
> 250-DELIVERBY 
> 250 HELP 
> starttls 
> 220 2.0.0 Ready to start TLS 
> 
> 
> If you cant execute the "STARTTLS" command, somehting could be wrong on
> the remote server.
> 
> Good luck,
> david
> 
> -Original Message-
> From: Ingo Claro [mailto:[EMAIL PROTECTED]  ] 
> Sent: Monday, April 04, 2005 11:41 AM
> To: toaster@shupp.org
> Subject: [toaster] TLS connect failed
> 
> Hello all,
> 
> i've encountered the following bounce from my server:
> 
> <[EMAIL PROTECTED]>:
> TLS connect failed; connected to xxx.xxx.xxx.xxx.
> I'm not going to try again; this message has been in the queue too long.
> 
> anyone knows why it happens?
> 
> regards,
> Ingo
> 
<>

RE: [toaster] TLS connect failed

[Ingo Claro]

David:

that was it! i get the following:

250-TLS
250-HELP
250-STARTTLS
250-DSN
250-SIZE 2048
250-8BITMIME
250 PIPELINING
starttls
220 Ready to start TLS
Connection closed by foreign host.

the server closed the connection inmediatly after doing the starttls. So
it's a problem in the other server.

regards,
Ingo

_ 
De: Pollack, David [mailto:[EMAIL PROTECTED] 
Enviado el: Lunes, 04 de Abril de 2005 13:05
Para:   'toaster@shupp.org'
Asunto: [toaster] TLS connect failed

There are a couple of things to check here. 

*   Look in /var/log/qmail/qmail-send/current - are you seeing
permissions errors for "clientcert.pem" and /or "servercert.pem"?
*   Make sure you have servercert.pem and clientcert.pem in
/var/qmail/control, and that they are readable by the user that is running
qmail.  The simplest thing to do is to chown the files so that the qmail
group is the owner - this way you're sure that all the qmail users can read
it. 
*   If this is happening with only ONE host on the intenet - like, it
always fails to "domain.com" - there's a chance that the remote server is
not configured correctly for TLS, but is saying that it is. 

You can test this like this: 

slimy:~> telnet mx1.domain.com 25 
Trying 216.251.32.71... 
Connected to mx1.domain.com. 
Escape character is '^]'. 
220 mail107.domain.com ESMTP Sendmail 8.13.1/8.13.1; Thu, 31 Mar 2005
12:01:12 -0500 
ehlo domain.com 
250-mail107.domain.com Hello slimy.dreamhost.com [205.196.208.18], pleased
to meet you 
250-ENHANCEDSTATUSCODES 
250-PIPELINING 
250-8BITMIME 
250-SIZE 52428800 
250-DSN 
250-AUTH PLAIN LOGIN 
250-STARTTLS 
250-DELIVERBY 
250 HELP 
starttls 
220 2.0.0 Ready to start TLS 


If you cant execute the "STARTTLS" command, somehting could be wrong on the
remote server.

Good luck,
david

-Original Message-
From: Ingo Claro [mailto:[EMAIL PROTECTED] 
Sent: Monday, April 04, 2005 11:41 AM
To: toaster@shupp.org
Subject: [toaster] TLS connect failed

Hello all,

i've encountered the following bounce from my server:

<[EMAIL PROTECTED]>:
TLS connect failed; connected to xxx.xxx.xxx.xxx.
I'm not going to try again; this message has been in the queue too long.

anyone knows why it happens?

regards,
Ingo

RE: [toaster] TLS connect failed

[David Pollack]

Cool. Quite likely, the  firewall between that server & the internet is not
configured to allow TLS thru.

Cheers,
david

-Original Message-
From: Ingo Claro [mailto:[EMAIL PROTECTED] 
Sent: Monday, April 04, 2005 12:34 PM
To: toaster@shupp.org
Subject: RE: [toaster] TLS connect failed

David:

that was it! i get the following:

250-TLS
250-HELP
250-STARTTLS
250-DSN
250-SIZE 2048
250-8BITMIME
250 PIPELINING
starttls
220 Ready to start TLS
Connection closed by foreign host.

the server closed the connection inmediatly after doing the starttls. So
it's a problem in the other server.

regards,
Ingo

_ 
De: Pollack, David [mailto:[EMAIL PROTECTED] 
Enviado el: Lunes, 04 de Abril de 2005 13:05
Para:   'toaster@shupp.org'
Asunto: [toaster] TLS connect failed

There are a couple of things to check here. 

*   Look in /var/log/qmail/qmail-send/current - are you seeing
permissions errors for "clientcert.pem" and /or "servercert.pem"?
*   Make sure you have servercert.pem and clientcert.pem in
/var/qmail/control, and that they are readable by the user that is running
qmail.  The simplest thing to do is to chown the files so that the qmail
group is the owner - this way you're sure that all the qmail users can read
it. 
*   If this is happening with only ONE host on the intenet - like, it
always fails to "domain.com" - there's a chance that the remote server is
not configured correctly for TLS, but is saying that it is. 

You can test this like this: 

slimy:~> telnet mx1.domain.com 25
Trying 216.251.32.71... 
Connected to mx1.domain.com. 
Escape character is '^]'. 
220 mail107.domain.com ESMTP Sendmail 8.13.1/8.13.1; Thu, 31 Mar 2005
12:01:12 -0500
ehlo domain.com
250-mail107.domain.com Hello slimy.dreamhost.com [205.196.208.18], pleased
to meet you 250-ENHANCEDSTATUSCODES 250-PIPELINING 250-8BITMIME 250-SIZE
52428800 250-DSN 250-AUTH PLAIN LOGIN 250-STARTTLS 250-DELIVERBY 250 HELP
starttls 220 2.0.0 Ready to start TLS 


If you cant execute the "STARTTLS" command, somehting could be wrong on the
remote server.

Good luck,
david

-Original Message-
From: Ingo Claro [mailto:[EMAIL PROTECTED]
Sent: Monday, April 04, 2005 11:41 AM
To: toaster@shupp.org
Subject: [toaster] TLS connect failed

Hello all,

i've encountered the following bounce from my server:

<[EMAIL PROTECTED]>:
TLS connect failed; connected to xxx.xxx.xxx.xxx.
I'm not going to try again; this message has been in the queue too long.

anyone knows why it happens?

regards,
Ingo

RE: [toaster] TLS connect failed

[Ingo Claro]

David:

but isn't the communication still in port 25? What config requires the
firewall? 

atte,
Ingo Claro 
Gerente de Operaciones
[EMAIL PROTECTED] 
(+56-2) 43 00 155



-Mensaje original-
De: David Pollack [mailto:[EMAIL PROTECTED] 
Enviado el: Lunes, 04 de Abril de 2005 12:44
Para: toaster@shupp.org
Asunto: RE: [toaster] TLS connect failed

Cool. Quite likely, the  firewall between that server & the internet is not
configured to allow TLS thru.

Cheers,
david

-Original Message-
From: Ingo Claro [mailto:[EMAIL PROTECTED]
Sent: Monday, April 04, 2005 12:34 PM
To: toaster@shupp.org
Subject: RE: [toaster] TLS connect failed

David:

that was it! i get the following:

250-TLS
250-HELP
250-STARTTLS
250-DSN
250-SIZE 2048
250-8BITMIME
250 PIPELINING
starttls
220 Ready to start TLS
Connection closed by foreign host.

the server closed the connection inmediatly after doing the starttls. So
it's a problem in the other server.

regards,
Ingo

_ 
De: Pollack, David [mailto:[EMAIL PROTECTED] 
Enviado el: Lunes, 04 de Abril de 2005 13:05
Para:   'toaster@shupp.org'
Asunto: [toaster] TLS connect failed

There are a couple of things to check here. 

*   Look in /var/log/qmail/qmail-send/current - are you seeing
permissions errors for "clientcert.pem" and /or "servercert.pem"?
*   Make sure you have servercert.pem and clientcert.pem in
/var/qmail/control, and that they are readable by the user that is running
qmail.  The simplest thing to do is to chown the files so that the qmail
group is the owner - this way you're sure that all the qmail users can read
it. 
*   If this is happening with only ONE host on the intenet - like, it
always fails to "domain.com" - there's a chance that the remote server is
not configured correctly for TLS, but is saying that it is. 

You can test this like this: 

slimy:~> telnet mx1.domain.com 25
Trying 216.251.32.71... 
Connected to mx1.domain.com. 
Escape character is '^]'. 
220 mail107.domain.com ESMTP Sendmail 8.13.1/8.13.1; Thu, 31 Mar 2005
12:01:12 -0500
ehlo domain.com
250-mail107.domain.com Hello slimy.dreamhost.com [205.196.208.18], pleased
to meet you 250-ENHANCEDSTATUSCODES 250-PIPELINING 250-8BITMIME 250-SIZE
52428800 250-DSN 250-AUTH PLAIN LOGIN 250-STARTTLS 250-DELIVERBY 250 HELP
starttls 220 2.0.0 Ready to start TLS 


If you cant execute the "STARTTLS" command, somehting could be wrong on the
remote server.

Good luck,
david

-Original Message-
From: Ingo Claro [mailto:[EMAIL PROTECTED]
Sent: Monday, April 04, 2005 11:41 AM
To: toaster@shupp.org
Subject: [toaster] TLS connect failed

Hello all,

i've encountered the following bounce from my server:

<[EMAIL PROTECTED]>:
TLS connect failed; connected to xxx.xxx.xxx.xxx.
I'm not going to try again; this message has been in the queue too long.

anyone knows why it happens?

regards,
Ingo

Re: [toaster] TLS connect failed

[Jason 'XenoPhage' Frisvold]

Ingo Claro wrote:

>David:
>
>but isn't the communication still in port 25? What config requires the
>firewall? 
>  
>

Some firewalls, most notably the Cisco PIX, like to "fix-up" the SMTP
protocol for you.  And if you're not aware of it, it's a real pain ...

>atte,
>   Ingo Claro 
>Gerente de Operaciones
>[EMAIL PROTECTED] 
>(+56-2) 43 00 155
>  
>


-- 
---
Jason 'XenoPhage' Frisvold
Engine / Technology Programmer
[EMAIL PROTECTED]
RedHat Certified - RHCE # 803004140609871
MySQL Pro Certified - ID# 207171862
MySQL Core Certified - ID# 205982910
---
"Something mysterious is formed, born in the silent void. Waiting alone and 
unmoving, it is at once still and yet in constant motion. It is the source of 
all programs. I do not know its name, so I will call it the Tao of Programming."

RE: [toaster] TLS connect failed

[Ingo Claro]

Jason:

ok, thanks for the aclaration. 

regards,
Ingo Claro 



-Mensaje original-
De: Jason 'XenoPhage' Frisvold [mailto:[EMAIL PROTECTED] 
Enviado el: Lunes, 04 de Abril de 2005 13:18
Para: toaster@shupp.org
Asunto: Re: [toaster] TLS connect failed

Ingo Claro wrote:

>David:
>
>but isn't the communication still in port 25? What config requires the 
>firewall?
>  
>

Some firewalls, most notably the Cisco PIX, like to "fix-up" the SMTP
protocol for you.  And if you're not aware of it, it's a real pain ...

>atte,
>   Ingo Claro
>Gerente de Operaciones
>[EMAIL PROTECTED]
>(+56-2) 43 00 155
>  
>


-- 
---
Jason 'XenoPhage' Frisvold
Engine / Technology Programmer
[EMAIL PROTECTED]
RedHat Certified - RHCE # 803004140609871
MySQL Pro Certified - ID# 207171862
MySQL Core Certified - ID# 205982910
---
"Something mysterious is formed, born in the silent void. Waiting alone and
unmoving, it is at once still and yet in constant motion. It is the source
of all programs. I do not know its name, so I will call it the Tao of
Programming."

Re: [toaster] qmail maillog

[List]

List wrote:
I am using the lastest which is 0.7.9 but i dont seem to log anything to 
maillog.
I believed vpopmail is properly configure.

$ 
./configure --enable-roaming-users --enable-learn-passwords --enable-domainquotas 
 --enable-logging=v

But it is still not logging.
Figure out where Syslog is logging your MAIL facility.  Perhaps it's not 
maillog.  T
he configuration above will log to the MAIL facility.
In /etc/syslog.conf
It says :-
# Log all the mail messages in one place.
mail.*  /var/log/maillog
Is there any other place i should look into? 

Re: [toaster] qmail maillog (Solved)

[List]

- Original Message - 
From: "List" <[EMAIL PROTECTED]>
To: 
Sent: Tuesday, April 05, 2005 3:09 AM
Subject: Re: [toaster] qmail maillog


List wrote:
I am using the lastest which is 0.7.9 but i dont seem to log anything to 
maillog.
I believed vpopmail is properly configure.

$ 
./configure --enable-roaming-users --enable-learn-passwords --enable-domainquotas 
 --enable-logging=v

But it is still not logging.
Figure out where Syslog is logging your MAIL facility.  Perhaps it's not 
maillog.  T
he configuration above will log to the MAIL facility.
In /etc/syslog.conf
It says :-
# Log all the mail messages in one place.
mail.*  /var/log/maillog
Is there any other place i should look into?
I re-configure vpopmail with --enable-logging=y instead and now i can see 
the vpopmail connections in /var/log/maillog.

Thanks alot 

Re: [toaster] qmail maillog

[Bob Hutchinson]

On Monday 04 Apr 2005 20:09, List wrote:
> > List wrote:
> >> I am using the lastest which is 0.7.9 but i dont seem to log anything to
> >> maillog.
> >> I believed vpopmail is properly configure.
> >>
> >> $
> >> ./configure --enable-roaming-users --enable-learn-passwords
> >> --enable-domainquotas --enable-logging=v
> >>
> >> But it is still not logging.
> >
> > Figure out where Syslog is logging your MAIL facility.  Perhaps it's not
> > maillog.  T
> > he configuration above will log to the MAIL facility.
>
> In /etc/syslog.conf
>
> It says :-
>
> # Log all the mail messages in one place.
> mail.*  /var/log/maillog
>
> Is there any other place i should look into?

how about trying

grep -r 'vpopmail' /var/log/*

then pick through the output.

login to pop3 with a false login/pw deliberately, that should appear in the 
log

HTH
-- 
-
Bob Hutchinson
Midwales dot com
-

[toaster] Patching

[Michael Di Martino]

I know this is not the right list but my google searchs have come up empty.

What is the proper syntax for patching code (software) on linux.

For example I trying to patch mess833 but I havbe is the patch code.. How is 
that patch applied?

Thanks in advance.
Regards,
Michael Di Martino
Director of MIS
The telx Group
Office: 212 480 3300  X.2022
Cell: 646 207 6603
[EMAIL PROTECTED]
--
Sent from my BlackBerry Wireless Handheld

Re: [toaster] Patching

[Rick Macdougall]

Michael Di Martino wrote:
I know this is not the right list but my google searchs have come up empty.
What is the proper syntax for patching code (software) on linux.
For example I trying to patch mess833 but I havbe is the patch code.. How is 
that patch applied?
Thanks in advance.
Regards,
Michael Di Martino
Hi,
Many ways...
cat patch.file | patch -p0
patch -p0 < patch.file
etc
You might want -p0 or -p1 depending on the patch type.  You might or 
might not want to be in the same directory as the original files 
depending on the patch type.

Usually looking at the first few lines of the patch will let you know.
Regards,
Rick

Re: [toaster] Patching

[Tom Collins]

On Apr 4, 2005, at 5:27 PM, Rick Macdougall wrote:
patch -p0 < patch.file
etc
You might want -p0 or -p1 depending on the patch type.  You might or 
might not want to be in the same directory as the original files 
depending on the patch type.
I always like to include the '--dry-run' option to patch the first time 
through, in case I used the wrong -p option or there are other problems 
(like patches that aren't going to apply correctly).

Once I'm confident it will run smoothly, I just remove the --dry-run 
from the last command.

--
Tom Collins  -  [EMAIL PROTECTED]
QmailAdmin: http://qmailadmin.sf.net/  Vpopmail: http://vpopmail.sf.net/
You don't need a laptop to troubleshoot high-speed Internet: 
sniffter.com

Re: [toaster] Patching

[Bill Shupp]

Tom Collins wrote:
On Apr 4, 2005, at 5:27 PM, Rick Macdougall wrote:
patch -p0 < patch.file
etc
You might want -p0 or -p1 depending on the patch type.  You might or 
might not want to be in the same directory as the original files 
depending on the patch type.

I always like to include the '--dry-run' option to patch the first time 
through, in case I used the wrong -p option or there are other problems 
(like patches that aren't going to apply correctly).

Once I'm confident it will run smoothly, I just remove the --dry-run 
from the last command.
If you're on BSD, the equivalent is -C I believe, unless gpatch is 
installed.

Bill

[toaster] suspicous file

[Rene]

Hi Group,
I 'm blocking Mails contents crypted Archivfiles.
But now toll-collect the german "truck duty" sends the paymentinfos in 
such archives.
Is there a way to tag such mails like sa do ([SPAM] foo bar ) in the 
subject and let them through the recivers ?

kind regars
rene