Re: Radius Question
Which radius server are you using? Steve On Thu, Feb 27, 2003 at 04:02:02PM -0800, Kevin Lynch wrote: > >I'm switching from Radius on a NT Server and I have the program >install but, I'm not sure where the config files are supposed to go in >Debian? > > > >I also can't seem to find useful help files. > > > > > >Suggestions?
Re: Radius Question
Which radius server are you using? Steve On Thu, Feb 27, 2003 at 04:02:02PM -0800, Kevin Lynch wrote: > >I'm switching from Radius on a NT Server and I have the program >install but, I'm not sure where the config files are supposed to go in >Debian? > > > >I also can't seem to find useful help files. > > > > > >Suggestions? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Radius Question
Title: Message I'm switching from Radius on a NT Server and I have the program install but, I'm not sure where the config files are supposed to go in Debian? I also can't seem to find useful help files. Suggestions?
Radius Question
Title: Message I'm switching from Radius on a NT Server and I have the program install but, I'm not sure where the config files are supposed to go in Debian? I also can't seem to find useful help files. Suggestions?
Re: 400 000 mails in 12 Hours
On Thursday 27 February 2003 15:02, Guus Houtzager wrote: > I saw your post on debian-isp containing the following: > > On Thu, 2003-02-27 at 17:26, Fraser Campbell wrote: > > Whatever MTA you use I'm sure you'll need to do some tuning. We had a > > default postfix install that would choke when it had 1,000 messages in > > the queue. It would take up to 3 hours to deliver an email that should > > have been instantly delivered. Now that we've tuned that client's > > postfix a bit it instantly delivers messages even when there are 2 to 3 > > thousand messages in the queue, and without noticable load being added to > > the machine. > > Could you please tell me which options you tweaked to get this speed > increase? The mailservers we use are having the same problem, and if it > can be fixed, it saves me some whining customers complaining about > emaildelays :) > Thanks very much in advance! I'm folllowing up to debian-isp just in case others are interested. These are the steps that I took: - upgrade postfix (that helped marginally, probably because the upgrade switched the default queue manager from qmgr to nqmgr) - increased the process limit for smtp deliveries from 50 to 100, this is in master.cf - we were running a 2.2 kernel so we upped the open files limit to 16384 (default on 2.4 kernel) echo 16384 > /proc/sys/fs/file-max - installed more RAM, during mailing list runs postfix was maxing out the 128MB that was installed (basically it seems to just use 128) after upgrading to 512MB of RAM the usage rarely goes over 128MB but it gets close enough that 128MB alone can't do the job So in answer to your question (except for the resource issues) all we did was up the maximum number of smtp processes and switched to nqmgr from qmgr. Here is the difference that it made, time to deliver emails in a 24 hour period to changes: - 18.3% within 1 minute - 20.0% within 2 minutes - 20.7% within 3 minutes - 21.6% within 4 minutes - 22.2% within 5 minutes - 61.2% within 30 minutes - 88.5% within 1 hour, Time to deliver emails in a 24 hour period after changes: - 48.7% within 1 minute - 68.0% within 2 minutes - 89.2% within 3 minutes - 95.3% within 4 minutes - 98.4% within 5 minutes - 98.7% within 30 minutes - 99.5% within 1 hour As you can see after changes more mail was delivered within 2 minutes than what could previously be done in 30 minutes. Hope this helps. -- Fraser Campbell <[EMAIL PROTECTED]> http://wehave.net/ Brampton, Ontario, CanadaLinux 2.4.20 AuthenticAMD
Re: 400 000 mails in 12 Hours
On Thursday 27 February 2003 15:02, Guus Houtzager wrote: > I saw your post on debian-isp containing the following: > > On Thu, 2003-02-27 at 17:26, Fraser Campbell wrote: > > Whatever MTA you use I'm sure you'll need to do some tuning. We had a > > default postfix install that would choke when it had 1,000 messages in > > the queue. It would take up to 3 hours to deliver an email that should > > have been instantly delivered. Now that we've tuned that client's > > postfix a bit it instantly delivers messages even when there are 2 to 3 > > thousand messages in the queue, and without noticable load being added to > > the machine. > > Could you please tell me which options you tweaked to get this speed > increase? The mailservers we use are having the same problem, and if it > can be fixed, it saves me some whining customers complaining about > emaildelays :) > Thanks very much in advance! I'm folllowing up to debian-isp just in case others are interested. These are the steps that I took: - upgrade postfix (that helped marginally, probably because the upgrade switched the default queue manager from qmgr to nqmgr) - increased the process limit for smtp deliveries from 50 to 100, this is in master.cf - we were running a 2.2 kernel so we upped the open files limit to 16384 (default on 2.4 kernel) echo 16384 > /proc/sys/fs/file-max - installed more RAM, during mailing list runs postfix was maxing out the 128MB that was installed (basically it seems to just use 128) after upgrading to 512MB of RAM the usage rarely goes over 128MB but it gets close enough that 128MB alone can't do the job So in answer to your question (except for the resource issues) all we did was up the maximum number of smtp processes and switched to nqmgr from qmgr. Here is the difference that it made, time to deliver emails in a 24 hour period to changes: - 18.3% within 1 minute - 20.0% within 2 minutes - 20.7% within 3 minutes - 21.6% within 4 minutes - 22.2% within 5 minutes - 61.2% within 30 minutes - 88.5% within 1 hour, Time to deliver emails in a 24 hour period after changes: - 48.7% within 1 minute - 68.0% within 2 minutes - 89.2% within 3 minutes - 95.3% within 4 minutes - 98.4% within 5 minutes - 98.7% within 30 minutes - 99.5% within 1 hour As you can see after changes more mail was delivered within 2 minutes than what could previously be done in 30 minutes. Hope this helps. -- Fraser Campbell <[EMAIL PROTECTED]> http://wehave.net/ Brampton, Ontario, CanadaLinux 2.4.20 AuthenticAMD -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: 400 000 mails in 12 Hours
On Thursday 27 February 2003 06:10, debian-isp wrote: > I have the task of setting up a mailserver capabel of sending 400 000 mail > in a max time of 12 hours. All mails have an attachment of 1 mb. The system > should be a mailer for a newsletter system. As I made quite a couple of > things with postfix, my concern is the amount and considerations which have > to be made when handling such an amount. Do not personalize the emails then they can be sent to multiple recipients at once. I have used mailman on postfix and majordomo on both postfix and sendmail, no matter the combination you will see that emails to people at the same domain will go out as a single email. With 400,000 emails there will be thousands of people at the same domain for every email that you send. Postfix by default will try to send emails in chunks of 50 recipients before breaking up the remainder into smaller chunks. Your 400,000 deliveries could be reduced to 50,000 lets say (number pulled from thin air with no statistics to back it up). Whatever MTA you use I'm sure you'll need to do some tuning. We had a default postfix install that would choke when it had 1,000 messages in the queue. It would take up to 3 hours to deliver an email that should have been instantly delivered. Now that we've tuned that client's postfix a bit it instantly delivers messages even when there are 2 to 3 thousand messages in the queue, and without noticable load being added to the machine. The above system has a majordomo list of about 4,000 subscribers. During the 10 minutes immediately after the list gets sent the system managed to send 4,784 emails .. that's over 7 emails per second. 549 of those emails were delivered to localhost or other servers on the localnetwork. To summarize this machine was able to send over 7 messages per second to remote email address. Exrapolating that over 12 hours you could have 302,400 emails delivered. This machine is a P3-700, 512MB RAM and single IDE disk, it is not a powerhouse and it is barely taxed (by feel only) during this mailing. The Internet connection is an already saturated and poorly performing 1mb SDSL. The email that I grabbed these statistics from was approximately 7KB. As someone else has pointed out you shouldn't really send large attachments by email. The 1MB becomes typically 30% larger, better to have them click on a link to the document at their leisure. Also many people won't appreciate your mass mailing large files particularly the network admins whose bandwidth, virus scanners and other resources that you are clogging up. With 400,000 emails you will end up with a tonne of undeliverable emails in your queue, you will have to have the bounce handling, queue aging and all such parameters very well set up beforehand. With a good machine and reasonable bandwidth I don't think the task should be that difficult although since I haven't handled such load I can't say for sure. If you're emails are text only I doubt you'll have any problem coming up with a postfix config that blasts them out even faster than you need. -- Fraser Campbell <[EMAIL PROTECTED]> http://wehave.net/ Brampton, Ontario, CanadaLinux 2.4.20 AuthenticAMD
Re: 400 000 mails in 12 Hours
On Thursday 27 February 2003 06:10, debian-isp wrote: > I have the task of setting up a mailserver capabel of sending 400 000 mail > in a max time of 12 hours. All mails have an attachment of 1 mb. The system > should be a mailer for a newsletter system. As I made quite a couple of > things with postfix, my concern is the amount and considerations which have > to be made when handling such an amount. Do not personalize the emails then they can be sent to multiple recipients at once. I have used mailman on postfix and majordomo on both postfix and sendmail, no matter the combination you will see that emails to people at the same domain will go out as a single email. With 400,000 emails there will be thousands of people at the same domain for every email that you send. Postfix by default will try to send emails in chunks of 50 recipients before breaking up the remainder into smaller chunks. Your 400,000 deliveries could be reduced to 50,000 lets say (number pulled from thin air with no statistics to back it up). Whatever MTA you use I'm sure you'll need to do some tuning. We had a default postfix install that would choke when it had 1,000 messages in the queue. It would take up to 3 hours to deliver an email that should have been instantly delivered. Now that we've tuned that client's postfix a bit it instantly delivers messages even when there are 2 to 3 thousand messages in the queue, and without noticable load being added to the machine. The above system has a majordomo list of about 4,000 subscribers. During the 10 minutes immediately after the list gets sent the system managed to send 4,784 emails .. that's over 7 emails per second. 549 of those emails were delivered to localhost or other servers on the localnetwork. To summarize this machine was able to send over 7 messages per second to remote email address. Exrapolating that over 12 hours you could have 302,400 emails delivered. This machine is a P3-700, 512MB RAM and single IDE disk, it is not a powerhouse and it is barely taxed (by feel only) during this mailing. The Internet connection is an already saturated and poorly performing 1mb SDSL. The email that I grabbed these statistics from was approximately 7KB. As someone else has pointed out you shouldn't really send large attachments by email. The 1MB becomes typically 30% larger, better to have them click on a link to the document at their leisure. Also many people won't appreciate your mass mailing large files particularly the network admins whose bandwidth, virus scanners and other resources that you are clogging up. With 400,000 emails you will end up with a tonne of undeliverable emails in your queue, you will have to have the bounce handling, queue aging and all such parameters very well set up beforehand. With a good machine and reasonable bandwidth I don't think the task should be that difficult although since I haven't handled such load I can't say for sure. If you're emails are text only I doubt you'll have any problem coming up with a postfix config that blasts them out even faster than you need. -- Fraser Campbell <[EMAIL PROTECTED]> http://wehave.net/ Brampton, Ontario, CanadaLinux 2.4.20 AuthenticAMD -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: 400 000 mails in 12 Hours
Jean-Francois Dive wrote: That's interesting: 400.000 email in 12 hours = 9 mail a second sent. which means 9Mbytes of data per seconds, assuming that you ahve a pipe of at least 1Mbyte (8Mbit) to each remote end server, which you obviously wont... This means too that you'll need 72Mbit at least of raw bandwith just to sustain the traffic. Now to take more real world values, that's means that the number of email on the fly needs to increase as the remote server bandwith will the bottle neck. Some interesting mail server tests, look at postal test program and results, and i'm sure Russel Coker will comment on this. Just a thought too: as you have only one file to send, ramFS it. I dont know if any of the MTA's support sendfile() but it'd be interesting to see the gain brought by the decrease of context switching (using sendfile) instead of read(fileh), write(socket), which may means more concurent connections. We can say that SMTP has an overhead of about 30%, so you need a 100MBit connection at least. Probably that isn't the problem. If you use the system only to send this one mail you could think about mqueue on ramdisk or so which will increase your performance slightly. All of this without the mail to resend etc..etc.. The consideration: remove the attachement and send it as a link to download (which is most of the time prefered by users especially when they read their email by modem and receive a 1 meg mail), then the figure looks better to me... This however could be against ACK regards -- \\\ ||| /// _\=/_ ( @ @ )(o o) +oOOo-(_)-oOOo--oOOo-(_)-oOOo--+ | Markus Schabel TGM - Die Schule der Technik www.tgm.ac.at | | IT-Service A-1200 Wien, Wexstrasse 19-23 net.tgm.ac.at | | [EMAIL PROTECTED] Tel.: +43(1)33126/316 | | [EMAIL PROTECTED] Fax.: +43(1)33126/154 | | FSF Associate Member #597, Linux User #259595 (counter.li.org) | |oOOoYet Another Spam Trap: oOOo | | ()oOOo[EMAIL PROTECTED] ( ) oOOo | +\ (( )--\ ( -( )-+ \_) ) /\_) ) / (_/ (_/ Computers are like airconditioners: They stop working properly if you open windows.
AW: 400 000 mails in 12 Hours
hi > > Hi all ! > I have the task of setting up a mailserver capabel of sending > 400 000 mail in a max time of 12 hours. > All mails have an attachment of 1 mb. The system should be a > mailer for a newsletter system. As I made quite a couple of > things with postfix, my concern is the amount and > considerations which have to be made when handling such an amount. If it is a unpersonalized mail (e.g. no "Dear Joe Doe" but "Dear Friend ;) and many addresses in the To/Cc/Bcc-field, Exim might be a resonable choice, as it batches deliveries and uses one connection for a bunch of mails to one MX. Mit freundlichen Grüßen / Kind regards Michael Kaiser -- HDI V.a.G. Zentrale Systemtechnik / ZIVP3 Podbielskistr. 396 30659 Hannover Tel.: +49 (511) 645 3491 Fax: +49 (511) 645 4400 E-Mail: [EMAIL PROTECTED]
Re: 400 000 mails in 12 Hours
That's interesting: 400.000 email in 12 hours = 9 mail a second sent. which means 9Mbytes of data per seconds, assuming that you ahve a pipe of at least 1Mbyte (8Mbit) to each remote end server, which you obviously wont... This means too that you'll need 72Mbit at least of raw bandwith just to sustain the traffic. Now to take more real world values, that's means that the number of email on the fly needs to increase as the remote server bandwith will the bottle neck. Some interesting mail server tests, look at postal test program and results, and i'm sure Russel Coker will comment on this. Just a thought too: as you have only one file to send, ramFS it. I dont know if any of the MTA's support sendfile() but it'd be interesting to see the gain brought by the decrease of context switching (using sendfile) instead of read(fileh), write(socket), which may means more concurent connections. All of this without the mail to resend etc..etc.. The consideration: remove the attachement and send it as a link to download (which is most of the time prefered by users especially when they read their email by modem and receive a 1 meg mail), then the figure looks better to me... This however could be against On Thu, 2003-02-27 at 22:10, debian-isp wrote: > Hi all ! > I have the task of setting up a mailserver capabel of sending 400 000 mail in > a max time of 12 hours. > All mails have an attachment of 1 mb. The system should be a mailer for a > newsletter system. As I made quite a couple of things with postfix, my > concern is the amount and considerations which have to be made when handling > such an amount. > > __ > Nik Engel NETWAYS GmbH > Senior Systems Engineer Deutschherrnstr. 47a > Fon.0911/92885-13 D-90429 Nürnberg > Fax.0911/92885-33 > [EMAIL PROTECTED] www.netways.de > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] -- -> Jean-Francois Dive --> [EMAIL PROTECTED] There is no such thing as randomness. Only order of infinite complexity. - Marquis de LaPlace - deterministic Principles -
Re: 400 000 mails in 12 Hours
Jean-Francois Dive wrote: That's interesting: 400.000 email in 12 hours = 9 mail a second sent. which means 9Mbytes of data per seconds, assuming that you ahve a pipe of at least 1Mbyte (8Mbit) to each remote end server, which you obviously wont... This means too that you'll need 72Mbit at least of raw bandwith just to sustain the traffic. Now to take more real world values, that's means that the number of email on the fly needs to increase as the remote server bandwith will the bottle neck. Some interesting mail server tests, look at postal test program and results, and i'm sure Russel Coker will comment on this. Just a thought too: as you have only one file to send, ramFS it. I dont know if any of the MTA's support sendfile() but it'd be interesting to see the gain brought by the decrease of context switching (using sendfile) instead of read(fileh), write(socket), which may means more concurent connections. We can say that SMTP has an overhead of about 30%, so you need a 100MBit connection at least. Probably that isn't the problem. If you use the system only to send this one mail you could think about mqueue on ramdisk or so which will increase your performance slightly. All of this without the mail to resend etc..etc.. The consideration: remove the attachement and send it as a link to download (which is most of the time prefered by users especially when they read their email by modem and receive a 1 meg mail), then the figure looks better to me... This however could be against ACK regards -- \\\ ||| /// _\=/_ ( @ @ )(o o) +oOOo-(_)-oOOo--oOOo-(_)-oOOo--+ | Markus Schabel TGM - Die Schule der Technik www.tgm.ac.at | | IT-Service A-1200 Wien, Wexstrasse 19-23 net.tgm.ac.at | | [EMAIL PROTECTED] Tel.: +43(1)33126/316 | | [EMAIL PROTECTED] Fax.: +43(1)33126/154 | | FSF Associate Member #597, Linux User #259595 (counter.li.org) | |oOOoYet Another Spam Trap: oOOo | | ()oOOo[EMAIL PROTECTED] ( ) oOOo | +\ (( )--\ ( -( )-+ \_) ) /\_) ) / (_/ (_/ Computers are like airconditioners: They stop working properly if you open windows. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
AW: 400 000 mails in 12 Hours
hi > > Hi all ! > I have the task of setting up a mailserver capabel of sending > 400 000 mail in a max time of 12 hours. > All mails have an attachment of 1 mb. The system should be a > mailer for a newsletter system. As I made quite a couple of > things with postfix, my concern is the amount and > considerations which have to be made when handling such an amount. If it is a unpersonalized mail (e.g. no "Dear Joe Doe" but "Dear Friend ;) and many addresses in the To/Cc/Bcc-field, Exim might be a resonable choice, as it batches deliveries and uses one connection for a bunch of mails to one MX. Mit freundlichen Grüßen / Kind regards Michael Kaiser -- HDI V.a.G. Zentrale Systemtechnik / ZIVP3 Podbielskistr. 396 30659 Hannover Tel.: +49 (511) 645 3491 Fax: +49 (511) 645 4400 E-Mail: [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
400 000 mails in 12 Hours
Hi all ! I have the task of setting up a mailserver capabel of sending 400 000 mail in a max time of 12 hours. All mails have an attachment of 1 mb. The system should be a mailer for a newsletter system. As I made quite a couple of things with postfix, my concern is the amount and considerations which have to be made when handling such an amount. __ Nik Engel NETWAYS GmbH Senior Systems Engineer Deutschherrnstr. 47a Fon.0911/92885-13 D-90429 Nürnberg Fax.0911/92885-33 [EMAIL PROTECTED] www.netways.de
Re: 400 000 mails in 12 Hours
That's interesting: 400.000 email in 12 hours = 9 mail a second sent. which means 9Mbytes of data per seconds, assuming that you ahve a pipe of at least 1Mbyte (8Mbit) to each remote end server, which you obviously wont... This means too that you'll need 72Mbit at least of raw bandwith just to sustain the traffic. Now to take more real world values, that's means that the number of email on the fly needs to increase as the remote server bandwith will the bottle neck. Some interesting mail server tests, look at postal test program and results, and i'm sure Russel Coker will comment on this. Just a thought too: as you have only one file to send, ramFS it. I dont know if any of the MTA's support sendfile() but it'd be interesting to see the gain brought by the decrease of context switching (using sendfile) instead of read(fileh), write(socket), which may means more concurent connections. All of this without the mail to resend etc..etc.. The consideration: remove the attachement and send it as a link to download (which is most of the time prefered by users especially when they read their email by modem and receive a 1 meg mail), then the figure looks better to me... This however could be against On Thu, 2003-02-27 at 22:10, debian-isp wrote: > Hi all ! > I have the task of setting up a mailserver capabel of sending 400 000 mail in a max > time of 12 hours. > All mails have an attachment of 1 mb. The system should be a mailer for a newsletter > system. As I made quite a couple of things with postfix, my concern is the amount > and considerations which have to be made when handling such an amount. > > __ > Nik Engel NETWAYS GmbH > Senior Systems Engineer Deutschherrnstr. 47a > Fon.0911/92885-13 D-90429 Nürnberg > Fax.0911/92885-33 > [EMAIL PROTECTED] www.netways.de > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] -- -> Jean-Francois Dive --> [EMAIL PROTECTED] There is no such thing as randomness. Only order of infinite complexity. - Marquis de LaPlace - deterministic Principles - -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Cracking attempt
Hi All, c) i don't know about you, but i wouldn't be inclined to trust the security of a $100 consumer-grade firewall. I agree. Use a PC running SE Linux instead. ;) I would just like to add (to this already long thread but thats what I like about Debian-ISP) that an OpenBSD firewall in a bridging configuration makes for a good setup. This saves on IP addresses and provides added security due to the "stealth" nature of the firewall. One can also run Snort on it. And I might add the OpenBSD packet filter syntax is my favourite as far as writing firewall rules go. Cheers, Fred.
400 000 mails in 12 Hours
Hi all ! I have the task of setting up a mailserver capabel of sending 400 000 mail in a max time of 12 hours. All mails have an attachment of 1 mb. The system should be a mailer for a newsletter system. As I made quite a couple of things with postfix, my concern is the amount and considerations which have to be made when handling such an amount. __ Nik Engel NETWAYS GmbH Senior Systems Engineer Deutschherrnstr. 47a Fon.0911/92885-13 D-90429 Nürnberg Fax.0911/92885-33 [EMAIL PROTECTED] www.netways.de -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Cracking attempt
Hi All, c) i don't know about you, but i wouldn't be inclined to trust the security of a $100 consumer-grade firewall. I agree. Use a PC running SE Linux instead. ;) I would just like to add (to this already long thread but thats what I like about Debian-ISP) that an OpenBSD firewall in a bridging configuration makes for a good setup. This saves on IP addresses and provides added security due to the "stealth" nature of the firewall. One can also run Snort on it. And I might add the OpenBSD packet filter syntax is my favourite as far as writing firewall rules go. Cheers, Fred. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
