After updating softlimit did you simple restart qmail or do a qmailclt stop, qmailctl start?

On 11/19/2016 3:21 PM, [email protected] wrote:

Yes, i remove : '/usr/bin/softlimit -m 64000000' line from both /var/qmail/supervise/submission/run and var/qmail/supervise/smtp/run.

And nothing change. When try send by 587 port outlook ask my password and see segfault error in message log file.

*From:*Eric Broch [mailto:[email protected]]
*Sent:* Saturday, November 19, 2016 10:52 PM
*To:* [email protected]
*Subject:* Re: [qmailtoaster] I can't send email by 587 port new fresh qmailtoaster install

did you remove the call to softlimit: '/usr/bin/softlimit -m 64000000'? Remove it if you haven't already.

On 11/19/2016 11:45 AM, [email protected] <mailto:[email protected]> wrote:

    I do another fresh install on other computer (intel). And is the
    same. Segfault error and can send only by 25 port. When try 587 I
    have error segfault in message log and outlook asking for
    password. Increase softlimit nothing change L

    *From:*Eric Broch [mailto:[email protected]]
    *Sent:* Saturday, November 19, 2016 4:39 AM
    *To:* [email protected]
    <mailto:[email protected]>
    *Subject:* Re: [qmailtoaster] I can't send email by 587 port new
    fresh qmailtoaster install

    Also, I think the program needs to be compiled in debug mode for
    valgrind

    On 11/18/2016 7:30 PM, Eric Broch wrote:

        Odd. I'm playing around now with one I just set up...works
        fine. Put valgrind in to check memory like so:

        # yum install valgrind

        # vi /var/qmail/supervise/submission/run

        exec /usr/bin/valgrind -v --tool=memcheck /usr/bin/softlimit
        -m 64000000 /usr/bin/tcpserver -v -R -H -l $HOSTNAME -x
        $TCP_CDB -c "$MAXSMTPD" -u "$QMAILDUID" -g "$NOFILESGID" 0 587
        $SMTPD $VCHKPW /bin/true 2>&1

        What kind of server/computer is it?

        On 11/18/2016 6:01 PM, [email protected] <mailto:[email protected]>
        wrote:

I try set 256 ,00,000 512,000,000 1024,000,000 2048,000,000 on bot /var/qmail/supervise/submission/run
            and var/qmail/supervise/smtp/run

            Still not work. Connected to the server and asking for
            password. Password is ok. When i change port in outlook to
            25 everything work fine

            L

            *From:*Eric Broch [mailto:[email protected]]
            *Sent:* Saturday, November 19, 2016 12:30 AM
            *To:* [email protected]
            <mailto:[email protected]>
            *Subject:* Re: [qmailtoaster] I can't send email by 587
            port new fresh qmailtoaster install

            Mine's set at 128,000,000. I'd bump it up.

            I have a client's set at 1,280,000,000 because of a
            certain email client.

            256,000,000

            512,000,000

            1024,000,000

            On 11/18/2016 4:22 PM, [email protected]
            <mailto:[email protected]> wrote:

                Thanks for fast reply,

                Its may first idea.  I have segfult.

                Nov 18 23:43:47 mail kernel: vchkpw[8451]: segfault at
                0 ip 00007f29e9e03346 sp 00007ffef20c4378 error 4 in
                libc-2.17.so[7f29e9d7e000+1b7000]

                But I change soft limit to 100 000 000, 128 000 000,
                30 000 000, 40 000 000 and still not work

                *From:*Eric Broch [mailto:[email protected]
                <mailto:[email protected]>]
                *Sent:* Saturday, November 19, 2016 12:17 AM
                *To:* [email protected]
                <mailto:[email protected]>
                *Subject:* Re: [qmailtoaster] I can't send email by
                587 port new fresh qmailtoaster install

                Check in /var/log/messages for a segfault error. Also
                bump up the softlimit in
                /var/qmail/supervise/submission/run

                On 11/18/2016 3:58 PM, [email protected]
                <mailto:[email protected]> wrote:

                    454 oops, problem with child and I can't auth (#4.3.0)


Reply via email to