🚀 go-pugleaf

On Thu, 24 Jun 2004 19:04:35 +0000 (UTC), Soruk <soruk@bitbucket.eridani.co.uk> wrote:
> 
> 
> Hi there.
> 
> I'm trying to write something that will enforce a message size limit, 
> intended for use over a modem connection.
> 
> The other catch: No ESMTP. It has to be workable with bog-standard SMTP.
> 
> Is there a way of doing this without having to wait for all 10Mb of a 
> message to squeeze its way down a 28k8 phone line?
> 
> I know just kicking the connection will make the sending server treat it 
> as a 4xx error and retry later. What I want to do is to somehow tell it to 
> get lost and don't bother retrying if the message hits a particular 
> size threshold.
> 

Fetchmail will dump mails over a certain size, but I am not clear whether
it downloads them first or not. Procmail downloads them and then dumps
them.

I have an nc (netcat) script (bash) that could be modified to pull down the
message numbers and sizes, and then delete any that were too large 
on the server (POP) and then either bring the rest of the mail down
or get out of the way.

You can also bring down the headers and scan them for anything else 
objectionable and have those mails deleted on the server too.

There is a tool called "mailfilter" that brings down the headers for
the same reasons, and I assume that it has the option to set a size
limit.

(I THINK I have that name right.)


AC



-- 
Pass-List -----> Block-List ----> Challenge-Response
The key to taking control of your mailbox.  Design Parameters:
http://tinyurl.com/2t5kp ||   http://tinyurl.com/3c3ag
Challenge-Response links -- http://tinyurl.com/yrfjb

[fu-t set -- cross-posted articles should always have one set]

in comp.mail.misc i read:

>I'm trying to write something that will enforce a message size limit, 
>intended for use over a modem connection.
>
>The other catch: No ESMTP. It has to be workable with bog-standard SMTP.
>
>Is there a way of doing this without having to wait for all 10Mb of a 
>message to squeeze its way down a 28k8 phone line?

not really.  you might write a mime parser into your mta (which in general
is a mistake to do in an mta), in which case there may be sufficient clues
available (content-length headers) which you would trust (which an mta
should not do, and even a mime parser should be wary of mistakes), but even
that might not always work (think lots of small objects).

>I know just kicking the connection will make the sending server treat it 
>as a 4xx error and retry later. What I want to do is to somehow tell it to 
>get lost and don't bother retrying if the message hits a particular 
>size threshold.

you must return a 5xx code.  technically you shouldn't send it until the
sender is done, but in general it works to send it as soon as your limit is
exceeded; either the sender will immediately stop (modulo stuff already in
transit) or it will continue and you'll just have to dump the connection
and hope it processes the 5xx even though it had an abrupt disconnect.  and
you'll need to decide how to cope with sites that aren't willing to deviate
sufficiently from the standard for this to work -- they'll retry, and even
if you abort as soon as the message-id is seen (another mistake for an mta)
that might end-up transferring as many or more bytes across all retries as
the message you are trying to block, i.e., you need to learn from which
servers you have to give-up and take it.

-- 
a signature

On Thu, 24 Jun 2004 20:09:40 GMT, Alan Connor <zzzzzz@xxx.yyy> wrote:
> 
> 
> On Thu, 24 Jun 2004 19:04:35 +0000 (UTC), Soruk <soruk@bitbucket.eridani.co.uk> wrote:
>> 
>> 
>> Hi there.
>> 
>> I'm trying to write something that will enforce a message size limit, 
>> intended for use over a modem connection.
>> 
>> The other catch: No ESMTP. It has to be workable with bog-standard SMTP.
>> 
>> Is there a way of doing this without having to wait for all 10Mb of a 
>> message to squeeze its way down a 28k8 phone line?
>> 
>> I know just kicking the connection will make the sending server treat it 
>> as a 4xx error and retry later. What I want to do is to somehow tell it to 
>> get lost and don't bother retrying if the message hits a particular 
>> size threshold.
>> 
> 
> Fetchmail will dump mails over a certain size, but I am not clear whether
> it downloads them first or not. Procmail downloads them and then dumps
> them.
> 
> I have an nc (netcat) script (bash) that could be modified to pull down the
> message numbers and sizes, and then delete any that were too large 
> on the server (POP) and then either bring the rest of the mail down
> or get out of the way.
> 
> You can also bring down the headers and scan them for anything else 
> objectionable and have those mails deleted on the server too.
> 
> There is a tool called "mailfilter" that brings down the headers for
> the same reasons, and I assume that it has the option to set a size
> limit.
> 
> (I THINK I have that name right.)
> 

I checked to see whether fetchmail downloads oversized  mail before deleting
it, and it doesn't. Here are the strings from my packet logger for fetchmail
checking for new mail in a POP mailbox with only one, oversized mail in it:
The size limit set in fetchmail is 20K.

pop     earthlink
pop     earthlink
itchy
scratchy
+OK NGPopper vEL_7_8 at earthlink.net ready <14247.1078111293@scaup.mail.paz.ear
thlink.net>
8CAPA
user
pass
uidl
KUSER me@earthlink.net
^PASS XXXXXXXXX
+OK me has 1 messages (36416 octets).
pSTAT
+OK 1 36416
LIST
<'+OK
1 36416
DELE 1
<7+OK
QUIT
<H+OK


(no, I have no idea what "itchy\nscratchy" means :-)

AC


-- 
Pass-List -----> Block-List ----> Challenge-Response
The key to taking control of your mailbox.  Design Parameters:
http://tinyurl.com/2t5kp ||   http://tinyurl.com/3c3ag
Challenge-Response links -- http://tinyurl.com/yrfjb

On Thursday, in article
     <slrncdm9e3.dql.soruk@zeskia.int.eridani.co.uk>
     soruk@bitbucket.eridani.co.uk "Soruk" wrote:

> Hi there.
> 
> I'm trying to write something that will enforce a message size limit, 
> intended for use over a modem connection.
> 
> The other catch: No ESMTP. It has to be workable with bog-standard SMTP.
> 
> Is there a way of doing this without having to wait for all 10Mb of a 
> message to squeeze its way down a 28k8 phone line?

No.

The SMTP client (i.e. the remote end that's sending the 10MB to you) will
not expect any sort of status return from you until it's sent all of the
message (following its DATA command, and your "go ahead").  As you said
(in the snipped bit) it will merely requeue and try again if you drop the
line mid-transfer.

-- 
   fix (vb.): 1. to paper over, obscure, hide from public view; 2. to
   work around, in a way that produces unintended consequences that are
   worse than the original problem.  Usage: "Windows ME fixes many of the
   shortcomings of Windows 98 SE".

This is a MIME GnuPG-signed message.  If you see this text, it means that
your E-mail or Usenet software does not support MIME signed messages.

--=_mimegpg-grandpa.email-scan.com-31700-1088119432-0001
Content-Type: text/plain; format=flowed; charset="US-ASCII"
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

Soruk writes:

> I know just kicking the connection will make the sending server treat it 
> as a 4xx error and retry later. What I want to do is to somehow tell it to 
> get lost and don't bother retrying if the message hits a particular 
> size threshold.

This is not possible with SMTP.


--=_mimegpg-grandpa.email-scan.com-31700-1088119432-0001
Content-Type: application/pgp-signature
Content-Transfer-Encoding: 7bit

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)

iD8DBQBA22KIx9p3GYHlUOIRAqA/AJsHppQxgJiqAjJlsmu6NY0cPpbboACfco5Z
WUWjWkhbZQ2ReKb+NHCEOc0=
=gVwv
-----END PGP SIGNATURE-----

--=_mimegpg-grandpa.email-scan.com-31700-1088119432-0001--

This is a MIME GnuPG-signed message.  If you see this text, it means that
your E-mail or Usenet software does not support MIME signed messages.

--=_mimegpg-grandpa.email-scan.com-31700-1088119478-0002
Content-Type: text/plain; format=flowed; charset="US-ASCII"
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

Alan Connor writes:

> On Thu, 24 Jun 2004 19:04:35 +0000 (UTC), Soruk <soruk@bitbucket.eridani.co.uk> wrote:
> 
>> I know just kicking the connection will make the sending server treat it 
>> as a 4xx error and retry later. What I want to do is to somehow tell it to 
>> get lost and don't bother retrying if the message hits a particular 
>> size threshold.
>> 
> 
> Fetchmail will dump mails over a certain size, but I am not clear whether
> it downloads them first or not. Procmail downloads them and then dumps
> them.

He is not talking about fetchmail.  This has nothing to do with fetchmail.  
He is receiving mail using SMTP.


--=_mimegpg-grandpa.email-scan.com-31700-1088119478-0002
Content-Type: application/pgp-signature
Content-Transfer-Encoding: 7bit

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)

iD8DBQBA22K2x9p3GYHlUOIRAmz2AJ9HKzBWetEaa2IxB88lIA4APdFfngCcCD3/
iH1NpDoiep5LYxXq9H2+Hbo=
=W6vR
-----END PGP SIGNATURE-----

--=_mimegpg-grandpa.email-scan.com-31700-1088119478-0002--

On 25 Jun 2004 18:20:36 GMT, "Huge" wrote:
> 
> 
> Alan Connor <zzzzzz@xxx.yyy> writes:
> 
>>I checked to see whether fetchmail 
> 
> fetchmail is a POP3 tool, not SMTP.
> 

Yes. I see that now. He's running a full-fledged MTA accepting mail
on port 25. I thought was just an ordinary user downloading mail from
his ISP (etc.) and trying to get his MTA to do things it wasn't designed
to do.

Which he apparently is. I have never heard of a way to configure an MTA
to do what he wants and I don't see anyone else here coming up with
a way.


------------------------------------------------------------------------

> -- 
>        "The road to Paradise is through Intercourse."
> 


No it isn't. At best you could say that it CAN be a road to a Paradise of a
sorts, and no one needs YOU to tell them that.  Furthermore, I have never met 
a woman worth spending time with that cared about the size of a man's penis.
That's a myth promoted by clueless, neurotic, and over-competitive men.
Sex is a beautiful thing, except when used as a drug.
Yes. I know about Tantra Yoga, but that's not what you are about. No Tantra
Yogi would ever use an alias like you have chosen.

AC


-- 
Pass-List -----> Block-List ----> Challenge-Response
The key to taking control of your mailbox.  Design Parameters:
http://tinyurl.com/2t5kp ||   http://tinyurl.com/3c3ag
Challenge-Response links -- http://tinyurl.com/yrfjb

This is a MIME GnuPG-signed message.  If you see this text, it means that
your E-mail or Usenet software does not support MIME signed messages.

--=_mimegpg-grandpa.email-scan.com-7461-1088203206-0005
Content-Type: text/plain; format=flowed; charset="US-ASCII"
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

Huge writes:

> Sam <sam@email-scan.com> writes:
>>This is a MIME GnuPG-signed message.  If you see this text, it means that
> 
> ... I am a selfish or ignorant twat who does not realise that Usenet is a plain
> text medium.

... you are an ignorant twat for assuming that when the shitware you use to 
read Usenet cannot properly show a plain text message that's formatted in 
accordance to an eight-year old MIME standard, it must mean that there's 
something wrong with the message.



--=_mimegpg-grandpa.email-scan.com-7461-1088203206-0005
Content-Type: application/pgp-signature
Content-Transfer-Encoding: 7bit

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)

iD8DBQBA3KnGx9p3GYHlUOIRAt2GAJ9wQAhShHRme33UHYQ2WilQSRQXzACeNMsr
C1X9cwvwkG5TMYLAwuphkVI=
=eZnW
-----END PGP SIGNATURE-----

--=_mimegpg-grandpa.email-scan.com-7461-1088203206-0005--

This is a MIME GnuPG-signed message.  If you see this text, it means that
your E-mail or Usenet software does not support MIME signed messages.

--=_mimegpg-grandpa.email-scan.com-16287-1088260203-0002
Content-Type: text/plain; format=flowed; charset="UTF-8"
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
X-Mime-Autoconverted: from 8bit to quoted-printable by mimegpg

Huge writes:

> Sam <sam@email-scan.com> writes:
>>This is a MIME GnuPG-signed message.  If you see this text, it means that
> 
> ... the poster is an ignorant retard with a broken newsreader
> 
>>your E-mail or Usenet software does not support MIME signed messages.
> 
> Newsreaders don't have to.

Yes, they do.

>                            Usenet is a plain text medium.

And MIME is a plain text format.

>                                                           I expect you're
> the sort of fucktard who sends HTML emails, too.

You need to go back to school in order to study up on fucktards.  Using 
yourself as an example is not enough.

>>Content-Type: text/plain; format=3Dflowed; charset=3D"US-ASCII"

What part of =E2=80=9Ctext/plain=E2=80=9D do you not understand?

>>.... you are an ignorant twat for assuming that when the shitware you use =
to 
>>read Usenet cannot properly show a plain text message that's formatted in 
>>accordance to an eight-year old MIME standard, it must mean that there's 
>>something wrong with the message.
> 
> Good lord, is there a day trip from the asylum today? Are the drooling
> retards wandering the byways of usenet, wearing their "I am an ignorant
> cunt" sandwich boards, with shit dribbling down their legs, opening
> their mouths and letting content-free grunting noises out?

Go and drink your tea with crumpets, or I'll have the Germans bomb you back 
to the stone-age, again.

> 
> Yes, yes, and yes agin, it would appear.
> 
> Now fuck off and die with Connor the failed lorry driver, eh?

                         TROLL-O-MATIC

+-----+-----+-----+-----+-----+-----+-----+-----+-----+-----+
|     |     |     |     |     |     |     |     |     |     |
|  1  |  2  |  3  |  4  |  5  |  6  |  7  |  8  |  9  | 10  |
|     |     |     |     |     |     |     |     |     |     |
+-----+-----+-----+-----+-----+-----+-----+-----+-----+-----+
   _
  /|\
   |
   |
   |


Not even a blip.


--=_mimegpg-grandpa.email-scan.com-16287-1088260203-0002
Content-Type: application/pgp-signature
Content-Transfer-Encoding: 7bit

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)

iD8DBQBA3Yhrx9p3GYHlUOIRAl+TAJ9qLKTaIrW5GTYraTVKNeBuGnBp6gCfaCTg
zDvIjttb4cGt0oHEXghEsIc=
=XYru
-----END PGP SIGNATURE-----

--=_mimegpg-grandpa.email-scan.com-16287-1088260203-0002--

This is a MIME GnuPG-signed message.  If you see this text, it means that
your E-mail or Usenet software does not support MIME signed messages.

--=_mimegpg-commodore.email-scan.com-5727-1088268432-0002
Content-Type: text/plain; format=flowed; charset="US-ASCII"
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

Huge writes:

> (please don't make fun of me in alt.usenet.kooks, I have a very low
> self-esteem)

Too late.

> Sam <sam@email-scan.com> writes:
>>This is a MIME GnuPG-signed message.  If you see this text, it means that
> 
> The poster is a cunt.

Don't be too hard on yourself.

>>Huge writes:
>>
>>> Sam <sam@email-scan.com> writes:
>>>>This is a MIME GnuPG-signed message.  If you see this text, it means that
>>> 
>>> ... the poster is an ignorant retard with a broken newsreader
>>> 
>>>>your E-mail or Usenet software does not support MIME signed messages.
>>> 
>>> Newsreaders don't have to.
>>
>>Yes, they do.
> 
> *plonk*

Looks like we've found Beavis' evil twin.

Someday your children will come across their papa's old messages archived in 
Google, and will immediately order a paternity test.



--=_mimegpg-commodore.email-scan.com-5727-1088268432-0002
Content-Type: application/pgp-signature
Content-Transfer-Encoding: 7bit

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQBA3aiQx9p3GYHlUOIRAvMHAJ4/UAxjtLZr69c/2le3gkui3XlO7wCdH2Sz
eK8Mp5gwBlsWSYyovA6xWRs=
=qdtM
-----END PGP SIGNATURE-----

--=_mimegpg-commodore.email-scan.com-5727-1088268432-0002--

On Saturday, in article
     <cone.1088260203.500461.16287.501@grandpa.email-scan.com>
     sam@email-scan.com "Sam" wrote:

> Huge writes:
> 
> > Sam <sam@email-scan.com> writes:
> >>your E-mail or Usenet software does not support MIME signed messages.
> > 
> > Newsreaders don't have to.
> 
> Yes, they do.

Please quote the relevant RFC.  As yet, there is only ONE standard for
network.news[1]; said standard requires that news articles be posted in
plain SEVEN-bit ASCII text.

[Hint: what does the second M represent in the acronym MIME?]

BTW, I see that you are the sort of unadultered cunt that cross-posts to
irrelevant groups without mentioning that you've changed the Followup-To;
your lacuna has been corrected.  If you were a Demon customer, you'd be
arguing about retaining posting privileges by now.

[1] To refer to non-Usenet hierarchies such as demon.* with the epithet
"Usenet" displays even more of your ignorance.  Or were you unaware that
your shite was cross-posted?

-- 
   fix (vb.): 1. to paper over, obscure, hide from public view; 2. to
   work around, in a way that produces unintended consequences that are
   worse than the original problem.  Usage: "Windows ME fixes many of the
   shortcomings of Windows 98 SE".

This is a MIME GnuPG-signed message.  If you see this text, it means that
your E-mail or Usenet software does not support MIME signed messages.

--=_mimegpg-commodore.email-scan.com-6266-1088344444-0002
Content-Type: text/plain; format=flowed; charset="UTF-8"
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
X-Mime-Autoconverted: from 8bit to quoted-printable by mimegpg

Brian {Hamilton Kelly} writes:

> On Saturday, in article
>      <cone.1088260203.500461.16287.501@grandpa.email-scan.com>
>      sam@email-scan.com "Sam" wrote:
> 
>> Huge writes:
>> 
>> > Sam <sam@email-scan.com> writes:
>> >>your E-mail or Usenet software does not support MIME signed messages.
>> > 
>> > Newsreaders don't have to.
>> 
>> Yes, they do.
> 
> Please quote the relevant RFC.

    RFC 850:

                                                Therefore, the
    rule is adopted that all  USENET  news  articles  must  be
    formatted as valid ARPANET mail messages, according to the
    ARPANET  standard  RFC  822.

MIME defines the format using which a =E2=80=9Cvalid ARPANET mail message=E2=
=80=9D may carry 
arbitrary media types, which is now also applicable to Usenet.

>                                As yet, there is only ONE standard for
> network.news[1]; said standard requires that news articles be posted in
> plain SEVEN-bit ASCII text.

No, it doesn't.

> [Hint: what does the second M represent in the acronym MIME?]

Hint: have you been toilet-trained yet?

> BTW, I see that you are the sort of unadultered cunt that cross-posts to
> irrelevant groups without mentioning that you've changed the Followup-To;
> your lacuna has been corrected.

Boo-hoo.  Boo-hoo-hoo.

>                                 If you were a Demon customer, you'd be
> arguing about retaining posting privileges by now.

Bite my shiny metal ass.

> [1] To refer to non-Usenet hierarchies such as demon.* with the epithet
> "Usenet" displays even more of your ignorance.  Or were you unaware that
> your shite was cross-posted?

Are you unaware that you are arguing with your mental superior?



--=_mimegpg-commodore.email-scan.com-6266-1088344444-0002
Content-Type: application/pgp-signature
Content-Transfer-Encoding: 7bit

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQBA3tF8x9p3GYHlUOIRAvHzAJ9nqOrutuzW6EyLO6+jzgaTp/yMSgCfRrWc
Y+pfwzj/fqFFSeNQQBRAHC8=
=j53r
-----END PGP SIGNATURE-----

--=_mimegpg-commodore.email-scan.com-6266-1088344444-0002--

Brian {Hamilton Kelly} wrote:
> 
> On Saturday, in article
>      <cone.1088260203.500461.16287.501@grandpa.email-scan.com>
>      sam@email-scan.com "Sam" wrote:
> 
> > Huge writes:
> >
> > > Sam <sam@email-scan.com> writes:
> > >>your E-mail or Usenet software does not support MIME signed messages.
> > >
> > > Newsreaders don't have to.
> >
> > Yes, they do.
> 
> Please quote the relevant RFC.  As yet, there is only ONE standard for
> network.news[1]; said standard requires that news articles be posted in
> plain SEVEN-bit ASCII text.
> 
> [Hint: what does the second M represent in the acronym MIME?]

I'm unaware of any formal standard specific to netnews. Neither RFC 850 nor
RFC 1036 are standards; the status of both is "unknown". However, since RFC
1036 is widely used, one could refer to it as a de facto standard.

As an interesting note, RFC 1036 mandates that all Usenet news messages must
be formatted as valid Internet mail messages.

Follow-ups set.

Thor

-- 
http://www.anta.net/

Alan Connor wrote:

> I checked to see whether fetchmail downloads oversized  mail before deleting
> it, and it doesn't. Here are the strings from my packet logger for fetchmail
> checking for new mail in a POP mailbox with only one, oversized mail in it:
> The size limit set in fetchmail is 20K.

FYI, there isn't any size limit in fetchmail unless it is configured to use
one.

From the fetchmail man page;
{
 -l <maxbytes> | --limit <maxbytes>
              (Keyword: limit) Takes a maximum octet size argument.  Messages 
larger  than  this  size will not be fetched and will be left on the server 
(in foreground sessions, the progress  messages will note  that they are 
"oversized").  If the fetch protocol permits (in particular, under IMAP or 
POP3 without the fetchall option) the  message  will  not  be marked seen 
An explicit --limit of 0 overrides any limits set in your run control file.  
This option is intended for those needing to strictly control fetch time due
to expensive and variable phone rates.  Combined  with --flush, it can be 
used to delete oversized messages waiting on a server.  In daemon mode, 
oversize notifications are mailed to the calling user  (see  the  
--warnings  option).  This option does not work with ETRN or ODMR.
}

HTH

-- 
Black Dragon                                       /"\  ASCII ribbon campaign
                                                   \ /  against HTML mail and
Hell, rocket science isn't even rocket science.     X   postings.
A NASA Rocket Scientist; Undernet; circa 1996      / \

On Tue, 29 Jun 2004 21:12:39 GMT, Black Dragon <bd@thedragons.lair> wrote:
> 
> 
> Alan Connor wrote:
> 
>> I checked to see whether fetchmail downloads oversized  mail before deleting
>> it, and it doesn't. Here are the strings from my packet logger for fetchmail
>> checking for new mail in a POP mailbox with only one, oversized mail in it:
>> The size limit set in fetchmail is 20K.
> 
> FYI, there isn't any size limit in fetchmail unless it is configured to use
> one.
> 

Yes. I know. How else could I have done what I did above if I didn't know
that? Fetchmail doesn't do anything unless it is configured to do it. A
blank fetchmailrc will not get your mail down.

I've been deleting mails from strangers over 20K for a long time with
fetchmail. It's a great way to kill spam: No one I want to know would
send a mail that large to me on the first contact. If they want to
at a later date, then there are simple ways to arrange it.


> From the fetchmail man page;
> {
>  -l <maxbytes> | --limit <maxbytes>
>               (Keyword: limit) Takes a maximum octet size argument.  Messages 
> larger  than  this  size will not be fetched and will be left on the server 
> (in foreground sessions, the progress  messages will note  that they are 
> "oversized").  If the fetch protocol permits (in particular, under IMAP or 
> POP3 without the fetchall option) the  message  will  not  be marked seen 
> An explicit --limit of 0 overrides any limits set in your run control file.  
> This option is intended for those needing to strictly control fetch time due
> to expensive and variable phone rates.  Combined  with --flush, it can be 
> used to delete oversized messages waiting on a server.  In daemon mode, 
> oversize notifications are mailed to the calling user  (see  the  
> --warnings  option).  This option does not work with ETRN or ODMR.
> }
> 
> HTH


I appreciate the thought.


AC


-- 
Pass-List -----> Block-List ----> Challenge-Response
The key to taking control of your mailbox.  Design Parameters:
http://tinyurl.com/2t5kp ||   http://tinyurl.com/3c3ag
Challenge-Response links -- http://tinyurl.com/yrfjb

On 2005-05-16, Sam <sam@email-scan.com> wrote:
> Alan Connor writes:
>
>> On Thu, 24 Jun 2004 19:04:35 +0000 (UTC), Soruk <soruk@bitbucket.eridani.co.uk> wrote:
>> 
>>> I know just kicking the connection will make the sending server treat it 
>>> as a 4xx error and retry later. What I want to do is to somehow tell it to 
>>> get lost and don't bother retrying if the message hits a particular 
>>> size threshold.
>> 
>> Fetchmail will dump mails over a certain size, but I am not clear whether
>> it downloads them first or not. Procmail downloads them and then dumps
>> them.
>
> He is not talking about fetchmail.  This has nothing to do with fetchmail.  
> He is receiving mail using SMTP.

Good grief. I know Usenet has been getting quieter lately, but I started 
this thread nearly five YEARS ago.

-- 
-- Michael "Soruk" McConnell         Eridani Star System
   MailStripper - http://www.MailStripper.eu/ - SMTP spam filter
   Second Number - http://secondnumber.matrixnetwork.co.uk/
   International Calls - http://calls.matrixnetwork.co.uk/

In article  <slrnh1o7ra.52m.soruk@Zeskia.int.eridani.co.uk>
           soruk@bitbucket.eridani.co.uk "Soruk" writes:

> On 2005-05-16, Sam <sam@email-scan.com> wrote:
> > Alan Connor writes:
> >
> >> On Thu, 24 Jun 2004 19:04:35 +0000 (UTC), Soruk <soruk@bitbucket.eridani.co.
> uk> wrote:
> >> 
> >>> I know just kicking the connection will make the sending server treat it 
> >>> as a 4xx error and retry later. What I want to do is to somehow tell it to 
> >>> get lost and don't bother retrying if the message hits a particular 
> >>> size threshold.
> >> 
> >> Fetchmail will dump mails over a certain size, but I am not clear whether
> >> it downloads them first or not. Procmail downloads them and then dumps
> >> them.
> >
> > He is not talking about fetchmail.  This has nothing to do with fetchmail.  
> > He is receiving mail using SMTP.
> 
> Good grief. I know Usenet has been getting quieter lately, but I started 
> this thread nearly five YEARS ago.

Hey, don't knock the repeats -- the TV companies have been punting 
old stuff for years ;-)  And it is very quiet in here.

But talking of punts I did start a thread "Demon punts and SMTP" 
a short while back, originally in demon.ip.support.pc and followed 
up in demon.service, concerning the punts' apparent inability to 
use ESMTP (and its SIZE extemsion).  And, it transpired, to handle 
properly any 5xx error after completion of DATA.

Maybe we'll have to wait another five years for this topic to be 
resurrected ;-)

Pete
-- 
   "We have not inherited the earth from our ancestors,
    we have borrowed it from our descendants."

This is a MIME GnuPG-signed message.  If you see this text, it means that
your E-mail or Usenet software does not support MIME signed messages.
The Internet standard for MIME PGP messages, RFC 2015, was published in 1996.
To open this message correctly you will need to install E-mail or Usenet
software that supports modern Internet standards.

--=_mimegpg-commodore.email-scan.com-26462-1243464456-0002
Content-Type: text/plain; format=flowed; charset="US-ASCII"
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

pete@nospam.demon.co.uk writes:

> In article  <slrnh1o7ra.52m.soruk@Zeskia.int.eridani.co.uk>
>            soruk@bitbucket.eridani.co.uk "Soruk" writes:
> 
>> On 2005-05-16, Sam <sam@email-scan.com> wrote:
>> > Alan Connor writes:
>> >
>> >> On Thu, 24 Jun 2004 19:04:35 +0000 (UTC), Soruk <soruk@bitbucket.eridani.co.
>> uk> wrote:
>> >> 
>> >>> I know just kicking the connection will make the sending server treat it 
>> >>> as a 4xx error and retry later. What I want to do is to somehow tell it to 
>> >>> get lost and don't bother retrying if the message hits a particular 
>> >>> size threshold.
>> >> 
>> >> Fetchmail will dump mails over a certain size, but I am not clear whether
>> >> it downloads them first or not. Procmail downloads them and then dumps
>> >> them.
>> >
>> > He is not talking about fetchmail.  This has nothing to do with fetchmail.  
>> > He is receiving mail using SMTP.
>> 
>> Good grief. I know Usenet has been getting quieter lately, but I started 
>> this thread nearly five YEARS ago.
> 
> Hey, don't knock the repeats -- the TV companies have been punting 
> old stuff for years ;-)  And it is very quiet in here.
> 
> But talking of punts I did start a thread "Demon punts and SMTP" 
> a short while back, originally in demon.ip.support.pc and followed 
> up in demon.service, concerning the punts' apparent inability to 
> use ESMTP (and its SIZE extemsion).  And, it transpired, to handle 
> properly any 5xx error after completion of DATA.
> 
> Maybe we'll have to wait another five years for this topic to be 
> resurrected ;-)

Or, maybe the original poster figured out that his news provider must've 
restored some old backup tapes, for some reason, and he's the only one who 
apparently saw the repeat.



--=_mimegpg-commodore.email-scan.com-26462-1243464456-0002
Content-Type: application/pgp-signature
Content-Transfer-Encoding: 7bit

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)

iEYEABECAAYFAkodwwgACgkQx9p3GYHlUOJk5gCeNhJp09fNpLRap37FyG8OFSo/
cTUAnjGQEUUkkMLVzc29UsuuId7F3WT/
=KF3k
-----END PGP SIGNATURE-----

--=_mimegpg-commodore.email-scan.com-26462-1243464456-0002--