tag:old.nabble.com,2006:forum-845Nabble - cr.yp.to2009-11-26T19:46:59ZD. J. Bernstein on math, computer science, internet, cryptography. cr.yp.to home is <a href="http://cr.yp.to/" target="_top" rel="nofollow">here</a>.tag:old.nabble.com,2006:post-26537654Re: tcpserver, qmail-smtpd, qmail-queue and filter Qs2009-11-26T19:46:59Z2009-11-26T19:46:59ZPhilip Rhoades-2Jost,
<br><br><br>On 2009-11-27 08:01, Jost Krieger wrote:
<div class='shrinkable-quote'><br>> On Thu, Nov 19, 2009 at 10:16:37AM -0600, Kyle Wheeler wrote:
<br>>
<br>> Sorry to comeso late, but this all is a misunderstanding.
<br>>
<br>>> On Thursday, November 19 at 11:48 AM, quoth Philip Rhoades:
<br>>>> In my setup tcpserver execs greylite which eventually execs
<br>>>> qmail-smtpd. Greylite uses the to and from IP addresses of the tcp
<br>>>> communication - is any of the message itself (header lines?, body?)
<br>>>> available at this point or only after qmail-smtpd runs?
<br>>>
<br>>> As other folks have pointed out, the short answer is "no".
<br>>> ...
<br>>> Before qmail-smtpd runs, you know only the information about the
<br>>> connection itself: the IP address (and hostname) of the connecting
<br>>> client, the port numbers that are being used.
<br>>
<br>> That's not true (in the case of greylite).
<br>>
<br>> I used greylite for a while (and gave up for reasons of database
<br>> contention). Now I use a variant of greydaemon (thanks to John Levine),
<br>> but that needs patching qmail-smtpd (which we have been doing for ten
<br>> years anyway ...).
<br>>
<br>> Greylite is using "command line chainig", but not simple "exec
<br>> chaining". It does indeed set up a pair of pipes, then forks and execs.
<br>> After that, it listens into the SMTP stream. It will intercept the SMTP
<br>> dialogue for greylisting, and turn into a passthrough if everything is
<br>> fine. It never cares for anything after DATA, but it sees the MAIL FROM
<br>> and RCPT TO.
</div><br><br>Right - which would allow me to do some more filtering except that as
<br>someone else pointed out - MAIL FROM and RCPT TO don't necessarily
<br>correspond to From: and To: - I have checked most of my problem mails
<br>and they would not be stopped by such filtering unfortunately . .
<br><br><br>> Qmail-smtpd doen't notice, because it sees the complete SMTP dialogue,
<br>> normally.
<br>>
<br>> So greylite is like recordio in interface and function.
<br><br><br>Thanks for the extra info! - it is appreciated.
<br><br>Regards,
<br><br>Phil.
<br>--
<br>Philip Rhoades
<br><br>GPO Box 3411
<br>Sydney NSW 2001
<br>Australia
<br>E-mail: <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26537654&i=0" target="_top" rel="nofollow">phil@...</a>
<br><p>From forum: <a href="http://old.nabble.com/cr.yp.to---qmail-f870.html" embed="fixTarget[870]" target="_top" >cr.yp.to - qmail</a></p>tag:old.nabble.com,2006:post-26534894Re: tcpserver, qmail-smtpd, qmail-queue and filter Qs2009-11-26T13:01:10Z2009-11-26T13:01:10ZJost Krieger-6On Thu, Nov 19, 2009 at 10:16:37AM -0600, Kyle Wheeler wrote:
<br><br>Sorry to comeso late, but this all is a misunderstanding.
<br><div class='shrinkable-quote'><br>> On Thursday, November 19 at 11:48 AM, quoth Philip Rhoades:
<br>> > In my setup tcpserver execs greylite which eventually execs
<br>> > qmail-smtpd. Greylite uses the to and from IP addresses of the tcp
<br>> > communication - is any of the message itself (header lines?, body?)
<br>> > available at this point or only after qmail-smtpd runs?
<br>>
<br>> As other folks have pointed out, the short answer is "no".
<br>> ...
<br>> Before qmail-smtpd runs, you know only the information about the
<br>> connection itself: the IP address (and hostname) of the connecting
<br>> client, the port numbers that are being used.
</div><br>That's not true (in the case of greylite).
<br><br>I used greylite for a while (and gave up for reasons of database
<br>contention). Now I use a variant of greydaemon (thanks to John Levine),
<br>but that needs patching qmail-smtpd (which we have been doing for ten
<br>years anyway ...).
<br><br>Greylite is using "command line chainig", but not simple "exec
<br>chaining". It does indeed set up a pair of pipes, then forks and execs.
<br>After that, it listens into the SMTP stream. It will intercept the SMTP
<br>dialogue for greylisting, and turn into a passthrough if everything is
<br>fine. It never cares for anything after DATA, but it sees the MAIL FROM
<br>and RCPT TO.
<br><br>Qmail-smtpd doen't notice, because it sees the complete SMTP dialogue,
<br>normally.
<br><br>So greylite is like recordio in interface and function.
<br><br>Jost
<br>--
<br>| Helft Spam ausrotten! HTML in Mail ist unhöflich. |
<br>| Postmaster, JAPH, manchmal Wahrsager am RZ der RUB |
<br>| Bitte immer an Funktionsadressen schreiben: <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26534894&i=0" target="_top" rel="nofollow">Postmaster@...</a> |
<br><p>From forum: <a href="http://old.nabble.com/cr.yp.to---qmail-f870.html" embed="fixTarget[870]" target="_top" >cr.yp.to - qmail</a></p>tag:old.nabble.com,2006:post-26531235Re: limit outgoing email size but not incoming2009-11-26T07:39:22Z2009-11-26T07:39:22ZKyle Wheeler-2-----BEGIN PGP SIGNED MESSAGE-----
<br>Hash: SHA256
<br><br>On Thursday, November 26 at 09:37 AM, quoth Markus Stumpf:
<br>> Next you have to define what you mean by incoming and outgoing.
<br><br>This is key (especially since, without something like SMTP-AUTH, it
<br>could be pretty easy for a spammer to work around).
<br><br>Another way to do it is to place the restriction in a wrapper around
<br>qmail-remote, forcing a failure to deliver if the remote message is
<br>too big. This clearly delineates between "incoming" and "outgoing"
<br>(because incoming messages never go through qmail-remote), but means
<br>that the too-large messages get into the queue even though they'll
<br>never be delivered.
<br><br>~Kyle
<br>- --
<br>Nothing gives one person so great advantage over another as to remain
<br>always cool and unruffled under all circumstances.
<br> -- Thomas Jefferson to Francis Eppes, 1816
<br>-----BEGIN PGP SIGNATURE-----
<br>Comment: Thank you for using encryption!
<br><br>iQIcBAEBCAAGBQJLDqEpAAoJECuveozR/AWetY8QAJvOeMqJRp+Azfn58O9e5nEd
<br>ChpD7fR+ZQlHg/Ox+iRjZH2n5Hrb8ZSXY60AivD88TN6JukPVQHTmQjw3Oh3ydzV
<br>BqDciQBt3vCvVLpTOfUT23biwdh2/jNgENK/xjG1VIDofjJHOXXQ19XcOt2u5ReS
<br>Khb9slaIbo2MS0e69FUJxeuI+GpRNd4t0xfWpQ9LdsLno396Yer9MwqREvyZkqmD
<br>BOTElj1+LuWMtO1gD4nqQ/ysOf/NFnapC3NAEvGDKWc5tbvbWVoLE3tAPWnKD9zK
<br>xSlJL1rK9TNBvscwTAUG0+4opHa2dx4Ne0gFI9SFttBZRr9s+leqb21ukE6EFkEm
<br>YY1CVNAurEFq3Gtmf0RtK/sGcTIccR1El1z32v9cFTDWnfjHCyvg4YPOQwIUAzFL
<br>Xc2hoBu18h7QkrG8N0vnF5LwaUtaiyDGc0T2EZ/MCmKobIlXVfzDBSQukc4Oq50B
<br>M+Z2VVsIoGizCqQ43zAUYRdaFLWaS49gepr42MP+Ua+b4Jl2drKIIBR7XLRy4s0u
<br>UTVspP3+Abo06zLmaWstQKqpxr1Pyl7DwSbRFYNzSovbPThIUSRioSWK4165me86
<br>jIA4u2EFk78l2avgiErSVwniUyygt46pW0jV8WNThGynJAFMA+Veym/4h0Y6dSSB
<br>723MCyQJX2AgkZtdEMts
<br>=6kre
<br>-----END PGP SIGNATURE-----
<br><p>From forum: <a href="http://old.nabble.com/cr.yp.to---qmail-f870.html" embed="fixTarget[870]" target="_top" >cr.yp.to - qmail</a></p>tag:old.nabble.com,2006:post-26531250Re: limit outgoing email size but not incoming2009-11-26T07:36:05Z2009-11-26T07:36:05ZKyle Wheeler-2-----BEGIN PGP SIGNED MESSAGE-----
<br>Hash: SHA256
<br><br>On Thursday, November 26 at 08:35 AM, quoth Philipp Kolloczek:
<br>> Well, you can do like Hugo Monteiro suggested. Without patching
<br>> qmail sources there will be no other way.
<br><br>Well, now, that's just an open challenge.
<br><br>You can also do it with a qmail-queue wrapper (a convenient one is
<br>qmail-qfilter). If you rename qmail-queue and qmail-qfilter
<br>appropriately, you can make it apply to locally (e.g.
<br>/usr/sbin/sendmail) produced email as well.
<br><br>~Kyle
<br>- --
<br>It only takes 20 years for a liberal to become a conservative without
<br>changing a single idea.
<br> -- Robert Anton Wilson
<br>-----BEGIN PGP SIGNATURE-----
<br>Comment: Thank you for using encryption!
<br><br>iQIbBAEBCAAGBQJLDqBPAAoJECuveozR/AWeD94P9ic2QkO3/wmWI6lGIifEOyl7
<br>OkqDBLj8SXA3qm5KbNCG0lDaw8b5H/xDSjbz3CSh5xyzfh1lGStFRDrfTj5p2xmS
<br>MEXJWEH6HH0wIzjCuev6Zxm8kMOSaCQcxHHN7xTUHQzoay+VZ48E35Z0bB/sXbCe
<br>JNYg8UG9hMvUtk9DqmhDWFFKh0liO/elOHXnnGpFW6eAC8TpuIVRY8uDEym4yLQi
<br>+IP9de9yOshotvolA3aGphrR/KNk1+w3YMDz/uMXql29gve1OdummUf7heYeTiAJ
<br>xi9Ja//9AtYZkCtcMJprGBgPhXsW7AfaCrzm5PQyhQ0PER/ysD6tOGDM4sZEVouT
<br>i6CrNI5Xc6rw78rH4sbcdOzIrLV3f9tWVhTz9HkRCMSGsZYUfIAFRJPG5YS34BbL
<br>uYihGv18A5ez0SnwEcsfRx3AADgsUGODd/JZiRG94w1CJtr5NDJhpL/13Oa3Cmpz
<br>iU/ZzIZmzQjS4USKleACpS0XUl7Z+6/7bGLmIV26W/CByeIENq2ByNFLZWcniLO+
<br>9aXvVC7B4Mm16+YjjdffY/DHPEB8E+UUbFiXvN+l9IXlmlSh3R9pKiIxNsRjVzzz
<br>RYz/AZLMOL7cxNENIG0nhoLn23RyQ3D+oxOyOvly29NZX91wMqcXKxK1PelkWpQW
<br>HdEsxwGFLMterv3RORk=
<br>=f5lG
<br>-----END PGP SIGNATURE-----
<br><p>From forum: <a href="http://old.nabble.com/cr.yp.to---qmail-f870.html" embed="fixTarget[870]" target="_top" >cr.yp.to - qmail</a></p>tag:old.nabble.com,2006:post-26526060Re: limit outgoing email size but not incoming2009-11-26T00:37:40Z2009-11-26T00:37:40ZMarkus Stumpf-4On Thu, Nov 26, 2009 at 10:29:17AM +0800, packets wrote:
<br>> As I know, both incoming and outgoing will reject emails more than
<br>> 3mb and I don't want to do that.
<br><br>This is not correct.
<br>DATABYTES only affects incoming messages per qmail-smtpd.
<br>Messages created locally or uploaded and sent eg. via a webmail system
<br>are *NOT* affected.
<br><br>Next you have to define what you mean by incoming and outgoing.
<br>Do you mean by "incoming" *every* message from *every* user that
<br>would be delivered to a local address/mailbox?
<br>And outgoing would be every message for a non-local user/mailbox?
<br>How about messages coming in for a local user that has a forward to an
<br>external address?
<br>Next is error handling.
<br>At what point do you want to reject the message? Somehow the message has
<br>to be uploaded to your server. Do you want to reject it at that point?
<br>If not, how will you handle the already injected message? Bounce it back
<br>to the sender?
<br><br>I guess to accomplish what you want I'd modify qmail-smtpd.c in
<br>smtp_rcpt().
<br><br>Change
<br>------------------------------------------------------------------------
<br> if (!stralloc_0(&rcptto)) die_nomem();
<br> out("250 ok\r\n");
<br>}
<br>------------------------------------------------------------------------
<br>to
<br>------------------------------------------------------------------------
<br> if (!stralloc_0(&rcptto)) die_nomem();
<br> if (addrallowed()) databytes = 0;
<br> out("250 ok\r\n");
<br>}
<br>------------------------------------------------------------------------
<br><br>What does it do?
<br>For every connection that delivers a message to a local recipient
<br>(addrallowed() results in true) databytes is set to unlimited (aka
<br>turned off).
<br>If you now set DATABYTES to 3MB then every connection that requires a relay
<br>operation will be restricted to 3 MB, every connection with a local
<br>delivery will not.
<br><br>CAVEAT!!! SMTP allows more than one recipient with one message.
<br>the modification turns off DATABYTES if *ANY ONE* of multiple
<br>recipients of the message is local. So if there is a message
<br>of size 5 MB with 1 local and 1 remote recipient it will be accepted and
<br>delivered remote, even with the 5 MB size.
<br><br>Hope that helps,
<br><br> \Maex
<br><br><p>From forum: <a href="http://old.nabble.com/cr.yp.to---qmail-f870.html" embed="fixTarget[870]" target="_top" >cr.yp.to - qmail</a></p>tag:old.nabble.com,2006:post-26525588RE: limit outgoing email size but not incoming2009-11-25T23:35:21Z2009-11-25T23:35:21ZPhilipp KolloczekHello.
<br><br>> 3mb. As I know, both incoming and outgoing will reject emails more
<br>> than 3mb and I don't want to do that. I want to
<br>> accept incoming emails regardless of any size but I want to limit my
<br>> outgoing smtp to 3mb.
<br><br>Well, you can do like Hugo Monteiro suggested.
<br>Without patching qmail sources there will be no other way.
<br><br>If your sender do smtp-auth, it may be a way to alter qmails code
<br>to redefine databytes with a given value if the auth request was
<br>successful. Depending of your qmail you have to change more than
<br>one function in different modules.
<br><br>Greets
<br>Phil.
<br><br><br><p>From forum: <a href="http://old.nabble.com/cr.yp.to---qmail-f870.html" embed="fixTarget[870]" target="_top" >cr.yp.to - qmail</a></p>tag:old.nabble.com,2006:post-26523837Re: limit outgoing email size but not incoming2009-11-25T19:10:36Z2009-11-25T19:10:36ZHugo Monteiro-2packets wrote:
<div class='shrinkable-quote'><br>> Is it possible that I impose restriction on senders not to send emails
<br>> more than 5mb email? I have read databytes and I
<br>> imposed it to one of my server with 15mb. However, I want to implement
<br>> it to another server but this time it must be
<br>> 3mb. As I know, both incoming and outgoing will reject emails more
<br>> than 3mb and I don't want to do that. I want to
<br>> accept incoming emails regardless of any size but I want to limit my
<br>> outgoing smtp to 3mb.
<br>>
<br>>
</div><br><br>You can specify a different DATABYTES env var for each tcpserver rule
<br>that you have. The existence of that env variable will overwrite the
<br>default value set in the databytes file, if any.
<br><br>Regards,
<br><br>Hugo Monteiro.
<br><br>--
<br>ci.fct.unl.pt:~# cat .signature
<br><br>Hugo Monteiro
<br>Email : <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26523837&i=0" target="_top" rel="nofollow">hugo.monteiro@...</a>
<br>Telefone : +351 212948300 Ext.15307
<br>Web : <a href="http://hmonteiro.net" target="_top" rel="nofollow">http://hmonteiro.net</a><br><br>Centro de Informática
<br>Faculdade de Ciências e Tecnologia da
<br> Universidade Nova de Lisboa
<br>Quinta da Torre 2829-516 Caparica Portugal
<br>Telefone: +351 212948596 Fax: +351 212948548
<br>www.ci.fct.unl.pt <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26523837&i=1" target="_top" rel="nofollow">apoio@...</a>
<br><br>ci.fct.unl.pt:~# _
<br><br><p>From forum: <a href="http://old.nabble.com/cr.yp.to---qmail-f870.html" embed="fixTarget[870]" target="_top" >cr.yp.to - qmail</a></p>tag:old.nabble.com,2006:post-26523563limit outgoing email size but not incoming2009-11-25T18:29:17Z2009-11-25T18:29:17Zpackets-2Is it possible that I impose restriction on senders not to send emails more than 5mb email? I have read databytes and I
<br>imposed it to one of my server with 15mb. However, I want to implement it to another server but this time it must be
<br> 3mb. As I know, both incoming and outgoing will reject emails more than 3mb and I don't want to do that. I want to
<br>accept incoming emails regardless of any size but I want to limit my outgoing smtp to 3mb.
<br><br><p>From forum: <a href="http://old.nabble.com/cr.yp.to---qmail-f870.html" embed="fixTarget[870]" target="_top" >cr.yp.to - qmail</a></p>tag:old.nabble.com,2006:post-26512858Re: Removing primes2009-11-25T05:37:08Z2009-11-25T05:37:08ZKarim Belabas-4* Jeroen Demeyer [2009-11-24 12:03]:
<br>> I am in particular looking for a way to remove ALL primes from the
<br>> addprimes list, i.e. removeprimes(addprimes()).
<br><br>This will work, and this particular example is actually suggested in the
<br>extended help :-) [ although in a slightly incorrect way, just fixed that ].
<br><br>Cheers,
<br><br> K.B.
<br>--
<br>Karim Belabas, IMB (UMR 5251) Tel: (+33) (0)5 40 00 26 17
<br>Universite Bordeaux 1 Fax: (+33) (0)5 40 00 69 50
<br>351, cours de la Liberation <a href="http://www.math.u-bordeaux1.fr/~belabas/" target="_top" rel="nofollow">http://www.math.u-bordeaux1.fr/~belabas/</a><br>F-33405 Talence (France) <a href="http://pari.math.u-bordeaux1.fr/" target="_top" rel="nofollow">http://pari.math.u-bordeaux1.fr/</a> [PARI/GP]
<br>`
<br><p>From forum: <a href="http://old.nabble.com/cr.yp.to---pari-users-f864.html" embed="fixTarget[864]" target="_top" >cr.yp.to - pari-users</a></p>tag:old.nabble.com,2006:post-26512794Re: Removing primes2009-11-25T05:34:09Z2009-11-25T05:34:09ZKarim Belabas-4* Bill Allombert [2009-11-24 23:46]:
<br>> On Tue, Nov 24, 2009 at 12:01:43PM +0100, Jeroen Demeyer wrote:
<br>> > Hello pari-users,
<br>> >
<br>> > In ?removeprimes it is written that the given vector should have at most
<br>> > 100 components. What is the reason for this? In any case, it seems to
<br>> > work even with more than 100 primes.
<br>>
<br>> I supose this is a left over of a previous implementation of addprimes.
<br>> There is no such limitations currently.
<br><br>Correct, I just fixed the Help string in svn. The authoritative help is
<br>the extended one, i.e. the output of ??, which is also found in the
<br>printed manual. The short help '?' *may* lag behind and correspond to
<br>older, possibly obsolete, versions.
<br><br>Bill created the function database in 2003; since then, the short and
<br>extended help are in the same place in the sources, and updated together.
<br>At the time the database was created, we fixed or updated a large number
<br>of the Help texts, but never could spare the time to actually go through
<br>every single function one by one and check the short help message.
<br><br>Please go on reporting any weird discrepancies like this one !
<br><br>Cheers,
<br><br> K.B.
<br>--
<br>Karim Belabas, IMB (UMR 5251) Tel: (+33) (0)5 40 00 26 17
<br>Universite Bordeaux 1 Fax: (+33) (0)5 40 00 69 50
<br>351, cours de la Liberation <a href="http://www.math.u-bordeaux1.fr/~belabas/" target="_top" rel="nofollow">http://www.math.u-bordeaux1.fr/~belabas/</a><br>F-33405 Talence (France) <a href="http://pari.math.u-bordeaux1.fr/" target="_top" rel="nofollow">http://pari.math.u-bordeaux1.fr/</a> [PARI/GP]
<br>`
<br><p>From forum: <a href="http://old.nabble.com/cr.yp.to---pari-users-f864.html" embed="fixTarget[864]" target="_top" >cr.yp.to - pari-users</a></p>tag:old.nabble.com,2006:post-26504622Re: Removing primes2009-11-24T14:39:37Z2009-11-24T14:39:37ZBill Allombert-3On Tue, Nov 24, 2009 at 12:01:43PM +0100, Jeroen Demeyer wrote:
<br>> Hello pari-users,
<br>>
<br>> In ?removeprimes it is written that the given vector should have at most
<br>> 100 components. What is the reason for this? In any case, it seems to
<br>> work even with more than 100 primes.
<br><br>I supose this is a left over of a previous implementation of addprimes.
<br>There is no such limitations currently.
<br><br>Cheers,
<br>Bill.
<br><p>From forum: <a href="http://old.nabble.com/cr.yp.to---pari-users-f864.html" embed="fixTarget[864]" target="_top" >cr.yp.to - pari-users</a></p>tag:old.nabble.com,2006:post-26493995Removing primes2009-11-24T03:01:43Z2009-11-24T03:01:43ZJeroen Demeyer-2Hello pari-users,
<br><br>In ?removeprimes it is written that the given vector should have at most
<br>100 components. What is the reason for this? In any case, it seems to
<br>work even with more than 100 primes.
<br><br>I am in particular looking for a way to remove ALL primes from the
<br>addprimes list, i.e. removeprimes(addprimes()).
<br><br><br>Cheers,
<br>Jeroen.
<br><p>From forum: <a href="http://old.nabble.com/cr.yp.to---pari-users-f864.html" embed="fixTarget[864]" target="_top" >cr.yp.to - pari-users</a></p>tag:old.nabble.com,2006:post-26492127Re: change filename2009-11-24T00:24:31Z2009-11-24T00:24:31ZMarkus Stumpf-4On Tue, Nov 24, 2009 at 03:50:59PM +0800, packets wrote:
<br>> I implement safecat so that I can create another copy of emails outside
<br>> Maildir directory. I want to create a script wherein it will tar all files
<br>> if the file was receive lets say November. All emails received last October
<br>> will not be included on tar.
<br><br>You may want to look at the GNU tar -N/--newer/--after-date options.
<br>They allow to specify "DATE" as (from "info tar"):
<br>* Calendar date items:: 19 Dec 1994.
<br>* Time of day items:: 9:20pm.
<br>* Time zone items:: EST, PDT, GMT.
<br>* Day of week items:: Monday and others.
<br>* Relative items in date strings:: next tuesday, 2 years ago.
<br>* Pure numbers in date strings:: 19931219, 1440.
<br>* Seconds since the Epoch:: @1078100502.
<br><br> \Maex
<br><p>From forum: <a href="http://old.nabble.com/cr.yp.to---qmail-f870.html" embed="fixTarget[870]" target="_top" >cr.yp.to - qmail</a></p>tag:old.nabble.com,2006:post-26491847Re: change filename2009-11-23T23:50:59Z2009-11-23T23:50:59Zpackets-2I implement safecat so that I can create another copy of emails outside Maildir directory. I want to create a script
<br>wherein it will tar all files if the file was receive lets say November. All emails received last October will not be
<br>included on tar. Since this is an old server and there are files wayback last year, its hard to use mtime options of
<br>find command though still possible by calculating days. If I can append month and date on the filename, it could make my
<br>life easier.
<br><br>>
<br>> But the main question to me is:
<br>> What problem are you trying to solve?
<br>>
<br><br><p>From forum: <a href="http://old.nabble.com/cr.yp.to---qmail-f870.html" embed="fixTarget[870]" target="_top" >cr.yp.to - qmail</a></p>tag:old.nabble.com,2006:post-26491298Re: change filename2009-11-23T23:01:32Z2009-11-23T23:01:32ZMarkus Stumpf-4Hi,
<br><br>the original spec is here:
<br> <a href="http://cr.yp.to/proto/maildir.html" target="_top" rel="nofollow">http://cr.yp.to/proto/maildir.html</a><br>Maildir++ spec is here:
<br> <a href="http://www.inter7.com/courierimap/README.maildirquota.html" target="_top" rel="nofollow">http://www.inter7.com/courierimap/README.maildirquota.html</a><br><br>Those define naming rules, which programs should adopt, to guarantee some
<br>interoperability.
<br><br>On Tue, Nov 24, 2009 at 11:18:26AM +0800, packets wrote:
<br>> Is it possible to change filename of all incoming emails before it will be
<br>> deliver to Maildir?
<br><br>Is the question:
<br> - is it possible like in "how can I do it"?
<br> Then you might want to take a look at
<br> <a href="http://www.jeenyus.net/linux/software/safecat.html" target="_top" rel="nofollow">http://www.jeenyus.net/linux/software/safecat.html</a><br> and modify the source code to produce the new names
<br> Or modify qmail-local.c around line 700 in procedure maildir_child().
<br>or is the question
<br> - is it possible like in "will I break things"?
<br> The you must check with your software accessing the maildirs.
<br><br>But the main question to me is:
<br> What problem are you trying to solve?
<br><br>The information you try to add to the name is already stored in the
<br>inode. You can access it with eg. "/bin/ls -l"
<br>If you want a more easy to process list use (GNU) find like:
<br> find /path -type f -printf "%CY%Cm %p\n"
<br><br> \Maex
<br><p>From forum: <a href="http://old.nabble.com/cr.yp.to---qmail-f870.html" embed="fixTarget[870]" target="_top" >cr.yp.to - qmail</a></p>tag:old.nabble.com,2006:post-26489924change filename2009-11-23T19:18:26Z2009-11-23T19:18:26Zpackets-2Is it possible to change filename of all incoming emails before it will be deliver to Maildir? Let's say I have a
<br>filename 1258692713.M653901P24650.localhost. Can I change it to 1258692713.M653901P24650-200911.localhost. Can I apply
<br>the output of the command "date +%F" in each incoming emails to append on the filename before it reach Maildir?
<br><p>From forum: <a href="http://old.nabble.com/cr.yp.to---qmail-f870.html" embed="fixTarget[870]" target="_top" >cr.yp.to - qmail</a></p>tag:old.nabble.com,2006:post-26462439PROMOÇÃO HYSTER2009-11-21T18:34:52Z2009-11-21T18:34:52ZHAILSON<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML xmlns:st1="urn:schemas-microsoft-com:office:smarttags" xmlns:o="urn:schemas-microsoft-com:office:office"><HEAD><TITLE></TITLE>
<META http-equiv=Content-Type content="text/html; charset=windows-1252">
<META content="MSHTML 6.00.2800.1106" name=GENERATOR></HEAD>
<BODY>
<P><STRONG><FONT size=5>
</FONT></STRONG></P>
<P><FONT size=7><STRONG> </STRONG><EM><SPAN style="FONT-SIZE: 18pt; COLOR: red"><STRONG>
</STRONG></SPAN></EM></P>
<P><EM><SPAN style="FONT-SIZE: 18pt; COLOR: #0080ff"><STRONG>SOMOS FABRICANTES
DE ROLETES E ROLDANAS PARA TORRES E QUADROS DE ELEVAÇÃO PARA EMPILHADEIRAS DAS
LINHAS:</STRONG></SPAN></EM></P>
<P><STRONG><EM><SPAN lang=EN-US style="FONT-SIZE: 18pt; BACKGROUND: white; COLOR: #004000; mso-ansi-language: EN-US">CLARK,
HYSTER, YALE, <st1:City w:st="on">MILAN</st1:City>, MADAL,<st1:place w:st="on"><st1:City w:st="on">TOYOTA</st1:City></st1:place>,</SPAN></EM><SPAN lang=EN-US style="mso-ansi-language: EN-US"><o:p></o:p></SPAN></STRONG></P>
<P><STRONG><EM><SPAN lang=EN-US style="FONT-SIZE: 18pt; BACKGROUND: white; COLOR: #004000; mso-ansi-language: EN-US"> </SPAN></EM><EM><SPAN style="FONT-SIZE: 18pt; BACKGROUND: white; COLOR: #004000">DAE-WOO, LINDE,
MITSUBISHI. E ETC.</SPAN></EM></STRONG></P>
<P><EM><SPAN style="FONT-SIZE: 13.5pt; COLOR: navy"><STRONG>NOSSOS PRODUTOS,
RESPEITAM TODOS OS PADRÕES ORIGINAIS DO FABRICANTE,</STRONG></SPAN></EM></P>
<P><EM><SPAN style="FONT-SIZE: 13.5pt; COLOR: navy"><STRONG>E VOCÊ PODERÁ
CONSULTA-LO <st1:PersonName w:st="on" ProductID="EM NOSSA EMPRESA COM">EM NOSSA
EMPRESA COM</st1:PersonName> O CÓDIGO ORIGINAL DO
FABRICANTE.</STRONG></SPAN></EM></P>
<P><STRONG><EM><SPAN style="FONT-SIZE: 24pt; COLOR: navy">GARANTIA SAVIPEÇAS,
</SPAN></EM><EM><SPAN style="FONT-SIZE: 13.5pt; COLOR: navy">PARA TODA A LINHA
DE NOSSOS PRODUTOS.</SPAN></EM></STRONG></P>
<P><EM><SPAN style="FONT-SIZE: 13.5pt; COLOR: navy"><STRONG>GARANTIA TOTAL DE 03
MESES .</STRONG></SPAN></EM></P>
<P><EM><SPAN style="FONT-SIZE: 13.5pt; COLOR: olive"><STRONG>PREÇOS E PRAZOS
ESPECIAIS PARA REVENDAS DE PEÇAS E LOCADORES.</STRONG></SPAN></EM></P>
<P><EM><SPAN style="FONT-SIZE: 13.5pt; COLOR: olive"><STRONG>VENHA FAZER PARTE
DESTE SELETO GRUPO DE CLIENTES SATISFEITOS.</STRONG></SPAN></EM></P>
<P><STRONG><EM><SPAN style="FONT-SIZE: 13.5pt; COLOR: #ff8000">E
MAIS: </SPAN></EM><SPAN style="FONT-SIZE: 13.5pt; COLOR: #ff8000">
DESENVOLVEMOS QUALQUER ÍTEM SOB DESENHO OU AMOSTRA.</SPAN></STRONG></P>
<P><SPAN style="FONT-SIZE: 13.5pt; COLOR: black"><STRONG>MUITO OBRIGADO POR
VOSSA ATENÇÃO E SE PUDER AJUDAR ME LIGUE.</STRONG></SPAN></P>
<P> </P>
<P><SPAN style="FONT-SIZE: 13.5pt"><STRONG>CONTATO<SPAN style="mso-spacerun: yes"> </SPAN>0XX13<SPAN style="mso-spacerun: yes"> </SPAN>30282634<SPAN style="mso-spacerun: yes">
</SPAN><o:p></o:p></STRONG></SPAN></P>
<P><SPAN style="FONT-SIZE: 13.5pt"><STRONG><SPAN style="mso-spacerun: yes">
</SPAN><SPAN style="mso-spacerun: yes"> </SPAN>0XX13
97323554 </STRONG></SPAN></P>
<P><o:p><FONT size=3> </FONT></o:p></P>
<P><SPAN style="FONT-SIZE: 13.5pt"><STRONG>SDS HAILSON
<SPAN style="mso-spacerun: yes"> </SPAN>// DEPTO PRODUÇÃO //
VENDAS.</STRONG></SPAN></P>
<P></FONT></P>
<HR SIZE=1>
<FONT face="Verdana, Arial" size=1><FONT color=#808080><B>OBS:</B> Você está
recebendo este e-mail porque está cadastrado para tal. Caso você não deseje mais
receber nenhum tipo de contato nosso, </FONT><a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26462439&i=0" target="_top" rel="nofollow">seuemail@...</a><FONT color=#808080>, ou envie um e-mail para <B><a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26462439&i=1" target="_top" rel="nofollow">seuemail@...</a></B> com o assunto
REMOVER.</FONT></FONT> </BODY></HTML>
<p>From forum: <a href="http://old.nabble.com/cr.yp.to---pari-dev-f863.html" embed="fixTarget[863]" target="_top" >cr.yp.to - pari-dev</a></p>tag:old.nabble.com,2006:post-26458417Re: Checking sender ID2009-11-21T08:57:00Z2009-11-21T08:57:00ZErwin HoffmannHi Wong
<br><br><br>--On Samstag, November 21, 2009 14:26:42 +0800 Wong <<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26458417&i=0" target="_top" rel="nofollow">wongbali@...</a>>
<br>wrote:
<br><div class='shrinkable-quote'><br>> Dear All,
<br>>
<br>> So far, our qmail allow all user sent messages as long as they are in our
<br>> LAN subnet.
<br>>
<br>> I need advise how to limit qmail to allow users sending out messages
<br>> (only) if they use company domain. By that policy, user only able to send
<br>> out messages with 2 conditions:
<br>>
<br>> 1. In LAN subnet
<br>> 2. Use specific (company) domain
<br>>
<br>> All incoming messages should not effected by this setting. Is it possible?
</div><br>Plain (= vanilla) qmail does not support this restriction.
<br><br>However, you can use my 'Mail From: Address Verification' (MAV) patch for
<br>qmail which allows you to setup those filter mechanisms.
<br>MAV is also part of my SPAMCONTROL.
<br><br><a href="http://www.fehcom.de/qmail.html" target="_top" rel="nofollow">http://www.fehcom.de/qmail.html</a><br><br>regards.
<br>--eh.
<br><br>Dr. Erwin Hoffmann | FEHCom | <a href="http://www.fehcom.de/" target="_top" rel="nofollow">http://www.fehcom.de/</a><br><p>From forum: <a href="http://old.nabble.com/cr.yp.to---qmail-f870.html" embed="fixTarget[870]" target="_top" >cr.yp.to - qmail</a></p>tag:old.nabble.com,2006:post-26454192Checking sender ID2009-11-20T22:26:42Z2009-11-20T22:26:42ZWong-8Dear All,
<br><br>So far, our qmail allow all user sent messages as long as they are in our
<br>LAN subnet.
<br><br>I need advise how to limit qmail to allow users sending out messages (only)
<br>if they use company domain. By that policy, user only able to send out
<br>messages with 2 conditions:
<br><br>1. In LAN subnet
<br>2. Use specific (company) domain
<br><br>All incoming messages should not effected by this setting. Is it possible?
<br><br>Thank you so much for your help.
<br><br>Best Rgds,
<br><br>Wong
<br><br><br><p>From forum: <a href="http://old.nabble.com/cr.yp.to---qmail-f870.html" embed="fixTarget[870]" target="_top" >cr.yp.to - qmail</a></p>tag:old.nabble.com,2006:post-26437528Re: tcpserver, qmail-smtpd, qmail-queue and filter Qs2009-11-19T18:24:54Z2009-11-19T18:24:54ZMarkus Stumpf-4On Fri, Nov 20, 2009 at 10:03:17AM +1100, Philip Rhoades wrote:
<br>> Good question - why is it that the two pairs can have different values?
<br><br>Just think of this mailing list.
<br>The 2822.From of your message was
<br> Philip Rhoades <<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26437528&i=0" target="_top" rel="nofollow">phil@...</a>>
<br>but the 2821.FROM points to the qmail list manager, as this is where
<br>administrative messages regarding this message should go to (like
<br>recipient does no longer exist).
<br>Also (although I have never seen that) per RFC 2822 a email can have
<br>more than one address in the 2822.From field, but only one 2821.MAILFROM.
<br><br>Just think of the 2821.MAILFROM as what it is often called: the envelope
<br>sender. As with a lot of snail mail messages the address on the envelope
<br>may be somewhat generic, while the address on the letter in the envelope
<br>is more specific.
<br><br> \Maex
<br><br><p>From forum: <a href="http://old.nabble.com/cr.yp.to---qmail-f870.html" embed="fixTarget[870]" target="_top" >cr.yp.to - qmail</a></p>tag:old.nabble.com,2006:post-26435811Re: tcpserver, qmail-smtpd, qmail-queue and filter Qs2009-11-19T15:03:17Z2009-11-19T15:03:17ZPhilip Rhoades-2Adi,
<br><br><br>On 2009-11-19 17:03, Adi Pircalabu wrote:
<div class='shrinkable-quote'><br>> On Thu, 19 Nov 2009 11:48:35 +1100 Philip Rhoades wrote:
<br>>
<br>>> I was thinking if the sender's and recipient's addresses could be
<br>>> available immediately after greylite, I could block black listed
<br>>> senders and recipients before qmail-smtpd execs?
<br>>
<br>> 1. Sender (as specified by MAIL FROM) and recipient (as specified by
<br>> RPCTO TO) email addresses in the message envelope can differ to the ones
<br>> in the email message (specified by From: and To:). Which one is the
<br>> pair of addresses you are referring to?
</div><br><br>Good question - why is it that the two pairs can have different values?
<br><br><br>> 2. Addresses in the envelope are not available until qmail-smtpd is
<br>> executed, because that's the process that sends "220 hostname ESMTP".
<br>> Before this message the client won't send any envelope information.
<br><br><br>That doesn't seem to be the case - greylite execs before qmail-smtpd and
<br>in the greylite code there is this:
<br><br>#define SMTP_ENVELOPE_OK 0
<br>/* session OK, envelope data stored correctly */
<br><br>Thanks,
<br><br>Phil.
<br>--
<br>Philip Rhoades
<br><br>GPO Box 3411
<br>Sydney NSW 2001
<br>Australia
<br>E-mail: <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26435811&i=0" target="_top" rel="nofollow">phil@...</a>
<br><p>From forum: <a href="http://old.nabble.com/cr.yp.to---qmail-f870.html" embed="fixTarget[870]" target="_top" >cr.yp.to - qmail</a></p>tag:old.nabble.com,2006:post-26429471Re: tcpserver, qmail-smtpd, qmail-queue and filter Qs2009-11-19T08:16:37Z2009-11-19T08:16:37ZKyle Wheeler-2-----BEGIN PGP SIGNED MESSAGE-----
<br>Hash: SHA256
<br><br>On Thursday, November 19 at 11:48 AM, quoth Philip Rhoades:
<br>> In my setup tcpserver execs greylite which eventually execs
<br>> qmail-smtpd. Greylite uses the to and from IP addresses of the tcp
<br>> communication - is any of the message itself (header lines?, body?)
<br>> available at this point or only after qmail-smtpd runs?
<br><br>As other folks have pointed out, the short answer is "no".
<br><br>But, I think the longer answer is: just precisely what is it that you
<br>think qmail-smtpd *does*? If the message is available before
<br>qmail-smtpd runs to communicate with the sender, what's the purpose of
<br>qmail-smtpd?
<br><br>Qmail-smtpd is there to SPEAK SMTP. That is, it can handle
<br>authentication, allows the sender to specify recipients and the
<br>sender, and finally prompts the sender to transmit the message. Before
<br>that happens, the sender HAS NOT SENT THE MESSAGE. Thus, none of it is
<br>available. Your question is akin to asking "is it possible to find out
<br>what the lottery number will be before they draw the numbers from the
<br>lottery machine?". The message is transmitted by talking SMTP;
<br>qmail-smtpd is the program that speaks SMTP; without talking SMTP, no
<br>part of the message has been transmitted (and you have not received
<br>it). Before qmail-smtpd runs, you know only the information about the
<br>connection itself: the IP address (and hostname) of the connecting
<br>client, the port numbers that are being used.
<br><br>> In the qmail-qfilter setup, the filtering of the message is done
<br>> after qmail-smtpd processes the message and before it hands it to
<br>> qmail-queue. So it looks like any filtering on lines from the
<br>> message itself has to be done at this point.
<br><br>Indeed - do you understand why that is the case?
<br><br>> I was thinking if the sender's and recipient's addresses could be
<br>> available immediately after greylite, I could block black listed
<br>> senders and recipients before qmail-smtpd execs?
<br><br>The sender and recipient list is transmitted VIA SMTP. Without
<br>speaking SMTP (i.e. by using some program (such as qmail-smtpd) to
<br>speak SMTP), you cannot know that information. Similarly, you cannot
<br>know the first number that will come out of the lotto machine without
<br>turning the lotto machine on.
<br><br>If you want to create a greylisting behavior that includes
<br>sender/recipient information, you probably want to use something like
<br>the RCPTCHECK patch to qmail-smtpd, which allows qmail-smtpd to call
<br>another program to verify recipients AFTER the sender and recipients
<br>have been specified but BEFORE the message has been sent. I even have
<br>an example script on my website, here:
<br><a href="http://www.memoryhole.net/qmail/#rcptcheck" target="_top" rel="nofollow">http://www.memoryhole.net/qmail/#rcptcheck</a><br><br>Hope that helps. :)
<br><br>~Kyle
<br>- --
<br>A tyrant must put on the appearance of uncommon devotion to religion.
<br>Subjects are less apprehensive of illegal treatment from a ruler whom
<br>they consider God-fearing and pious. On the other hand, they do less
<br>easily move against him, believing that he has the gods on his side.
<br> -- Aristotle
<br>-----BEGIN PGP SIGNATURE-----
<br>Comment: Thank you for using encryption!
<br><br>iQIcBAEBCAAGBQJLBW9lAAoJECuveozR/AWeb9AP/jm7pK4bJ69etM3hmuAI35gA
<br>r7Y23GysxE1shpkbsBQIJVVAuroPudjIOeBqQJjcfB+WD7iuPlkjtms1CBvi5yY5
<br>U+53P2mERLB1/tIJQvYMOqoDW+yYRtoLURdkJpNOAu5a7C1rccC4/4cKkpCSeBsq
<br>7egYcRWNMTHbcmeKhuAYF0wr2uek2rGdm794yzzV/OGwMy+vat3CA9vCPE5gCKpX
<br>Exke4aOclQ4nXRCjdD110PGGoTDufasY5/NPiklS2b+dSw6ptKPQk412BzvabL77
<br>EgMQGKMC+ZlW+0mQgjjtKYBwaLk8YLacRjl8HmJCEIe3cRniWT72lUXuhGLhGoXp
<br>yu2JLG9K0kSwQBqAJFWx3RRdbUC6hSJYO2X79bR3JTW0HGwvbB87wHFHFFFg13M8
<br>dA9uLFyyh+gkxsxww05Ro0wyY/ZYY+iDWlfoIUJ0YXeY6CGU2bCTUxAPRHZQEwmT
<br>eN6i4vTCE99la04Ds86lBYuBuOLghdkxAjT2yNPpGJtNKLqbVHhk8XWwfmBkz5hY
<br>shk+CZJswx452WPrHkYKK6stwaaQjPHcTreIX3RNgsRqVN5hPEf471rCrspk2KxW
<br>DNBCt2cHXOHSP27+JRQJz2XwHIYabSVFWHfx++NQ5NOeiFtvgFsFHdPHm2NT7db/
<br>MXG7xdKpbAJtmQ6ahVFv
<br>=nFkg
<br>-----END PGP SIGNATURE-----
<br><p>From forum: <a href="http://old.nabble.com/cr.yp.to---qmail-f870.html" embed="fixTarget[870]" target="_top" >cr.yp.to - qmail</a></p>tag:old.nabble.com,2006:post-26425708Re: Ideals2009-11-19T04:51:50Z2009-11-19T04:51:50ZBill Allombert-3On Thu, Nov 19, 2009 at 01:21:54PM +0100, Vojtech Brtnik wrote:
<br>> Hello,
<br>>
<br>> I am trying to figure out how to list all prime ideals and ideals
<br>> (with norm under certain bound) in a field Q(a) where a is a root of
<br>> certain irreducible polynomial... I am relatively newbie to PARI so if
<br>> there is a better place to ask these questions please let me kindly
<br>> know.
<br><br>Look at the function ideallist:
<br><br>? ideallist(nfinit(x^3+x+1),10)
<br>%2 = [[[1, 0, 0; 0, 1, 0; 0, 0, 1]], [], [[3, 1, 2; 0, 1, 0; 0, 0, 1]], [], [],
<br>[], [], [[2, 0, 0; 0, 2, 0; 0, 0, 2]], [[9, 4, 2; 0, 1, 0; 0, 0, 1], [3, 0, 1; 0, 3, 1; 0, 0, 1]], []]
<br><br>Cheers,
<br>Bill.
<br><p>From forum: <a href="http://old.nabble.com/cr.yp.to---pari-users-f864.html" embed="fixTarget[864]" target="_top" >cr.yp.to - pari-users</a></p>tag:old.nabble.com,2006:post-26425375Ideals2009-11-19T04:21:54Z2009-11-19T04:21:54ZVojtech Brtnik-2Hello,
<br><br>I am trying to figure out how to list all prime ideals and ideals
<br>(with norm under certain bound) in a field Q(a) where a is a root of
<br>certain irreducible polynomial... I am relatively newbie to PARI so if
<br>there is a better place to ask these questions please let me kindly
<br>know.
<br><br>Best regards,
<br>V.
<br><p>From forum: <a href="http://old.nabble.com/cr.yp.to---pari-users-f864.html" embed="fixTarget[864]" target="_top" >cr.yp.to - pari-users</a></p>tag:old.nabble.com,2006:post-26420882Re: tcpserver, qmail-smtpd, qmail-queue and filter Qs2009-11-18T22:03:32Z2009-11-18T22:03:32ZAdi PircalabuOn Thu, 19 Nov 2009 11:48:35 +1100 Philip Rhoades wrote:
<br><br>> I was thinking if the sender's and recipient's addresses could be
<br>> available immediately after greylite, I could block black listed
<br>> senders and recipients before qmail-smtpd execs?
<br><br>1. Sender (as specified by MAIL FROM) and recipient (as specified by
<br>RPCTO TO) email addresses in the message envelope can differ to the ones
<br>in the email message (specified by From: and To:). Which one is the
<br>pair of addresses you are referring to?
<br>2. Addresses in the envelope are not available until qmail-smtpd is
<br>executed, because that's the process that sends "220 hostname ESMTP".
<br>Before this message the client won't send any envelope information.
<br><br>--
<br>Adi Pircalabu
<br><p>From forum: <a href="http://old.nabble.com/cr.yp.to---qmail-f870.html" embed="fixTarget[870]" target="_top" >cr.yp.to - qmail</a></p>tag:old.nabble.com,2006:post-26420769Re: tcpserver, qmail-smtpd, qmail-queue and filter Qs2009-11-18T21:41:18Z2009-11-18T21:41:18ZDhaval Thakar-2<br><br><div class="gmail_quote">On Thu, Nov 19, 2009 at 6:18 AM, Philip Rhoades <span dir="ltr"><<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26420769&i=0" target="_top" rel="nofollow">phil@...</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
People,<br>
<br>
Following up the previous question re tcpserver operation:<br>
<br>
In my setup tcpserver execs greylite which eventually execs qmail-smtpd. Greylite uses the to and from IP addresses of the tcp communication - is any of the message itself (header lines?, body?) available at this point or only after qmail-smtpd runs?<br>
<br>
In the qmail-qfilter setup, the filtering of the message is done after qmail-smtpd processes the message and before it hands it to qmail-queue. So it looks like any filtering on lines from the message itself has to be done at this point. I was thinking if the sender's and recipient's addresses could be available immediately after greylite, I could block black listed senders and recipients before qmail-smtpd execs?<br>
<br>
Thanks,<br>
<br>
<br></blockquote><div>i have blocked blacklisted sender & recipient at smtp using jms patch<br>
all you need to do is to mention email ids in badmailfrom &
badrcptto of qmail control folder.<br>
<br>
-- <br>
Regards<br>
Dhaval Thakar<br>
<a href="http://www.linuxreaders.com" target="_top" rel="nofollow">http://www.linuxreaders.com</a><br>
<br>
<br></div></div><br><br clear="all"><br>/<br><br>
<p>From forum: <a href="http://old.nabble.com/cr.yp.to---qmail-f870.html" embed="fixTarget[870]" target="_top" >cr.yp.to - qmail</a></p>tag:old.nabble.com,2006:post-26419576Re: duplicate copy2009-11-18T18:52:19Z2009-11-18T18:52:19Zpackets-2Thanks Andrew! It works
<br>>
<br>> If it's not you could use a tool like safecat instead,
<br>>
<br>> ./Maildir/
<br>> |safecat Maildir/tmp Maildir/backup
<br>>
<br>>
<br>>
<br><p>From forum: <a href="http://old.nabble.com/cr.yp.to---qmail-f870.html" embed="fixTarget[870]" target="_top" >cr.yp.to - qmail</a></p>tag:old.nabble.com,2006:post-26418741Re: tcpserver, qmail-smtpd, qmail-queue and filter Qs2009-11-18T17:07:46Z2009-11-18T17:07:46ZCharles Cazabon-17Philip Rhoades <<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26418741&i=0" target="_top" rel="nofollow">phil@...</a>> wrote:
<br>>
<br>> In my setup tcpserver execs greylite which eventually execs qmail-smtpd.
<br>> Greylite uses the to and from IP addresses of the tcp communication - is
<br>> any of the message itself (header lines?, body?) available at this point
<br>> or only after qmail-smtpd runs?
<br><br>No, no data has been exchanged with the client before qmail-smtpd runs. The
<br>only information that is available is that which tcpserver makes available to
<br>the program it runs through the various environment variables it sets.
<br><br>> In the qmail-qfilter setup, the filtering of the message is done after
<br>> qmail-smtpd processes the message and before it hands it to qmail-queue. So
<br>> it looks like any filtering on lines from the message itself has to be done
<br>> at this point.
<br><br>Yes, exactly.
<br><br>> I was thinking if the sender's and recipient's addresses could be available
<br>> immediately after greylite, I could block black listed senders and
<br>> recipients before qmail-smtpd execs?
<br><br>Not without a magic wand ;)
<br><br>Charles
<br>--
<br>--------------------------------------------------------------------------
<br>Charles Cazabon
<br>GPL'ed software available at: <a href="http://pyropus.ca/software/" target="_top" rel="nofollow">http://pyropus.ca/software/</a><br>Read <a href="http://pyropus.ca/personal/writings/12-steps-to-qmail-list-bliss.html" target="_top" rel="nofollow">http://pyropus.ca/personal/writings/12-steps-to-qmail-list-bliss.html</a><br>--------------------------------------------------------------------------
<br><p>From forum: <a href="http://old.nabble.com/cr.yp.to---qmail-f870.html" embed="fixTarget[870]" target="_top" >cr.yp.to - qmail</a></p>tag:old.nabble.com,2006:post-26418564tcpserver, qmail-smtpd, qmail-queue and filter Qs2009-11-18T16:48:35Z2009-11-18T16:48:35ZPhilip Rhoades-2People,
<br><br>Following up the previous question re tcpserver operation:
<br><br>In my setup tcpserver execs greylite which eventually execs qmail-smtpd.
<br>Greylite uses the to and from IP addresses of the tcp communication - is
<br>any of the message itself (header lines?, body?) available at this point
<br>or only after qmail-smtpd runs?
<br><br>In the qmail-qfilter setup, the filtering of the message is done after
<br>qmail-smtpd processes the message and before it hands it to qmail-queue.
<br> So it looks like any filtering on lines from the message itself has to
<br>be done at this point. I was thinking if the sender's and recipient's
<br>addresses could be available immediately after greylite, I could block
<br>black listed senders and recipients before qmail-smtpd execs?
<br><br>Thanks,
<br><br>Phil.
<br>--
<br>Philip Rhoades
<br><br>GPO Box 3411
<br>Sydney NSW 2001
<br>Australia
<br>E-mail: <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26418564&i=0" target="_top" rel="nofollow">phil@...</a>
<br><p>From forum: <a href="http://old.nabble.com/cr.yp.to---qmail-f870.html" embed="fixTarget[870]" target="_top" >cr.yp.to - qmail</a></p>tag:old.nabble.com,2006:post-26411566Re: tcpserver help2009-11-18T08:58:09Z2009-11-18T08:58:09ZPhilip Rhoades-2Markus, Kyle, Otavio,
<br><br><br>On 2009-11-19 03:05, Kyle Wheeler wrote:
<div class='shrinkable-quote'><br>> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256
<br>>
<br>> On Wednesday, November 18 at 03:47 PM, quoth Philip Rhoades:
<br>>> Yes, I understand and it is more or less what I thought - so if
<br>>> greylite (or any other prog in the chain) exits with the
<br>>> appropriate return value, the rest of the chain is not executed?
<br>>
<br>> If you're worried about the return value, then you're not
<br>> understanding what I wrote.
<br>>
<br>> The process is called "exec chaining" because the fundamental aspect
<br>> of it is the "exec" system call, which (on Unix machines) fully and
<br>> completely replaces the application that makes the call with the
<br>> program it specifies. For example, if I have a program (let's call it
<br>> "tcpserver") that calls "exec(/usr/bin/greylite)", then the program
<br>> is no longer tcpserver, it is now greylite. Tcpserver is gone and
<br>> cannot come back, it cannot control what greylite does, and when
<br>> greylite exits the program simply ends (tcpserver does not restart
<br>> or come back or anything even remotely similar). An "exec chain" is
<br>> when several programs exec each other one after the next: first
<br>> tcpserver execs greylite, then greylite execs qmail-smtpd, then
<br>> qmail-smtpd exits, the end. (OR, alternately, first tcpserver execs
<br>> greylite, then greylite exits, the end.) You see? The "return code"
<br>> has no impact on the chain. In fact, when a program calls "exec", it
<br>> does not have an opportunity to return any code of any sort: it is
<br>> now a completely different program.
</div><br><br>Right.
<br><br><div class='shrinkable-quote'><br>> Now, things are actually slightly more complicated. The "exec" call
<br>> is normally (i.e. when not doing "exec chaining") paired with a
<br>> "fork" call. "Fork", on Unix machines, creates a duplicate of a
<br>> program. So, if tcpserver calls "fork", suddenly I have *TWO*
<br>> instances of tcpserver. This is how tcpserver can behave as a
<br>> server. For every new connection, it duplicates itself. The original
<br>> goes back to listening for new connections, while the duplicate
<br>> calls "exec" to replace itself with some program (e.g. greylite).
<br>>
<br>> Thus, tcpserver runs one program, and only one program, and only ever
<br>> one program.
</div><br><br>Right.
<br><br><br>> That program may do whatever it likes. It can exec another program
<br>> (and thus cease to exist), OR it may return whatever return code it
<br>> likes. Tcpserver (the original) does nothing more than record that
<br>> return value in the log file.
<br>>
<br>> Does that clear things up somewhat?
<br><br><br>Very well thanks!
<br><br><div class='shrinkable-quote'><br>>> So if I construct a script that does the filtering that I want then
<br>>> I just need it to be able to exec the rest of the chain if
<br>>> necessary?
<br>>
<br>> Exactly.
<br>>
<br>> For example, if you wanted to create a script that would only allow
<br>> connections from the IP address 1.2.3.4, what would that mean? (Yes,
<br>> there are simpler ways of doing this than with a wrapper script, but
<br>> I'm using this as an informative example.) In an exec-chain like
<br>> this, "allowing the connection" means "continuing the chain", which
<br>> really means "exec-ing the next program in the chain (and passing
<br>> along the arguments to define the rest of the chain)". "Denying the
<br>> connection" means simply exiting.
<br>>
<br>> So, here's an example simple script that demonstrates (more verbosely
<br>> than necessary) the idea:
<br>>
<br>> #!/bin/bash if [ $TCPREMOTEIP == 1.2.3.4 ] ; then exec "$@" else
<br>> exit $RANDOM fi
<br>>
<br>> You'll notice that the exit code is random. That's to emphasize that
<br>> it is irrelevant. You may be wondering "what does this "$@" mean?".
<br>> In bash, the $@ variable is a reference to the arguments that have
<br>> been passed to the program. Putting the $@ variable in quotes tells
<br>> bash to expand the variable to its component pieces as if each
<br>> component (each argument) was in quotes (if that makes no sense to
<br>> you, ignore it for the moment and just take on faith that the quotes
<br>> are important to use).
</div><br><br>OK.
<br><br><br>> So, now you have to ask yourself: how does this fit into the chain?
<br>> You'll note that it doesn't check the return value of whatever it
<br>> exec's, and yet the exec chain after this program can be long and
<br>> complicated.
<br>>
<br>> If you already know all this, I apologize for flogging a dead horse.
<br>> But by talking about the return code, it sounded like you didn't
<br>> quite understand the concept.
<br><br><br>No, I was probably still a bit confused and I didn't explain myself
<br>clearly enough - I guess I was thinking of the qmail-qfilter situation
<br>and the return codes from the filter programs returned to the
<br>qmail-qfilter program.
<br><br><br>> It's worth pointing out: this is VERY different from how
<br>> qmail-qfilter works, because qmail-qfilter doesn't use exec
<br>> chaining. Qmail-qfilter runs each program (read: "filter"), captures
<br>> its output and its return code, and decides whether to run the next
<br>> program.
<br><br><br>Understood clearly now.
<br><br><br>> ~Kyle
<br><br><br>Many thanks for the in-depth responses! I have learnt a lot with this
<br>exercise!
<br><br>Appreciatively,
<br><br>Phil.
<br>--
<br>Philip Rhoades
<br><br>GPO Box 3411
<br>Sydney NSW 2001
<br>Australia
<br>E-mail: <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26411566&i=0" target="_top" rel="nofollow">phil@...</a>
<br><p>From forum: <a href="http://old.nabble.com/cr.yp.to---qmail-f870.html" embed="fixTarget[870]" target="_top" >cr.yp.to - qmail</a></p>tag:old.nabble.com,2006:post-26410722Re: tcpserver help2009-11-18T08:05:22Z2009-11-18T08:05:22ZKyle Wheeler-2-----BEGIN PGP SIGNED MESSAGE-----
<br>Hash: SHA256
<br><br>On Wednesday, November 18 at 03:47 PM, quoth Philip Rhoades:
<br>> Yes, I understand and it is more or less what I thought - so if
<br>> greylite (or any other prog in the chain) exits with the appropriate
<br>> return value, the rest of the chain is not executed?
<br><br>If you're worried about the return value, then you're not
<br>understanding what I wrote.
<br><br>The process is called "exec chaining" because the fundamental aspect
<br>of it is the "exec" system call, which (on Unix machines) fully and
<br>completely replaces the application that makes the call with the
<br>program it specifies. For example, if I have a program (let's call it
<br>"tcpserver") that calls "exec(/usr/bin/greylite)", then the program is
<br>no longer tcpserver, it is now greylite. Tcpserver is gone and cannot
<br>come back, it cannot control what greylite does, and when greylite
<br>exits the program simply ends (tcpserver does not restart or come back
<br>or anything even remotely similar). An "exec chain" is when several
<br>programs exec each other one after the next: first tcpserver execs
<br>greylite, then greylite execs qmail-smtpd, then qmail-smtpd exits, the
<br>end. (OR, alternately, first tcpserver execs greylite, then greylite
<br>exits, the end.) You see? The "return code" has no impact on the
<br>chain. In fact, when a program calls "exec", it does not have an
<br>opportunity to return any code of any sort: it is now a completely
<br>different program.
<br><br>Now, things are actually slightly more complicated. The "exec" call is
<br>normally (i.e. when not doing "exec chaining") paired with a "fork"
<br>call. "Fork", on Unix machines, creates a duplicate of a program. So,
<br>if tcpserver calls "fork", suddenly I have *TWO* instances of
<br>tcpserver. This is how tcpserver can behave as a server. For every new
<br>connection, it duplicates itself. The original goes back to listening
<br>for new connections, while the duplicate calls "exec" to replace
<br>itself with some program (e.g. greylite).
<br><br>Thus, tcpserver runs one program, and only one program, and only ever
<br>one program.
<br><br>That program may do whatever it likes. It can exec another program
<br>(and thus cease to exist), OR it may return whatever return code it
<br>likes. Tcpserver (the original) does nothing more than record that
<br>return value in the log file.
<br><br>Does that clear things up somewhat?
<br><br>> So if I construct a script that does the filtering that I want then
<br>> I just need it to be able to exec the rest of the chain if
<br>> necessary?
<br><br>Exactly.
<br><br>For example, if you wanted to create a script that would only allow
<br>connections from the IP address 1.2.3.4, what would that mean? (Yes,
<br>there are simpler ways of doing this than with a wrapper script, but
<br>I'm using this as an informative example.) In an exec-chain like this,
<br>"allowing the connection" means "continuing the chain", which really
<br>means "exec-ing the next program in the chain (and passing along the
<br>arguments to define the rest of the chain)". "Denying the connection"
<br>means simply exiting.
<br><br>So, here's an example simple script that demonstrates (more verbosely
<br>than necessary) the idea:
<br><br> #!/bin/bash
<br> if [ $TCPREMOTEIP == 1.2.3.4 ] ; then
<br> exec "$@"
<br> else
<br> exit $RANDOM
<br> fi
<br><br>You'll notice that the exit code is random. That's to emphasize that
<br>it is irrelevant. You may be wondering "what does this "$@" mean?". In
<br>bash, the $@ variable is a reference to the arguments that have been
<br>passed to the program. Putting the $@ variable in quotes tells bash to
<br>expand the variable to its component pieces as if each component (each
<br>argument) was in quotes (if that makes no sense to you, ignore it for
<br>the moment and just take on faith that the quotes are important to
<br>use).
<br><br>So, now you have to ask yourself: how does this fit into the chain?
<br>You'll note that it doesn't check the return value of whatever it
<br>exec's, and yet the exec chain after this program can be long and
<br>complicated.
<br><br>If you already know all this, I apologize for flogging a dead horse.
<br>But by talking about the return code, it sounded like you didn't quite
<br>understand the concept.
<br><br>It's worth pointing out: this is VERY different from how qmail-qfilter
<br>works, because qmail-qfilter doesn't use exec chaining. Qmail-qfilter
<br>runs each program (read: "filter"), captures its output and its return
<br>code, and decides whether to run the next program.
<br><br>~Kyle
<br>- --
<br>I see the pain on your face when you say the word intellectual,
<br>because it has so many syllables in it.
<br> -- Clive James
<br>-----BEGIN PGP SIGNATURE-----
<br>Comment: Thank you for using encryption!
<br><br>iQIcBAEBCAAGBQJLBBs7AAoJECuveozR/AWelJYP/2PQ678WDRIqUxom+WJ3XpR4
<br>aSEUnMUP8knuJHX+2nCJs/Lm3GayaJ4XpfQZe+qJpIUAj1WzrBafCyvZz4WQwfF6
<br>vrYGFzSeTpiF1WFSA1WXVzul+TOj5lZ/7tunw1SJCdujufkYuZD0aIsHcoeA2FDh
<br>WXyC3zRW2zcsOkVG9vfjc4U+x2av/C/lXW5dNFo4gp5omr4jRchfjbdA4SKW9asx
<br>vgmeY4nN0DkHwzUL63uhkKNgfxzht1+ps6ta7CG4Ot6Qv+DjJE1ApWWKMpBtECVB
<br>mT+lUEBQ8h6x2wDAv775BMsc+AETtVBKccwbUyI/JxXctlcCpZkYb67hStjoT3f4
<br>W/Edg5BkyoBkA4IliNuU/OfhHe9WjmzXRsGuiuFzgQLCm7usJPX095JJoO6P1MN+
<br>FseHAuCWLkZRVGlWA/t4KR1TCydn6zq5iZy3Wf/8SI2Y2DjckINBe+vTkq+dk39Y
<br>c9HaiY1ZY+aHyLT8fYZRZdHAhE1hv5FopquC/Zc3i84smvR7Z6o/WuDVYvmkGJqs
<br>h4GwOYQXeckJ7HuWx66eQ0hbRpr5jvW/Cmd2aqcrHlO5CSLoa14+Mso9NQef1LGO
<br>ZXSAM4vfvMRIfu3wGUHvNL5H55WobH4gecXh5NO6UN+g5z+6Gc4syf2Fv9AKp0lL
<br>ZIStwlnowKc5Fk6JkdC2
<br>=E+Ja
<br>-----END PGP SIGNATURE-----
<br><p>From forum: <a href="http://old.nabble.com/cr.yp.to---qmail-f870.html" embed="fixTarget[870]" target="_top" >cr.yp.to - qmail</a></p>tag:old.nabble.com,2006:post-26406149Re: duplicate copy (corrected)2009-11-18T03:21:29Z2009-11-18T03:21:29ZAndrew Richards-3On Wednesday 18 November 2009 09:04:03 nelsonts wrote:
<div class='shrinkable-quote'><br>> Anyone can give me a hint or advise how can I duplicate all emails
<br>> coming on a user to a have a copy to another folder inside his Maildir
<br>> directory.
<br>>
<br>> Example.
<br>>
<br>> There's a directory called backup inside the Maildir other than new, cur
<br>> and tmp. Of course if someone email to a user, the email will go to new
<br>> directory under Maildir. I want also to have a copy of that every new
<br>> email to the backup folder inside the Maildir. I believe I can do this
<br>> in .qmail inside the user's home directory. I just don't know where to
<br>> start. Can anyone give me a url or suggestion how to do this. Can I
<br>> create a simple bash script to put on .qmail to make this thing run?
</div><br>If Maildir/backup is also a Maildir, (so you have backup/cur, backup/new,
<br>backup/tmp) then you can just have your .qmail with,
<br><br> ./Maildir/
<br> ./Maildir/backup/
<br><br>If it's not you could use a tool like safecat instead,
<br><br> ./Maildir/
<br> |safecat Maildir/tmp Maildir/backup
<br><br>cheers,
<br><br>Andrew.
<br>--
<br>====================================================================
<br> * Custom email solutions * Systems Administration * Networking
<br> <a href="http://www.acrconsulting.co.uk/email/qmail.html" target="_top" rel="nofollow">http://www.acrconsulting.co.uk/email/qmail.html</a><br>====================================================================
<br><br><p>From forum: <a href="http://old.nabble.com/cr.yp.to---qmail-f870.html" embed="fixTarget[870]" target="_top" >cr.yp.to - qmail</a></p>tag:old.nabble.com,2006:post-26405330Re: tcpserver help2009-11-18T02:12:48Z2009-11-18T02:12:48ZOtavio Exel> On Wed, Nov 18, 2009 at 03:47:30PM +1100, Philip Rhoades wrote:
<br>> > Yes, I understand and it is more or less what I thought - so if
<br>> > greylite (or any other prog in the chain) exits with the appropriate
<br>> > return value, the rest of the chain is not executed?
<br><br>Markus Stumpf wrote:
<br>> Yes. But the return code is kinda irrelevant.
<br><br>Markus,
<br><br>looks like there's some misunderstanding going on;
<br><br>I guess Philip thinks there is an other shell-like program that:
<br>- execs progA
<br>- checks progA's exit code
<br>- depending on it's value execs progB
<br><br>I could be wrong (happens all the time);
<br><br>[]s,
<br><br>--
<br>Otavio Exel /<\oo/>\ <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26405330&i=0" target="_top" rel="nofollow">oexel@...</a>
<br><p>From forum: <a href="http://old.nabble.com/cr.yp.to---qmail-f870.html" embed="fixTarget[870]" target="_top" >cr.yp.to - qmail</a></p>tag:old.nabble.com,2006:post-26404716Re: duplicate copy2009-11-18T01:22:32Z2009-11-18T01:22:32ZAndrew Richards-3On Wednesday 18 November 2009 09:04:03 nelsonts wrote:
<div class='shrinkable-quote'><br>> Anyone can give me a hint or advise how can I duplicate all emails
<br>> coming on a user to a have a copy to another folder inside his Maildir
<br>> directory.
<br>>
<br>> Example.
<br>>
<br>> There's a directory called backup inside the Maildir other than new, cur
<br>> and tmp. Of course if someone email to a user, the email will go to new
<br>> directory under Maildir. I want also to have a copy of that every new
<br>> email to the backup folder inside the Maildir. I believe I can do this
<br>> in .qmail inside the user's home directory. I just don't know where to
<br>> start. Can anyone give me a url or suggestion how to do this. Can I
<br>> create a simple bash script to put on .qmail to make this thing run?
</div><br>If Maildir/backup is also a Maildir, (so you have backup/cur, backup/new,
<br>backup/tmp) then you can just have your .qmail with,
<br><br> ./Maildir/
<br> ./backup/Maildir/
<br><br>If it's not you could use a tool like safecat instead,
<br><br> ./Maildir/
<br> |safecat Maildir/tmp Maildir/backup
<br><br>cheers,
<br><br>Andrew.
<br>--
<br>====================================================================
<br> * Custom email solutions * Systems Administration * Networking
<br> <a href="http://www.acrconsulting.co.uk/email/qmail.html" target="_top" rel="nofollow">http://www.acrconsulting.co.uk/email/qmail.html</a><br>====================================================================
<br><p>From forum: <a href="http://old.nabble.com/cr.yp.to---qmail-f870.html" embed="fixTarget[870]" target="_top" >cr.yp.to - qmail</a></p>tag:old.nabble.com,2006:post-26404516duplicate copy2009-11-18T01:04:03Z2009-11-18T01:04:03Zpackets-2Anyone can give me a hint or advise how can I duplicate all emails
<br>coming on a user to a have a copy to another folder inside his Maildir
<br>directory.
<br><br>Example.
<br><br>There's a directory called backup inside the Maildir other than new, cur
<br>and tmp. Of course if someone email to a user, the email will go to new
<br>directory under Maildir. I want also to have a copy of that every new
<br>email to the backup folder inside the Maildir. I believe I can do this
<br>in .qmail inside the user's home directory. I just don't know where to
<br>start. Can anyone give me a url or suggestion how to do this. Can I
<br>create a simple bash script to put on .qmail to make this thing run?
<br><p>From forum: <a href="http://old.nabble.com/cr.yp.to---qmail-f870.html" embed="fixTarget[870]" target="_top" >cr.yp.to - qmail</a></p>