I have found that lowering the MTU helps a lot. If it is a particular route,
simply add an additional route with the lower limit set. The tradeoff of
efficiency v.s. reliability is improved.
-d
Horst von Brand wrote:
> In my experience, if you try to send large messages over unreliable
> netw
"Richard B. Johnson" <[EMAIL PROTECTED]> said:
> On Fri, 10 Nov 2000, Andrea Arcangeli wrote:
[...]
> > Ok. So please now show a tcpdump trace during the `sendmail -q` so we
> > can see what's going wrong in the TCP connection to the smtp server:
> >
> > tcpdump port smtp
> I tried to send
On Sat, Nov 11, 2000 at 01:24:18PM +, Henning P. Schmiedehausen wrote:
> [EMAIL PROTECTED] (Jeff V. Merkey) writes:
>
> >I did Dick. The config is fine. The daemon is also fine and running.
> >What's really weird is that even if I do a "sendmail -v -q" command
> >(which should force the qu
[EMAIL PROTECTED] (Dominik Kubla) writes:
>I can do better! I had a smart ass trying to backup his harddrives
>using email, no less than 2Gig!
So what? Get enough spool space in /var/spool/mqueue and a platform
with 64 bit file support and it works just fine. I have some boxes
where the users se
[EMAIL PROTECTED] (Claus Assmann) writes:
>> Sending a 50 MB file is OK here. So it's not a TCP/IP bug.
>Ok, hopefully this reaches everyone who has been "involved"
>by Jeff into this "problem".
So it is _once_ _again_ a Jeff "I have no clue but I know Linux-Kernel
list is cheaper than tech su
[EMAIL PROTECTED] (Jeff V. Merkey) writes:
>I did Dick. The config is fine. The daemon is also fine and running.
>What's really weird is that even if I do a "sendmail -v -q" command
>(which should force the queue to flush) it still doesn't.
O Timeout.ident=0s
O Timeout.initial=30s (these are
[EMAIL PROTECTED] (Jeff V. Merkey) writes:
>The sendmail folks are claiming that the TCPIP stack in Linux is broken,
>which is what they claim is causing problems on sendmail on Linux
>platforms. Before anyone says, "don't use that piece of shit sendmail,
>use qmail instead", perhaps we should l
On Fri, Nov 10, 2000 at 06:02:28PM -0800, David Ford wrote:
> > > With a handle like
> > > "Assmann", deviation is proably something you already understand quite
> > > well ...
> >
> > Don't be a moron. Claus is German, Assman really is his last name and
> > not some "handle", and it's pronoun
On Fri, Nov 10, 2000 at 05:15:53PM -0800, Steve VanDevender wrote:
> Jeff V. Merkey writes:
> > There was also an issue relative to how sendmail is interpreting load
> > average on a linux box. [EMAIL PROTECTED] pointed out that perhaps you
> > are not factoring sleeping processes, which Linux
> > With a handle like
> > "Assmann", deviation is proably something you already understand quite
> > well ...
>
> Don't be a moron. Claus is German, Assman really is his last name and
> not some "handle", and it's pronounced "Oss-man".
Claus is a well liked, knowledgable and well experienced
Jeff V. Merkey writes:
> There was also an issue relative to how sendmail is interpreting load
> average on a linux box. [EMAIL PROTECTED] pointed out that perhaps you
> are not factoring sleeping processes, which Linux does -- a deviation
> from BSD's interpretation of load average.
At wors
> > > Turn on encryption, and try sending attachements > 1MB and tell me if
> > > you see any problems, like emails sitting in /var/spool/mqueue for a day
> > > or two until they go out. I can guarantee you will.
> >
> > Are you talking client -> MTA encryption, or MTA -> MTA encryption ??
>
>
Claus Assmann wrote:
>
> On Sat, Nov 11, 2000, Igmar Palsenberg wrote:
> >
> > > > It ran out of memory. The file got sent fine after I got rid of
> > > > all the memory-consumers. Looks like a sendmail bug where they
> > > > expect to load a whole file into memory all at once before sending
>
On Sat, Nov 11, 2000, Igmar Palsenberg wrote:
>
> > > It ran out of memory. The file got sent fine after I got rid of
> > > all the memory-consumers. Looks like a sendmail bug where they
> > > expect to load a whole file into memory all at once before sending
> > > it. I always thought you could
> > It ran out of memory. The file got sent fine after I got rid of
> > all the memory-consumers. Looks like a sendmail bug where they
> > expect to load a whole file into memory all at once before sending
> > it. I always thought you could read from a file, then write to
> > a socket. Maybe I'm
On Fri, 10 Nov 2000, [iso-8859-1] willy tarreau wrote:
> Dick, have you tried a simple "strace -f -p " ?
> This often gives enough info.
>
> BTW, there's one version of sendmail that tests the
> capability security hole of a previous kernel version
> (2.2.15 ?), and refuses to launch if it disco
Igmar Palsenberg wrote:
>
> > Turn on encryption, and try sending attachements > 1MB and tell me if
> > you see any problems, like emails sitting in /var/spool/mqueue for a day
> > or two until they go out. I can guarantee you will.
>
> Are you talking client -> MTA encryption, or MTA -> MTA
> Turn on encryption, and try sending attachements > 1MB and tell me if
> you see any problems, like emails sitting in /var/spool/mqueue for a day
> or two until they go out. I can guarantee you will.
Are you talking client -> MTA encryption, or MTA -> MTA encryption ??
> Jeff
Igma
> > Yes. Plus 8.11.1 has problems talking to older sendmails sine it uses
> > encryption.
>
> I've been using sendmail-8.11.1 (no encryption) to talk to MTAs all over
> the place, many of them so old it is scary. No problems seen at this end.
> This is to be expected, BTW: They can't just go in
> > What about sendmail 8.11.1? Is the problem there too?
>
> Yes. Plus 8.11.1 has problems talking to older sendmails sine it uses
> encryption.
Depends on how you configure it. An enabled encryption doesn't always mean
it has problems taking to other sendmails. This sendmail here has no
pro
Followup to: <[EMAIL PROTECTED]>
By author:Davide Libenzi <[EMAIL PROTECTED]>
In newsgroup: linux.dev.kernel
>
> On Fri, 10 Nov 2000, Claus Assmann wrote:
> > On Fri, Nov 10, 2000, Jeff V. Merkey wrote:
> > > Looks like your bug. As an FYI, sendmail.rpms in Suse, RedHat, and
> > > OpenLinux
On Fri, Nov 10, 2000, Davide Libenzi wrote:
[Please use a MTA that sends the e-mail only once to a given machine,
we got three copies of this]
> On Fri, 10 Nov 2000, Claus Assmann wrote:
> > On Fri, Nov 10, 2000, Jeff V. Merkey wrote:
> > > Looks like your bug. As an FYI, sendmail.rpms in Suse,
"William F. Maton" wrote:
>
> On Fri, 10 Nov 2000, Jeff V. Merkey wrote:
>
> > Andrea Arcangeli wrote:
> > >
> > > On Fri, Nov 10, 2000 at 03:07:46PM -0500, Richard B. Johnson wrote:
> > > > It isn't a TCP/IP stack problem. It may be a memory problem. Every time
> > > > sendmail spawns a child
On Fri, 10 Nov 2000, Claus Assmann wrote:
> On Fri, Nov 10, 2000, Jeff V. Merkey wrote:
> > Looks like your bug. As an FYI, sendmail.rpms in Suse, RedHat, and
> > OpenLinux all exhibit this behavior, which means they're all broken.
>
> Sorry, this is plain wrong. sendmail does NOT read the enti
On Fri, 10 Nov 2000, Jeff V. Merkey wrote:
> Andrea Arcangeli wrote:
> >
> > On Fri, Nov 10, 2000 at 03:07:46PM -0500, Richard B. Johnson wrote:
> > > It isn't a TCP/IP stack problem. It may be a memory problem. Every time
> > > sendmail spawns a child to send the file data, it crashes. That's
On Fri, Nov 10, 2000, Jeff V. Merkey wrote:
> "Richard B. Johnson" wrote:
> > It ran out of memory. The file got sent fine after I got rid of
> > all the memory-consumers. Looks like a sendmail bug where they
> > expect to load a whole file into memory all at once before sending
> > it. I always
"Richard B. Johnson" wrote:
>
>
>
> It ran out of memory. The file got sent fine after I got rid of
> all the memory-consumers. Looks like a sendmail bug where they
> expect to load a whole file into memory all at once before sending
> it. I always thought you could read from a file, then writ
On Fri, 10 Nov 2000, Andrea Arcangeli wrote:
> On Fri, Nov 10, 2000 at 03:07:46PM -0500, Richard B. Johnson wrote:
> > It isn't a TCP/IP stack problem. It may be a memory problem. Every time
> > sendmail spawns a child to send the file data, it crashes. That's
> > why the file never gets sent!
>
Claus,
Richard appears to have found a problem while sending a 45MB file to me
with 8.11.10. I guess it's time for you to join the thread. Please
review attached.
Jeff
On Fri, 10 Nov 2000, Andrea Arcangeli wrote:
> On Fri, Nov 10, 2000 at 12:34:40PM -0700, Jeff V. Merkey wrote:
> >
>
On Fri, 10 Nov 2000, Jeff V. Merkey wrote:
>
>
> Andrea Arcangeli wrote:
> >
> > On Fri, Nov 10, 2000 at 03:07:46PM -0500, Richard B. Johnson wrote:
> > > It isn't a TCP/IP stack problem. It may be a memory problem. Every time
> > > sendmail spawns a child to send the file data, it crashes. T
Andre,
SSH is running on this system, so send me your IP address to add to the
hosts.allow file and I'll send you an account so you can get into the
box and see just what's happening with ssh. Andre Hedrick has root
privileges on this machine, so if I'm ever not around, he can get into
it. I a
Andrea Arcangeli wrote:
>
> On Fri, Nov 10, 2000 at 03:07:46PM -0500, Richard B. Johnson wrote:
> > It isn't a TCP/IP stack problem. It may be a memory problem. Every time
> > sendmail spawns a child to send the file data, it crashes. That's
> > why the file never gets sent!
>
> Sure that cou
Dick, have you tried a simple "strace -f -p " ?
This often gives enough info.
BTW, there's one version of sendmail that tests the
capability security hole of a previous kernel version
(2.2.15 ?), and refuses to launch if it discovers it.
It may be possible that sendmail does other tests like
this
On Fri, Nov 10, 2000 at 03:07:46PM -0500, Richard B. Johnson wrote:
> It isn't a TCP/IP stack problem. It may be a memory problem. Every time
> sendmail spawns a child to send the file data, it crashes. That's
> why the file never gets sent!
Sure that could be the case. You should be able to ver
On Fri, 10 Nov 2000, Andrea Arcangeli wrote:
> On Fri, Nov 10, 2000 at 12:34:40PM -0700, Jeff V. Merkey wrote:
> >
> > Andrea,
> >
> > All done. It's already setup this way.
>
> Ok. So please now show a tcpdump trace during the `sendmail -q` so we can see
> what's going wrong in the TCP conne
On Fri, Nov 10, 2000 at 12:34:40PM -0700, Jeff V. Merkey wrote:
>
> Andrea,
>
> All done. It's already setup this way.
Ok. So please now show a tcpdump trace during the `sendmail -q` so we can see
what's going wrong in the TCP connection to the smtp server:
tcpdump port smtp
Andrea
-
On 11/10/2000 16:30 -0300, Horst von Brand wrote:
>> "Jeff V. Merkey" <[EMAIL PROTECTED]> said:
>> > Horst von Brand wrote:
>>
>> [...]
>>
>> > > I've been using sendmail-8.11.1 (no encryption) to talk to MTAs all over
>>
>> > Turn on encryption, and try
Andrea,
All done. It's already setup this way.
Jeff
Andrea Arcangeli wrote:
>
> On Fri, Nov 10, 2000 at 11:45:39AM -0700, Jeff V. Merkey wrote:
> > > > > > [..] Issuing the command "sendmail -v
> > > > > > -q" does not flush the mail queue. [..]
>
> So first thing to do is to check that in
On Fri, Nov 10, 2000 at 11:45:39AM -0700, Jeff V. Merkey wrote:
> > > > > [..] Issuing the command "sendmail -v
> > > > > -q" does not flush the mail queue. [..]
So first thing to do is to check that in /etc/sendmail.cf this line is
commented out this way:
#O HostStatusDirectory=...
(if you bu
"Richard B. Johnson" wrote:
>
> On Fri, 10 Nov 2000, William F. Maton wrote:
>
> > On Fri, 10 Nov 2000, Jeff V. Merkey wrote:
> >
> > >
> > > The sendmail folks are claiming that the TCPIP stack in Linux is broken,
> > > which is what they claim is causing problems on sendmail on Linux
> > > p
On Fri, 10 Nov 2000, William F. Maton wrote:
> On Fri, 10 Nov 2000, Jeff V. Merkey wrote:
>
> >
> > The sendmail folks are claiming that the TCPIP stack in Linux is broken,
> > which is what they claim is causing problems on sendmail on Linux
> > platforms. Before anyone says, "don't use that
"Jeff V. Merkey" <[EMAIL PROTECTED]> said:
> Horst von Brand wrote:
[...]
> > I've been using sendmail-8.11.1 (no encryption) to talk to MTAs all over
> Turn on encryption, and try sending attachements > 1MB and tell me if
> you see any problems, like emails sitting in /var/spool/mqueue for a d
Claus is sloging into the box and we will be trying to track this down.
If it is a problem in the Linux TCPIP stack, we'll post a report later
this afternoon as to where it looks like the problem is.
Jeff
"Jeff V. Merkey" wrote:
>
> Since I posted this on LKML, Claus over at sendmail.org s
Since I posted this on LKML, Claus over at sendmail.org seems more
motivated to track it down. (since it might appear on the front page of
Linux today). I would love your assistance Richard.
It could be a local problem since smrsh also seems to be f_cked up as
well, but I am seeing the same t
On Fri, 10 Nov 2000, Richard A Nelson wrote:
> On Fri, 10 Nov 2000, Jeff V. Merkey wrote:
>
> > "William F. Maton" wrote:
> > >
> > > What about sendmail 8.11.1? Is the problem there too?
> >
> > Yes. Plus 8.11.1 has problems talking to older sendmails sine it uses
> > encryption.
>
> Eh?!? T
Send me an email from it with an attachment > 1MB, and I will forward
back to you when (and if) It gets delivered before next week.
:-)
Jeff
Richard A Nelson wrote:
>
> On Fri, 10 Nov 2000, Jeff V. Merkey wrote:
>
> > "William F. Maton" wrote:
> > >
> > > What about sendmail 8.11.1? Is the
Horst von Brand wrote:
>
> "Jeff V. Merkey" <[EMAIL PROTECTED]> SAID:
> > "William F. Maton" wrote:
>
> [...]
>
> > > What about sendmail 8.11.1? Is the problem there too?
>
> > Yes. Plus 8.11.1 has problems talking to older sendmails sine it uses
> > encryption.
>
> I've been using sendm
"Jeff V. Merkey" <[EMAIL PROTECTED]> SAID:
> "William F. Maton" wrote:
[...]
> > What about sendmail 8.11.1? Is the problem there too?
> Yes. Plus 8.11.1 has problems talking to older sendmails sine it uses
> encryption.
I've been using sendmail-8.11.1 (no encryption) to talk to MTAs all ove
Richard A Nelson wrote:
>
> Any `real` reason you're still at 8.9.3? Current is 8.11.1
>
> If you send me a note of the type that fails, (to [EMAIL PROTECTED]),
> it'll get received on both a 2.2.18-21/8.11.1 and 2.4.0-test10/8.11.2.Beta0
8.11.1 has problems talking to older sendmails and q
"William F. Maton" wrote:
>
> On Fri, 10 Nov 2000, Jeff V. Merkey wrote:
>
> >
> > The sendmail folks are claiming that the TCPIP stack in Linux is broken,
> > which is what they claim is causing problems on sendmail on Linux
> > platforms. Before anyone says, "don't use that piece of shit se
On Fri, 10 Nov 2000, Jeff V. Merkey wrote:
>
> The sendmail folks are claiming that the TCPIP stack in Linux is broken,
> which is what they claim is causing problems on sendmail on Linux
> platforms. Before anyone says, "don't use that piece of shit sendmail,
> use qmail instead", perhaps we s
The sendmail folks are claiming that the TCPIP stack in Linux is broken,
which is what they claim is causing problems on sendmail on Linux
platforms. Before anyone says, "don't use that piece of shit sendmail,
use qmail instead", perhaps we should look at this problem and refute
these statements
52 matches
Mail list logo
