Re: [qmailtoaster] Re: Per Session Limit Question
Il 24/02/2012 21:03, Eric Shubert ha scritto: On 02/24/2012 12:24 PM, Joel Eddy wrote: That's kinda what I figured it did. Just wasn't 100% on that decision. Thanks for the info. I think what's happening is the client uses Peachtree accounting to send invoices. And from what I remember of Peachtree is it sends the invoice to the email client of choice and sends through it. Since the client uses Outlook 2007 I'm thinking it isn't sending the message right away. Instead I think it probably Cues the message in Outlook until you hit send and receive. If that's the case, and I believe that is the default for Outlook it could very well be holding a rather large number of messages to send. Hence, causing the per session limit pop up. I've got to go over to the clients place of business and check that to know for sure however. That's a good possibility. I can't honestly say if Outlook (any version) uses a separate session for each messages or not, but I would guess that it likely sends them all in a single smtp session. No reason not to that I can see. What I said earlier about this is probably wrong. I do know that Outlook doesn't leave an smtp session going continually though. That would eventually time out. However, if a slew of messages were waiting to go out, as in the case where Outlook was offline for a period of time, they could all be sent in a single smtp session. If/when this happens, I honestly don't know what chkuser would do. I expect that it would apply the limits to each messages individually, but I'm not certain of that. Tonino? It is per TCP session. It means when several messages are sent in different message sessions but within a unique SMTP connection, limit is global. I planned to make it become per message session, but honestly in years I've received no complains, so I'm uncertain if to make it. I suggest to keep this tarpitting action only on public MX, disabling it on server used for authenticated relaying. Let me repeat again: public and relay servers must be different (different IP or different ports), mainly because many email lients do not handle error messages, so I enable chkuser on public MX, and disable chkuser on authenticated relay servers, where users get back messages of not existing (local) users from qmail. Regards, Tonino Generally speaking, I'm not aware of any limits that are placed on multiple messages in a single smtp session. This doesn't mean that there aren't any though. Sorry for the disinformation earlier. Please keep us posted. -- Inter@zioniInterazioni di Antonio Nati http://www.interazioni.it to...@interazioni.it - Qmailtoaster is sponsored by Vickers Consulting Group (www.vickersconsulting.com) Vickers Consulting Group offers Qmailtoaster support and installations. If you need professional help with your setup, contact them today! - Please visit qmailtoaster.com for the latest news, updates, and packages. To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com
Re: [qmailtoaster] patch utility under Fedora 15
Am 25.02.2012 um 11:46 schrieb qmt: > > Hello all > I do as your method but When I built libdomainkeys-toaster-*.src.rpm ,i got > the error as below. > Can you help? > My system is frdora15_x64. > > daemontools-toaster-*.src.rpm build pass > => changes p0 -> p1 > > ucspi-tcp-toaster-*.src.rpmbuild pass > => changes p0 -> p1 > => one patch had to manually specify target > > vpopmail-toaster-*.src.rpm build pass > => Unsure, think there was one p0 -> p1, but made no notes > > libdomainkeys-toaster-*.src.rpm=> no changes error > libsrs2-toaster-*.src.rpm=> no changes build pass The rpm build command in Fedora forbids *futzz* (e.g. when a patch could be applied, but is e.g. one or two lines off). This means that the patch for that package needs to be re-created (using diff command) against this version. This will eliminate fuzz and everything will work ok. You can do this by installing the source-package, unpacking the source folder, making a copy of the source folder applying the patch manually to ONE of the folders and then using diff to re-create the patch. Martin signature.asc Description: Message signed with OpenPGP using GPGMail
[qmailtoaster] patch utility under Fedora 15
Hello all I do as your method but When I built libdomainkeys-toaster-*.src.rpm ,i got the error as below. Can you help? My system is frdora15_x64. daemontools-toaster-*.src.rpm build pass => changes p0 -> p1 ucspi-tcp-toaster-*.src.rpmbuild pass => changes p0 -> p1 => one patch had to manually specify target vpopmail-toaster-*.src.rpm build pass => Unsure, think there was one p0 -> p1, but made no notes libdomainkeys-toaster-*.src.rpm=> no changes error libsrs2-toaster-*.src.rpm=> no changes build pass [root@node01 src]# rpmbuild --rebuild --with fedora_1164 libdomainkeys-toaster-0.68-1.3.6.src.rpm Installing libdomainkeys-toaster-0.68-1.3.6.src.rpm Executing(%prep): /bin/sh -e /var/tmp/rpm-tmp.gu26N3 + umask 022 + cd /root/rpmbuild/BUILD + LANG=C + export LANG + unset DISPLAY + cd /root/rpmbuild/BUILD + rm -rf libdomainkeys-0.68 + /bin/tar -xf - + /usr/bin/gzip -dc /root/rpmbuild/SOURCES/libdomainkeys-0.68.tar.gz + STATUS=0 + '[' 0 -ne 0 ']' + cd libdomainkeys-0.68 + /bin/chmod -Rf a+rX,u+w,g-w,o-w . + '[' -f /var/tmp/libdomainkeys-0.68-gcc ']' + rm -f /var/tmp/libdomainkeys-0.68-gcc + echo gcc + '[' -f /var/tmp/libdomainkeys-0.68-show_flags ']' + cat + chmod u+x /var/tmp/libdomainkeys-0.68-show_flags + /var/tmp/libdomainkeys-0.68-show_flags RPM RELEASE: libdomainkeys-toaster-0.68-1.3.6 OS TYPE IS : Fedora 11 x86_64 Linux BUILD DATE : Fri Jun 12 2009 CCFLAGS: -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector --param=ssp-buffer-size=4 -m64 -mtune=generic LDFLAGS: -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector --param=ssp-buffer-size=4 -m64 -mtune=generic + '[' -f /var/tmp/libdomainkeys-0.68-show_flags ']' + rm -f /var/tmp/libdomainkeys-0.68-show_flags + perl -pi '-es/CFLAGS=/CFLAGS=-O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector --param=ssp-buffer-size=4 -m64 -mtune=generic -fPIC /' Makefile + echo -- -lresolv + exit 0 Executing(%build): /bin/sh -e /var/tmp/rpm-tmp.pNe0ol + umask 022 + cd /root/rpmbuild/BUILD + cd libdomainkeys-0.68 + LANG=C + export LANG + unset DISPLAY + '[' -n /root/rpmbuild/BUILDROOT/libdomainkeys-toaster-0.68-1.3.6.x86_64 -a /root/rpmbuild/BUILDROOT/libdomainkeys-toaster-0.68-1.3.6.x86_64 '!=' / ']' + rm -rf /root/rpmbuild/BUILDROOT/libdomainkeys-toaster-0.68-1.3.6.x86_64 + mkdir -p /root/rpmbuild/BUILDROOT/libdomainkeys-toaster-0.68-1.3.6.x86_64 + make UNAME=Linux gcc -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector --param=ssp-buffer-size=4 -m64 -mtune=generic -fPIC -DBIND_8_COMPAT -O2 -o makeheader makeheader.c ./makeheader domainkeys.h gcc -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector --param=ssp-buffer-size=4 -m64 -mtune=generic -fPIC -DBIND_8_COMPAT -O2 -c dktest.c -I. dktest.c: In function 'main': dktest.c:146:3: warning: pointer targets in passing argument 2 of 'dk_message' differ in signedness [-Wpointer-sign] ./domainkeys.h:248:9: note: expected 'const unsigned char *' but argument is of type 'char *' dktest.c:148:3: warning: pointer targets in passing argument 2 of 'dk_message' differ in signedness [-Wpointer-sign] ./domainkeys.h:248:9: note: expected 'const unsigned char *' but argument is of type 'char *' dktest.c:181:9: warning: pointer targets in passing argument 2 of 'dk_message' differ in signedness [-Wpointer-sign] ./domainkeys.h:248:9: note: expected 'const unsigned char *' but argument is of type 'char *' dktest.c:193:10: warning: pointer targets in passing argument 2 of 'dk_message' differ in signedness [-Wpointer-sign] ./domainkeys.h:248:9: note: expected 'const unsigned char *' but argument is of type 'char *' dktest.c:199:10: warning: pointer targets in passing argument 2 of 'dk_message' differ in signedness [-Wpointer-sign] ./domainkeys.h:248:9: note: expected 'const unsigned char *' but argument is of type 'char *' dktest.c:210:7: warning: pointer targets in passing argument 2 of 'dk_message' differ in signedness [-Wpointer-sign] ./domainkeys.h:248:9: note: expected 'const unsigned char *' but argument is of type 'char *' dktest.c:286:5: warning: pointer targets in passing argument 3 of 'dk_getsig' differ in signedness [-Wpointer-sign] ./domainkeys.h:343:9: note: expected 'unsigned char *' but argument is of type 'char *' dktest.c:288:5: warning: format '%d' expects argument of type 'int', but argument 2 has type 'size_t' [-Wformat] dktest.c:288:5: warning: format '%d' expects argument of type 'int', but argument 3 has type 'size_t' [-Wformat] dktest.c:291:5: warning: pointer targets in passing argument 3 of 'dk_getsig' differ in signedness [-Wpointer-sign] ./domainkeys.h:343:9: note: expected 'unsigned char *' but argument is of type 'char *' gcc -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector --param=ssp-buffer-size=4 -m64 -mtune=generic -fPIC -DBIND_8_COMPAT -O2 -c domainkeys.c -I. domainkeys.c:
