[qmailtoaster] auth disabled patch (by request of Adam Cantwell)

Hi, Just an test release, would be nice if it goes to the development server.. I did not test it a whole lot, but it was not a complex patch.. Default authentication is enabled, to disable put export AUTH_DISABLED=1 in your run file to disable authentication. Download for now at http://iserve01

Re: [qmailtoaster] email multiplicated

In spamdyke, authentication does not bypass the timeout filter. In theory, even authenticated users can have bad network connections or badly written mail server software. Limiting the attachment size in qmail won't solve this particular problem, because the timeout occurs before the attachme

Re: [qmailtoaster] email multiplicated

It's hard to say what the "correct" value should be -- you may simply have to use trial-and-error until the remote server is able to deliver the message. Personally, if it were me, I would increase the timeout to 5 minutes (or maybe even disable it) until the messages were all delivered succss

Re: [qmailtoaster] email multiplicated

Sam, I keep wondering why they get the timeout, b/c they are authenticated users and should go over spamdyke checks. I put the -T from 60 to 100. Should i set it to zero? Is there a way to limit attachment size in Qmail? thanks! -Original Message- From: Sam Clippinger <[EMAIL PROTECTED]>

Re: [qmailtoaster] email multiplicated

Thanks for your answer. I changed the -T from 60 to 100. would it be enough? I used "qmFind -s [EMAIL PROTECTED] < /var/log/qmail/qmail-send/current" and found out that so far I got this email 104 times!! E-Mail no. 104 with Msg-No: 8175703 Del-Id: 136 QP-Id: 697 U-Id: 89 - From: <[EMAIL PROTECTE

Re: [qmailtoaster] email multiplicated

It looks like you're using spamdyke. Some remote servers have a tendency to pause in the middle of a delivery in order to prepare attachments. Large attachments take longer, so the connection can timeout. Try increasing spamdyke's idle timeout to a higher value. In the configuration file, l

Re: [qmailtoaster] changing root password on mysql - effect the toaster?

That's the same password as my luggage. On Nov 21, 2007 1:35 PM, Ronnie Tartar <[EMAIL PROTECTED]> wrote: > Great, Now everybody knows my password. > > > > - Original Message - > From: Warren Melnick > To: qmailtoaster-list@qmailtoaster.com > Sent: Wednesday, November 21, 2007 3:34 PM > Su

Re: [qmailtoaster] changing root password on mysql - effect the toaster?

Great, Now everybody knows my password. - Original Message - From: Warren Melnick To: qmailtoaster-list@qmailtoaster.com Sent: Wednesday, November 21, 2007 3:34 PM Subject: Re: [qmailtoaster] changing root password on mysql - effect the toaster? The toaster uses whatever password y

Re: [qmailtoaster] changing root password on mysql - effect the toaster?

The toaster uses whatever password you have in the /home/vpopmail/etc/vpopmail.mysql file. It is one line that usually looks like this: localhost|0|vpopmail|SsEeCcRrEeTt|vpopmail 5 fields separated by pipes. I believe the order is: server port (0 for unix pipes) user password database Regards

[qmailtoaster] email multiplicated

Hey there guys. I am having this problem now that I am getting two emails from this sender (also on my host) several (LOTS of!) times. One is a 1mb e-mail and another a 6mb e-mail that's a failure notice with the attached file converted to text (why?!). This user reports that every message he send

Re: [qmailtoaster] changing root password on mysql - effect the toaster?

To the best of my knowledge you can change the root password and it will have no effect on Qmail toaster. Qmail uses the EZMLM user i believe and one other. It uses the root password for initial setup only. After that you can change it. I have done so on my production box with no advers

[qmailtoaster] changing root password on mysql - effect the toaster?

Does the toaster have any dependencies on the mysql root password? Meaning after I set everything up, can i change it, or do I need to modify any conf files? I assume the toaster uses it's own mysql user though for regular operations... Regards, Dustin --

[qmailtoaster] multilog / qmail-smtpd become defunct, zombie processes

Hello all, Some basic diagnoses before we get started: CentOS 4.5 Linux 2.6.9-55.0.12.ELsmp on Dual Intel(R) Xeon(TM) CPU 3.20GHz running a single 144 GB SCSI disk. I installed the most recent Qmail Toaster RPMs, the only deviations behing that I re-compiled vpopmail with roaming users enabled.

[qmailtoaster] multilog / qmail-smtpd become defunct, zombie processes

Hello all, (I e-mailed this in yesterday, but, for some unknown reason, I never saw it appear - if this turns out to be a duplicate, I apologize in advance.) Some basic diagnoses before we get started: CentOS 4.5 Linux 2.6.9-55.0.12.ELsmp on Dual Intel(R) Xeon(TM) CPU 3.20GHz running a single 14

Re: [qmailtoaster] How to Block Insecure SMTP Auth

On 11/21/2007 09:31 AM, Davide Bozzelli wrote: Adam Cantwell ha scritto: Setting AUTH=0 on my qmailrocks machine causes smtpd to no longer advertise auth at all, and MUA's detect this and drop the connection with an error before any credentials are sent. This is the setup I am trying to re

Re: [qmailtoaster] How to Block Insecure SMTP Auth

On 11/21/2007 09:22 AM, Jean-Paul van de Plasse wrote: Hi Adam, You are right about the advertising... Did see that also.. but it does make login in go wrong so to say :) Anyways there is no option now to stop this advertising from happening, I did not think this would be needed when I patched

Re: [qmailtoaster] How to Block Insecure SMTP Auth

Adam Cantwell ha scritto: Setting AUTH=0 on my qmailrocks machine causes smtpd to no longer advertise auth at all, and MUA's detect this and drop the connection with an error before any credentials are sent. This is the setup I am trying to replicate with QMT: to get smtpd on port 25 to no

Re: [qmailtoaster] How to Block Insecure SMTP Auth

Hi Adam, You are right about the advertising... Did see that also.. but it does make login in go wrong so to say :) Anyways there is no option now to stop this advertising from happening, I did not think this would be needed when I patched the require auth code in.. Wrong thinking it seems now

Re: [qmailtoaster] How to Block Insecure SMTP Auth

On 11/21/2007 07:40 AM, Jean-Paul van de Plasse wrote: Hi Adam, This seems to work : Change the /bin/true to /bin/false in your /var/qmail/supervise/smtp/run JP What I am trying to do is block unencrypted authentication requests from users trying to send outbound mail. I want to force them

[qmailtoaster] Webmai v-Webmail --

Someone, you use v-webmail? Http://v-webmail.sourceforge.net/ Works well? Thanks - QmailToaster hosted by: VR Hosted - To unsubscribe, e

Re: [qmailtoaster] How to Block Insecure SMTP Auth

Hi Adam, This seems to work : Change the /bin/true to /bin/false in your /var/qmail/supervise/smtp/run JP - Original Message - From: "Adam Cantwell" <[EMAIL PROTECTED]> To: Sent: Wednesday, November 21, 2007 3:26 PM Subject: Re: [qmailtoaster] How to Block Insecure SMTP Auth On 1

Re: [qmailtoaster] How to Block Insecure SMTP Auth

On 11/21/2007 6:36 AM, Igor Smitran wrote: > Isn't port 25 needed for incoming mails? If you block port 25 how will > some other sender out of your domain be able to send you an email? > For example, if [EMAIL PROTECTED] wants to send you an email then he > will come to your port 25 and deliver the

Re: [qmailtoaster] How to Block Insecure SMTP Auth

On 11/21/2007 6:23 AM, Peter Peltonen wrote: > Is it so, that the default SMTP auth is not SLL enabled? > > If so, could you document for rest of us, how you got SSL enabled? > > Cheers, > Peter > The default SMTP run file provides TLS on port 25. I wanted TLS+SSL to run on port 465 to provide

Re: [qmailtoaster] How to Block Insecure SMTP Auth

Isn't port 25 needed for incoming mails? If you block port 25 how will some other sender out of your domain be able to send you an email? For example, if [EMAIL PROTECTED] wants to send you an email then he will come to your port 25 and deliver the email. He will not be able to do smtp auth beca

Re: [qmailtoaster] How to Block Insecure SMTP Auth

Is it so, that the default SMTP auth is not SLL enabled? If so, could you document for rest of us, how you got SSL enabled? Cheers, Peter On Nov 21, 2007 2:21 PM, Adam Cantwell <[EMAIL PROTECTED]> wrote: > I have gotten ucspi-ssl working on port 465 for SSL enabled SMTP > authentication, and aut

[qmailtoaster] How to Block Insecure SMTP Auth

I have gotten ucspi-ssl working on port 465 for SSL enabled SMTP authentication, and auth is required on that port. What I want to do now is block authentication completely on port 25, so that users are forced to use SSL to auth. I can't find the correct variables for the SMTP run file to do this