Re: reportbug defaults [Re: Bug#367200: ITP: libemail-send-perl -- Simply Sending Email]
Scripsit Don Armstrong [EMAIL PROTECTED] On Wed, 17 May 2006, Henning Makholm wrote: How does sending directly to from reportbug to an ISP's smarthost validate the user's email address better than sending directly from reportbug to a HTTP POST somewhere? I'm talking about an HTTP access method in general; if it were to be done, I'd expect that it validate the users email address before actually forwarding bug reports from the user. Why don't you have the same expectation about SMTP access methods? It is not necessary that there is anywhere any HTML form that refers to the posting URL; only reportbug would need to know it. Except for the fact that anyone can create a page which posts to that url. ... with a big large text box in which a user is supposed to manually format some text that can be parsed properly by the unknown backend script? If anybody _really_ wanted to fake a bug report with a wrong user, it is much simpler to use an off-the-shelf MUA than to try to reverse-engineer the data format used by a the private reportbug HTTP application. -- Henning Makholm Det er trolddom og terror og jeg får en værre ballade når jeg kommer hjem! -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Bug#367200: ITP: libemail-send-perl -- Simply Sending Email
Scripsit Ron Johnson [EMAIL PROTECTED] On Wed, 2006-05-17 at 11:35 +0200, Adam Borowski wrote: Except, this is _doubling_ a question that was already asked somewhere else, ie, a bug. The UNIX way of configuring the mail is setting up a binary that knows how to deliver it as /usr/sbin/sendmail; it doesn't matter whether that binary will do the work itself, run ssh -T foo sendmail, or toss the mail to a smarthost. The Debian way of configuring stuff is asking the admin the relevant questions only once, and keeping the config in a shared place. You're free to file a bug against every Provides: mail-reader app. Serious bugs should certainly be filed against any MUA in Debian whose default configuration is not to use /usr/sbin/sendmail for outgoing mail. I don't know of any such packages in Debian; do you? Personally I use mutt, which has never had the audacity to ask me for external SMTP or IMAP addresses. I have no doubt that it would gladly _accept_ such a specification if I needed to and cared to look up how to configure it, but the _default_ configuration is to use the _default_ mail transport mechanism in Debian, which is how it should be. -- Henning Makholm Punctuation, is? fun! -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Bug#367200: ITP: libemail-send-perl -- Simply Sending Email
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Henning Makholm wrote: Scripsit Ron Johnson [EMAIL PROTECTED] On Wed, 2006-05-17 at 11:35 +0200, Adam Borowski wrote: Except, this is _doubling_ a question that was already asked somewhere else, ie, a bug. The UNIX way of configuring the mail is setting up a binary that knows how to deliver it as /usr/sbin/sendmail; it doesn't matter whether that binary will do the work itself, run ssh -T foo sendmail, or toss the mail to a smarthost. The Debian way of configuring stuff is asking the admin the relevant questions only once, and keeping the config in a shared place. You're free to file a bug against every Provides: mail-reader app. Serious bugs should certainly be filed against any MUA in Debian whose default configuration is not to use /usr/sbin/sendmail for outgoing mail. I don't know of any such packages in Debian; do you? Sylpheed, Evolution Tbird. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.3 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFEbcIoS9HxQb37XmcRArjKAJwIeEmXduzwBv5qHcHS0AexjaKhTQCg3CO7 xofIKSDNq9YY/4/nQqoASYA= =n+NR -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: reportbug defaults [Re: Bug#367200: ITP: libemail-send-perl -- Simply Sending Email]
Ron Johnson [EMAIL PROTECTED] writes: On Wed, 2006-05-17 at 00:24 +0200, Goswin von Brederlow wrote: Ron Johnson [EMAIL PROTECTED] writes: On Tue, 2006-05-16 at 08:44 -0700, Don Armstrong wrote: On Tue, 16 May 2006, Ron Johnson wrote: On the home desktop reportbug uses Python's smtp library to send email directly to the ISP's smtp server. And that's a good thing, because, for a long time, reportbug did not have that feature, and people who don't know how to configure MTAs were not able to send bug reports. reportbug sends mail to wherever it is configured; the default setup should be to send mail to bugs.debian.org, not the ISP's smtp server, since that can't be known in advance. [I don't know if this is the default now, but it should be the default.] bugs.d.o is the *destination*, not the journey. Isn't the default that reprotbug asks on the first run whether to use the local fetchmail / ISPs smpt or send to bugs.d.o now? OK, I'm confused. Isn't the question How does the report gets from the computer to bugs.d.o?? sendmail or smtp library, right? If you run reportbug without arguments it asks you questions on the first run: | Do you have a mail transport agent (MTA) like Exim, Postfix or SSMTP | configured on this computer? [Y|n|q|?]? n | Please enter the name of your SMTP host. Usually it's called something like | mail.example.org or smtp.example.org. Just press ENTER if you don't have | one or don't know. | which results in smtphost bugs.debian.org in the conffile. Maybe the default to the MTA question could be N instead. When I first installed rb, it failed to work, because it wanted to use sendmail, and the only way my PC sent mail to the outside world was using my MUA pointing to smtp.myisp.net (because exim was set up for local delivery only). Later on, I tried again, and found that they had added (or made it more clear in reportbug --configure) the ability to use the user's ISP to transport the email. Yes, that is a new feature. MfG Goswin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Bug#367200: ITP: libemail-send-perl -- Simply Sending Email
On Tue, May 16, 2006 at 07:58:52PM -0500, Ron Johnson wrote: On Tue, 2006-05-16 at 19:21 +0200, Henning Makholm wrote: The point is that they could if the wanted to. And if they did, it would work for _all_ programs, not just particular perl scripts that happen to use some obscure perl module to send mails. T-bird, Evo, Outlook, etc don't figure it out either. They ask the user, What's the name of your ISP's outgoing mail server? Here's the relevant question from reportbug --config Do you have a mail transport agent (MTA) like Exim, Postfix or SSMTP configured on this computer? [y|N|q|?]? Except, this is _doubling_ a question that was already asked somewhere else, ie, a bug. The UNIX way of configuring the mail is setting up a binary that knows how to deliver it as /usr/sbin/sendmail; it doesn't matter whether that binary will do the work itself, run ssh -T foo sendmail, or toss the mail to a smarthost. The Debian way of configuring stuff is asking the admin the relevant questions only once, and keeping the config in a shared place. Having to configure every single program that happens to send out mail adds more work to the user. You also are guaranteed that every such program will ask the questions in a different way, which adds extra confusion. Cheers and schtuff, -- 1KB // Rule #6: If violence wasn't your last resort, // you failed to resort to enough of it. // - The Seven Habits of Highly Effective Pirates -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Bug#367200: ITP: libemail-send-perl -- Simply Sending Email
On Wed, 2006-05-17 at 11:35 +0200, Adam Borowski wrote: On Tue, May 16, 2006 at 07:58:52PM -0500, Ron Johnson wrote: On Tue, 2006-05-16 at 19:21 +0200, Henning Makholm wrote: [snip] Except, this is _doubling_ a question that was already asked somewhere else, ie, a bug. The UNIX way of configuring the mail is setting up a binary that knows how to deliver it as /usr/sbin/sendmail; it doesn't matter whether that binary will do the work itself, run ssh -T foo sendmail, or toss the mail to a smarthost. The Debian way of configuring stuff is asking the admin the relevant questions only once, and keeping the config in a shared place. Having to configure every single program that happens to send out mail adds more work to the user. You also are guaranteed that every such program will ask the questions in a different way, which adds extra confusion. You're free to file a bug against every Provides: mail-reader app. People (well, end-users), though, ever since Netscape 1.0 Composer have been trained to enter their ISP's POP and SMTP server addresses, and I don't think you're going to get the Evo, Sylpheed, T-bird, etc developers to change their code. -- - Ron Johnson, Jr. Jefferson, LA USA They laughed at Columbus, they laughed at Fulton, they laughed at the Wright brothers. But they also laughed at Bozo the Clown. Carl Sagan -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: reportbug defaults [Re: Bug#367200: ITP: libemail-send-perl -- Simply Sending Email]
On Wed, 2006-05-17 at 10:41 +0200, Goswin von Brederlow wrote:
Ron Johnson [EMAIL PROTECTED] writes:
On Wed, 2006-05-17 at 00:24 +0200, Goswin von Brederlow wrote:
Ron Johnson [EMAIL PROTECTED] writes:
On Tue, 2006-05-16 at 08:44 -0700, Don Armstrong wrote:
On Tue, 16 May 2006, Ron Johnson wrote:
On the home desktop reportbug uses Python's smtp library to send
email directly to the ISP's smtp server. And that's a good thing,
because, for a long time, reportbug did not have that feature, and
people who don't know how to configure MTAs were not able to send
bug reports.
reportbug sends mail to wherever it is configured; the default setup
should be to send mail to bugs.debian.org, not the ISP's smtp server,
since that can't be known in advance. [I don't know if this is the
default now, but it should be the default.]
bugs.d.o is the *destination*, not the journey.
Isn't the default that reprotbug asks on the first run whether to use
the local fetchmail / ISPs smpt or send to bugs.d.o now?
OK, I'm confused.
Isn't the question How does the report gets from the computer
to bugs.d.o??
sendmail or smtp library, right?
If you run reportbug without arguments it asks you questions on the
first run:
| Do you have a mail transport agent (MTA) like Exim, Postfix or SSMTP
| configured on this computer? [Y|n|q|?]? n
| Please enter the name of your SMTP host. Usually it's called something like
| mail.example.org or smtp.example.org. Just press ENTER if you don't have
| one or don't know.
|
which results in smtphost bugs.debian.org in the conffile. Maybe the
default to the MTA question could be N instead.
Interesting. b.d.o doesn't seem to be answering on port 25 though.
I ran this tiny python script and it just sits there:
import smtplib
server = smtplib.SMTP('bugs.debian.org')
Traceback (most recent call last):
File stdin, line 1, in ?
File /usr/lib/python2.3/smtplib.py, line 240, in __init__
(code, msg) = self.connect(host, port)
File /usr/lib/python2.3/smtplib.py, line 293, in connect
self.sock.connect(sa)
File string, line 1, in connect
KeyboardInterrupt
When I first installed rb, it failed to work, because it wanted
to use sendmail, and the only way my PC sent mail to the outside
world was using my MUA pointing to smtp.myisp.net (because exim
was set up for local delivery only).
Later on, I tried again, and found that they had added (or made
it more clear in reportbug --configure) the ability to use the
user's ISP to transport the email.
Yes, that is a new feature.
And a darned useful one at that...
--
-
Ron Johnson, Jr.
Jefferson, LA USA
The mass of ignorant Negroes still breed carelessly and
disastrously, so that the increase among Negroes, even more than
the increase among whites, is from that portion of the population
least intelligent and fit, and least able to rear their children
properly.
W.E.B. DuBois (co-founder of the NAACP), 1932
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: reportbug defaults [Re: Bug#367200: ITP: libemail-send-perl -- Simply Sending Email]
Scripsit Don Armstrong [EMAIL PROTECTED] What about modifying it to work through something like an http POST? I'm personally not too terribly interested in implementing an HTTP access method for the BTS, because it makes it more easy for bug submissions to be sent from people who can not be accessed via e-mail. How does sending directly to from reportbug to an ISP's smarthost validate the user's email address better than sending directly from reportbug to a HTTP POST somewhere? It is not necessary that there is anywhere any HTML form that refers to the posting URL; only reportbug would need to know it. -- Henning Makholm This imposes the restriction on any procedure statement that the kind and type of each actual parameter be compatible with the kind and type of the corresponding formal parameter. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: reportbug defaults [Re: Bug#367200: ITP: libemail-send-perl -- Simply Sending Email]
On Wed, 17 May 2006 10:44:19 -0500 Ron Johnson [EMAIL PROTECTED] wrote: Interesting. b.d.o doesn't seem to be answering on port 25 though. Doesn't your provider block port 25? $ telnet bugs.debian.org 25 Trying 140.211.166.43... Connected to bugs.debian.org. Escape character is '^]'. 220 spohr.debian.org ESMTP Exim 4.50 Wed, 17 May 2006 13:45:34 -0700 EHLO me 250-spohr.debian.org Hello nat-10.jups.junix.cz [86.49.49.74] 250-SIZE 62914560 250-PIPELINING 250 HELP QUIT 221 spohr.debian.org closing connection Connection closed by foreign host. -- Michal Čihař | http://cihar.com | http://blog.cihar.com signature.asc Description: PGP signature
Re: Bug#367200: ITP: libemail-send-perl -- Simply Sending Email
On Wed, 17 May 2006 11:35:44 +0200, Adam Borowski [EMAIL PROTECTED] wrote: Except, this is _doubling_ a question that was already asked somewhere else, ie, a bug. The UNIX way of configuring the mail is setting up a binary that knows how to deliver it as /usr/sbin/sendmail; it doesn't matter whether that binary will do the work itself, run ssh -T foo sendmail, or toss the mail to a smarthost. The Debian way of configuring stuff is asking the admin the relevant questions only once, and keeping the config in a shared place. A bug reporting tool, which might be used to report a fatal bug in the default MTA, is a possible exception. Why this tool is written in python, an interpreted language with a run time system the size of Buckingham Palace, The White House and the Kreml combined, is an entirely different story. Greetings Marc -- -- !! No courtesy copies, please !! - Marc Haber |Questions are the | Mailadresse im Header Mannheim, Germany | Beginning of Wisdom | http://www.zugschlus.de/ Nordisch by Nature | Lt. Worf, TNG Rightful Heir | Fon: *49 621 72739834
Re: Bug#367200: ITP: libemail-send-perl -- Simply Sending Email
On 15 May 2006, at 1:13 pm, Henning Makholm wrote: Scripsit Russ Allbery [EMAIL PROTECTED] More generally, Perl modules to send mail rather than using /usr/sbin/sendmail are often useful with web applications (or other applications that need security isolation) that are running in a chroot. To use /usr/sbin/sendmail in the chroot requires setting up a chroot maildrop, and while there are packages to do this, using some module that can speak SMTP is often the path of least resistance. Why not just install some software that can speak SMTP as the chroot's /usr/bin/sendmail? E.g. nullmailer. I've done that on some systems. Works quite well. Tim -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: reportbug defaults [Re: Bug#367200: ITP: libemail-send-perl -- Simply Sending Email]
On Wed, 2006-05-17 at 22:47 +0200, Michal Čihař wrote: On Wed, 17 May 2006 10:44:19 -0500 Ron Johnson [EMAIL PROTECTED] wrote: Interesting. b.d.o doesn't seem to be answering on port 25 though. Doesn't your provider block port 25? $ telnet bugs.debian.org 25 Trying 140.211.166.43... Connected to bugs.debian.org. Escape character is '^]'. 220 spohr.debian.org ESMTP Exim 4.50 Wed, 17 May 2006 13:45:34 -0700 EHLO me 250-spohr.debian.org Hello nat-10.jups.junix.cz [86.49.49.74] 250-SIZE 62914560 250-PIPELINING 250 HELP QUIT 221 spohr.debian.org closing connection Connection closed by foreign host. It blocks *incoming* port 25 traffic for well understood reasons. I never knew, though that it also blocks all *outgoing* smtp traffic except to it's own servers. Maybe to Winbots from emailing files back home? $ telnet bugs.debian.org 25 Trying 140.211.166.43... $ telnet smtp.east.cox.net 25 Trying 68.1.17.4... Connected to smtp.east.cox.net. Escape character is '^]'. 220 eastrmmtao05.cox.net ESMTP server (InterMail vM.6.01.06.01 201-2131-130-101-20060113) ready Wed, 17 May 2006 19:24:46 -0400 EHLO me 250-eastrmmtao05.cox.net 250-HELP 250-XREMOTEQUEUE 250-ETRN 250-PIPELINING 250-DSN 250-8BITMIME 250 SIZE 10485760 HELP 214-This SMTP server is a part of the InterMail E-mail system. For 214- information about InterMail, please see http://www.openwave.com 214- 214- Supported commands: 214- 214-EHLO HELO MAIL RCPT DATA 214-VRFY RSET NOOP QUIT 214- 214- SMTP Extensions supported through EHLO: 214- 214-EXPN HELP SIZE 214- 214- For more information about a listed topic, use HELP topic 214 Please report mail-related problems to Postmaster at this site. QUIT 221 eastrmmtao05.cox.net ESMTP server closing connection Connection closed by foreign host. -- - Ron Johnson, Jr. Jefferson, LA USA marauders in radiation poluted area are not just a regular marauders, they don't steal stuff for themselves. There were cases of radiactive tv sets and other stuff being sold on city second hand markets and then police shot 7 or 8 of them and it helped http://www.angelfire.com/extreme4/kiddofspeed/page4.html
Re: Bug#367200: ITP: libemail-send-perl -- Simply Sending Email
On Wed, 2006-05-17 at 23:28 +0200, Marc Haber wrote: On Wed, 17 May 2006 11:35:44 +0200, Adam Borowski [EMAIL PROTECTED] wrote: [snip] Why this tool is written in python, an interpreted language with a run time system the size of Buckingham Palace, The White House and the Kreml combined, is an entirely different story. PID USER PR NI VIRT RES SHR S %CPU %MEMTIME+ COMMAND 11087 me16 0 155m 77m 18m S 0.0 7.6 0:25.85 evolution-2.6 12651 me15 0 123m 49m 17m S 32.9 4.9 0:12.98 firefox-bin 29560 root 15 0 183m 34m 7748 S 4.7 3.4 51:35.33 Xorg 1104 root 16 0 33252 28m 2268 S 0.0 2.8 0:42.62 spamd 5821 root 16 0 31056 25m 2204 S 0.0 2.6 0:12.51 spamd 2902 root 16 0 26768 21m 2236 S 0.0 2.1 0:07.74 spamd [snip] 12551 me16 0 9132 6624 2512 S 0.0 0.6 0:00.90 reportbug This doesn't look all that huge to me... Maybe I'm just jaded by pigs like Evo, FF, X SpamAssassin. -- - Ron Johnson, Jr. Jefferson, LA USA Supporting World Peace Through Nuclear Pacification -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: reportbug defaults [Re: Bug#367200: ITP: libemail-send-perl -- Simply Sending Email]
On Wed, 17 May 2006, Ron Johnson wrote: It blocks *incoming* port 25 traffic for well understood reasons. Yes, purely commercial reasons. I never knew, though that it also blocks all *outgoing* smtp traffic except to it's own servers. Maybe to Winbots from emailing files back home? Yes, to avoid spam-bots, spam mailers, and smtp-client-enabled viruses. -- One disk to rule them all, One disk to find them. One disk to bring them all and in the darkness grind them. In the Land of Redmond where the shadows lie. -- The Silicon Valley Tarot Henrique Holschuh -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: reportbug defaults [Re: Bug#367200: ITP: libemail-send-perl -- Simply Sending Email]
On Wed, 17 May 2006, Henning Makholm wrote: Scripsit Don Armstrong [EMAIL PROTECTED] What about modifying it to work through something like an http POST? I'm personally not too terribly interested in implementing an HTTP access method for the BTS, because it makes it more easy for bug submissions to be sent from people who can not be accessed via e-mail. How does sending directly to from reportbug to an ISP's smarthost validate the user's email address better than sending directly from reportbug to a HTTP POST somewhere? I'm talking about an HTTP access method in general; if it were to be done, I'd expect that it validate the users email address before actually forwarding bug reports from the user. reportbug is somewhat of a special case because it actually provides useful information along with the bug report; non-reachable submitters are slightly less anoying than in other cases. It is not necessary that there is anywhere any HTML form that refers to the posting URL; only reportbug would need to know it. Except for the fact that anyone can create a page which posts to that url. In any case, I'm not stoping anyone else from implementing it; I've just explained why I'm not going to implement it. Don Armstrong -- Unix, MS-DOS, and Windows NT (also known as the Good, the Bad, and the Ugly). -- Matt Welsh http://www.donarmstrong.com http://rzlab.ucr.edu signature.asc Description: Digital signature
Re: Bug#367200: ITP: libemail-send-perl -- Simply Sending Email
On Tue, May 16, 2006 at 03:16:32AM +0200, Steinar H. Gunderson wrote: verbose and chatty about seemingly normal occasions. In general, I've only seen problems with it; even sendmail seems easier to get to work. With hand-written config file. Written in ed. With or without the Sendmail bible? -- Fun will now commence -- Seven Of Nine, Ashes to Ashes, stardate 53679.4 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Bug#367200: ITP: libemail-send-perl -- Simply Sending Email
Scripsit Steinar H. Gunderson [EMAIL PROTECTED] On Mon, May 15, 2006 at 02:13:46PM +0200, Henning Makholm wrote: Why not just install some software that can speak SMTP as the chroot's /usr/bin/sendmail? E.g. nullmailer. nullmailer is, in general, broken. Then something else. One can easily envisage installing as /usr/bin/sendmail something that reads an email, immediately sends it to a smarthost via SMTP and exits with an error if a problem happened. No daemon, no local spool. That would be accessible to _all_ programs whether they are written in Perl or not. There is a reason for having standardised interfaces. It is that they can be implemented in different ways. -- Henning Makholm En tapper tinsoldat. En dame i spagat. Du er en lykkelig mand ... -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Bug#367200: ITP: libemail-send-perl -- Simply Sending Email
Henning Makholm wrote: Scripsit Steinar H. Gunderson [EMAIL PROTECTED] On Mon, May 15, 2006 at 02:13:46PM +0200, Henning Makholm wrote: Why not just install some software that can speak SMTP as the chroot's /usr/bin/sendmail? E.g. nullmailer. nullmailer is, in general, broken. Then something else. One can easily envisage installing as /usr/bin/sendmail something that reads an email, immediately sends it to a smarthost via SMTP and exits with an error if a problem happened. No daemon, no local spool. That would be accessible to _all_ programs whether they are written in Perl or not. But I still not get it why not to use Email::Send and choose method there? Email::Send is not another sendmail replacement - it's abstract method for using mailers in way you want to use. There is a reason for having standardised interfaces. It is that they can be implemented in different ways. And each could be used with this module. eloy -- [EMAIL PROTECTED] jak to dobrze, że są oceany - bez nich byłoby jeszcze smutniej -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Bug#367200: ITP: libemail-send-perl -- Simply Sending Email
On Tue, 2006-05-16 at 11:04 +0200, Henning Makholm wrote: Scripsit Steinar H. Gunderson [EMAIL PROTECTED] On Mon, May 15, 2006 at 02:13:46PM +0200, Henning Makholm wrote: Why not just install some software that can speak SMTP as the chroot's /usr/bin/sendmail? E.g. nullmailer. nullmailer is, in general, broken. Then something else. One can easily envisage installing as /usr/bin/sendmail something that reads an email, immediately sends it to a smarthost via SMTP and exits with an error if a problem happened. No daemon, no local spool. Not all people have their systems configured that way. I'd venture to say that most home desktops that POP email from their ISP don't have their MTA set up to relay mail. That would be accessible to _all_ programs whether they are written in Perl or not. On the home desktop reportbug uses Python's smtp library to send email directly to the ISP's smtp server. And that's a good thing, because, for a long time, reportbug did not have that feature, and people who don't know how to configure MTAs were not able to send bug reports. There is a reason for having standardised interfaces. It is that they can be implemented in different ways. Yes. The standardized interface is smtp. -- - Ron Johnson, Jr. Jefferson, LA USA Yes, indeed, C isn't 'trendy' enough in the same way gas lighting isn't trendy enough: it's dangerous and it's completely obsolete. http://developers.slashdot.org/comments.pl?sid=91653cid=7893882 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Bug#367200: ITP: libemail-send-perl -- Simply Sending Email
* Ron Johnson [EMAIL PROTECTED] [060516 15:14]: Then something else. One can easily envisage installing as /usr/bin/sendmail something that reads an email, immediately sends it to a smarthost via SMTP and exits with an error if a problem happened. No daemon, no local spool. Not all people have their systems configured that way. I'd venture to say that most home desktops that POP email from their ISP don't have their MTA set up to relay mail. There a trend currently that more and more companies and universities (perhaps also more ISPs in the near future), are blocking outgoing SMTP trafic for everything but their mail server. On the home desktop reportbug uses Python's smtp library to send email directly to the ISP's smtp server. And that's a good thing, because, for a long time, reportbug did not have that feature, and people who don't know how to configure MTAs were not able to send bug reports. Yeah. Its a workaround to a common problem (that the local mta is not that easily configurable). That does not mean that it is better to extend the workaround than to solve the problem. There is a reason for having standardised interfaces. It is that they can be implemented in different ways. Yes. The standardized interface is smtp. The standard *NIX way to send mail is the sendmail symlink, the standard for computers to exchange their mails is SMTP. Thats a difference. Hochachtungsvoll, Bernhard R. Link -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
reportbug defaults [Re: Bug#367200: ITP: libemail-send-perl -- Simply Sending Email]
On Tue, 16 May 2006, Ron Johnson wrote: On the home desktop reportbug uses Python's smtp library to send email directly to the ISP's smtp server. And that's a good thing, because, for a long time, reportbug did not have that feature, and people who don't know how to configure MTAs were not able to send bug reports. reportbug sends mail to wherever it is configured; the default setup should be to send mail to bugs.debian.org, not the ISP's smtp server, since that can't be known in advance. [I don't know if this is the default now, but it should be the default.] Don Armstrong -- I now know how retro SCOs OSes are. Riotous, riotous stuff. How they had the ya-yas to declare Linux an infant OS in need of their IP is beyond me. Upcoming features? PAM. files larger than 2 gigs. NFS over TCP. The 80's called, they want their features back. -- Compactable Dave http://www3.sympatico.ca/dcarpeneto/sco.html http://www.donarmstrong.com http://rzlab.ucr.edu -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: reportbug defaults [Re: Bug#367200: ITP: libemail-send-perl -- Simply Sending Email]
Don Armstrong wrote: reportbug sends mail to wherever it is configured; the default setup should be to send mail to bugs.debian.org, not the ISP's smtp server, since that can't be known in advance. [I don't know if this is the default now, but it should be the default.] Except that many ISPs now block outbound port 25 (at least on consumer-level service), except for what is relayed through their mail servers. I guess it is a bit of a catch-22. What about modifying it to work through something like an http POST? -Roberto -- Roberto C. Sanchez http://familiasanchez.net/~roberto signature.asc Description: OpenPGP digital signature
Re: reportbug defaults [Re: Bug#367200: ITP: libemail-send-perl -- Simply Sending Email]
On May 16, Roberto C. Sanchez [EMAIL PROTECTED] wrote: Except that many ISPs now block outbound port 25 (at least on consumer-level service), except for what is relayed through their mail servers. Agreed. It's not reasonable to expect that port 25 connections from large consumer ISPs will work. reportbug should use port 587 instead (see RFC2476 for details). -- ciao, Marco signature.asc Description: Digital signature
Re: reportbug defaults [Re: Bug#367200: ITP: libemail-send-perl -- Simply Sending Email]
On Tue, 2006-05-16 at 13:20 -0400, Roberto C. Sanchez wrote: Don Armstrong wrote: reportbug sends mail to wherever it is configured; the default setup should be to send mail to bugs.debian.org, not the ISP's smtp server, since that can't be known in advance. [I don't know if this is the default now, but it should be the default.] Except that many ISPs now block outbound port 25 (at least on consumer-level service), except for what is relayed through their mail servers. I guess it is a bit of a catch-22. What about modifying it to work through something like an http POST? That's what popcon does, I think. Remember, though, that reportbug *works*, simply and easily, be- cause it uses the $LANGUAGE smtp library. Why change what works? -- - Ron Johnson, Jr. Jefferson, LA USA You can either have software quality or you can have pointer arithmetic, but you cannot have both at the same time. Bertrand Meyer -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Bug#367200: ITP: libemail-send-perl -- Simply Sending Email
Scripsit Krzysztof Krzyzaniak [EMAIL PROTECTED] That would be accessible to _all_ programs whether they are written in Perl or not. But I still not get it why not to use Email::Send and choose method there? Because one might not be programming in Perl. Email::Send is not another sendmail replacement - it's abstract method for using mailers in way you want to use. /usr/sbin/sendmail _is_ an abstract method for sending mail through the transport configured by the system administrator. -- Henning Makholm ... a specialist in the breakaway oxidation phenomena of certain nuclear reactors. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Bug#367200: ITP: libemail-send-perl -- Simply Sending Email
Scripsit Ron Johnson [EMAIL PROTECTED] On Tue, 2006-05-16 at 11:04 +0200, Henning Makholm wrote: Scripsit Steinar H. Gunderson [EMAIL PROTECTED] On Mon, May 15, 2006 at 02:13:46PM +0200, Henning Makholm wrote: Why not just install some software that can speak SMTP as the chroot's /usr/bin/sendmail? E.g. nullmailer. nullmailer is, in general, broken. Then something else. One can easily envisage installing as /usr/bin/sendmail something that reads an email, immediately sends it to a smarthost via SMTP and exits with an error if a problem happened. No daemon, no local spool. Not all people have their systems configured that way. The point is that they could if the wanted to. And if they did, it would work for _all_ programs, not just particular perl scripts that happen to use some obscure perl module to send mails. On the home desktop reportbug uses Python's smtp library to send email directly to the ISP's smtp server. And that's a good thing, because, for a long time, reportbug did not have that feature, and people who don't know how to configure MTAs were not able to send bug reports. Reportbug may be a special case in that. There is a reason for having standardised interfaces. It is that they can be implemented in different ways. Yes. The standardized interface is smtp. Not according to Debian policy. It is perfectly acceptable to have a way of moving mail to and from the machine that does not use SMTP at all, as long as it provides the standard /usr/sbin/sendmail interface for programs that need to send mail. -- Henning Makholm Science, by its nature, is an uncertain undertaking, and offers plenty of opportunity for failure no matter how you approach it. Yet among the myriad ways to get nowhere, the only fully reliable one is doing and thinking the same as everyone else. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Bug#367200: ITP: libemail-send-perl -- Simply Sending Email
On Tue, 2006-05-16 at 19:18 +0200, Henning Makholm wrote: Scripsit Krzysztof Krzyzaniak [EMAIL PROTECTED] That would be accessible to _all_ programs whether they are written in Perl or not. But I still not get it why not to use Email::Send and choose method there? Because one might not be programming in Perl. So program in C or python or Ruby. Email::Send is not another sendmail replacement - it's abstract method for using mailers in way you want to use. /usr/sbin/sendmail _is_ an abstract method for sending mail through the transport configured by the system administrator. -- - Ron Johnson, Jr. Jefferson, LA USA Power concedes nothing without a demand. It never did and it never will. Frederick Douglass -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Bug#367200: ITP: libemail-send-perl -- Simply Sending Email
On Tue, 2006-05-16 at 19:21 +0200, Henning Makholm wrote: Scripsit Ron Johnson [EMAIL PROTECTED] On Tue, 2006-05-16 at 11:04 +0200, Henning Makholm wrote: Scripsit Steinar H. Gunderson [EMAIL PROTECTED] On Mon, May 15, 2006 at 02:13:46PM +0200, Henning Makholm wrote: [snip] Then something else. One can easily envisage installing as /usr/bin/sendmail something that reads an email, immediately sends it to a smarthost via SMTP and exits with an error if a problem happened. No daemon, no local spool. Not all people have their systems configured that way. The point is that they could if the wanted to. And if they did, it would work for _all_ programs, not just particular perl scripts that happen to use some obscure perl module to send mails. mail-transport-agent postinst config scripts will have to be a lot more clever, then, and explain things like relayhosts to non- sysadmins. -- - Ron Johnson, Jr. Jefferson, LA USA A woman should dress to attract attention. To attract the most attention, a woman should be either nude or wearing something as expensive as getting her nude is going to be. P.J. O'Rourke, satirist -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: reportbug defaults [Re: Bug#367200: ITP: libemail-send-perl -- Simply Sending Email]
On Tue, 2006-05-16 at 08:44 -0700, Don Armstrong wrote: On Tue, 16 May 2006, Ron Johnson wrote: On the home desktop reportbug uses Python's smtp library to send email directly to the ISP's smtp server. And that's a good thing, because, for a long time, reportbug did not have that feature, and people who don't know how to configure MTAs were not able to send bug reports. reportbug sends mail to wherever it is configured; the default setup should be to send mail to bugs.debian.org, not the ISP's smtp server, since that can't be known in advance. [I don't know if this is the default now, but it should be the default.] bugs.d.o is the *destination*, not the journey. -- - Ron Johnson, Jr. Jefferson, LA USA The First Amendment protects speech from being censored by the government; it does not regulate what private parties (such as most employers) do. http://www.eff.org/Privacy/Anonymity/blog-anonymously.php -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Bug#367200: ITP: libemail-send-perl -- Simply Sending Email
Scripsit Ron Johnson [EMAIL PROTECTED] On Tue, 2006-05-16 at 19:21 +0200, Henning Makholm wrote: The point is that they could if the wanted to. And if they did, it would work for _all_ programs, not just particular perl scripts that happen to use some obscure perl module to send mails. mail-transport-agent postinst config scripts will have to be a lot more clever, then, and explain things like relayhosts to non- sysadmins. Are you implying that the perl library in question is able to figure out these things without guidance from the sysadmin? In that case the AI code that does it ought to be appropriated and worked into our MTA postinst scripts. -- Henning Makholm Monarki, er ikke noget materielt ... Borger! -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: reportbug defaults [Re: Bug#367200: ITP: libemail-send-perl -- Simply Sending Email]
Ron Johnson [EMAIL PROTECTED] writes: On Tue, 2006-05-16 at 08:44 -0700, Don Armstrong wrote: On Tue, 16 May 2006, Ron Johnson wrote: On the home desktop reportbug uses Python's smtp library to send email directly to the ISP's smtp server. And that's a good thing, because, for a long time, reportbug did not have that feature, and people who don't know how to configure MTAs were not able to send bug reports. reportbug sends mail to wherever it is configured; the default setup should be to send mail to bugs.debian.org, not the ISP's smtp server, since that can't be known in advance. [I don't know if this is the default now, but it should be the default.] bugs.d.o is the *destination*, not the journey. Isn't the default that reprotbug asks on the first run whether to use the local fetchmail / ISPs smpt or send to bugs.d.o now? What do you want? Skip the question and default to bugs.d.o? MfG Goswin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: reportbug defaults [Re: Bug#367200: ITP: libemail-send-perl -- Simply Sending Email]
On Tue, 16 May 2006, Roberto C. Sanchez wrote: Don Armstrong wrote: reportbug sends mail to wherever it is configured; the default setup should be to send mail to bugs.debian.org, not the ISP's smtp server, since that can't be known in advance. [I don't know if this is the default now, but it should be the default.] Except that many ISPs now block outbound port 25 (at least on consumer-level service), except for what is relayed through their mail servers. There's not much that can be done about that besides using 587 or similar. In such a case the user should be prompted for an smtp server which actually works instead of the default. [Indeed, that's what should happen when any smtp server is unreachable.] bugs.debian.org is the only sensible default. Anything else requires user configuration. What about modifying it to work through something like an http POST? I'm personally not too terribly interested in implementing an HTTP access method for the BTS, because it makes it more easy for bug submissions to be sent from people who can not be accessed via e-mail. I don't have a problem with someone else implementing such a service that actually verifies the e-mail address of people, though. [You don't need anything from me at all to do that.] Don Armstrong -- Il semble que la perfection soit atteinte non quand il n'y a plus rien a ajouter, mais quand il n'y a plus rien a retrancher. (Perfection is apparently not achieved when nothing more can be added, but when nothing else can be removed.) -- Antoine de Saint-Exupe'ry, Terres des Hommes http://www.donarmstrong.com http://rzlab.ucr.edu -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: reportbug defaults [Re: Bug#367200: ITP: libemail-send-perl -- Simply Sending Email]
On Wed, 2006-05-17 at 00:24 +0200, Goswin von Brederlow wrote: Ron Johnson [EMAIL PROTECTED] writes: On Tue, 2006-05-16 at 08:44 -0700, Don Armstrong wrote: On Tue, 16 May 2006, Ron Johnson wrote: On the home desktop reportbug uses Python's smtp library to send email directly to the ISP's smtp server. And that's a good thing, because, for a long time, reportbug did not have that feature, and people who don't know how to configure MTAs were not able to send bug reports. reportbug sends mail to wherever it is configured; the default setup should be to send mail to bugs.debian.org, not the ISP's smtp server, since that can't be known in advance. [I don't know if this is the default now, but it should be the default.] bugs.d.o is the *destination*, not the journey. Isn't the default that reprotbug asks on the first run whether to use the local fetchmail / ISPs smpt or send to bugs.d.o now? OK, I'm confused. Isn't the question How does the report gets from the computer to bugs.d.o?? sendmail or smtp library, right? When I first installed rb, it failed to work, because it wanted to use sendmail, and the only way my PC sent mail to the outside world was using my MUA pointing to smtp.myisp.net (because exim was set up for local delivery only). Later on, I tried again, and found that they had added (or made it more clear in reportbug --configure) the ability to use the user's ISP to transport the email. What do you want? Skip the question and default to bugs.d.o? -- - Ron Johnson, Jr. Jefferson, LA USA Peace has its victories no less than war, but it doesn't have as many monuments to unveil. Kin Hubbard -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Bug#367200: ITP: libemail-send-perl -- Simply Sending Email
On Tue, 2006-05-16 at 22:39 +0200, Henning Makholm wrote: Scripsit Ron Johnson [EMAIL PROTECTED] On Tue, 2006-05-16 at 19:21 +0200, Henning Makholm wrote: The point is that they could if the wanted to. And if they did, it would work for _all_ programs, not just particular perl scripts that happen to use some obscure perl module to send mails. mail-transport-agent postinst config scripts will have to be a lot more clever, then, and explain things like relayhosts to non- sysadmins. Are you implying that the perl library in question is able to figure out these things without guidance from the sysadmin? In that case the AI code that does it ought to be appropriated and worked into our MTA postinst scripts. Of course not. T-bird, Evo, Outlook, etc don't figure it out either. They ask the user, What's the name of your ISP's outgoing mail server? Here's the relevant question from reportbug --config Do you have a mail transport agent (MTA) like Exim, Postfix or SSMTP configured on this computer? [y|N|q|?]? If you take the default N, it asks you: Please enter the name of your SMTP host. Usually it's called something like mail.example.org or smtp.example.org. Just press ENTER if you don't have one or don't know. -- - Ron Johnson, Jr. Jefferson, LA USA Your opinions are bound to affect the stories you choose to broadcast [on TV/radio]. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Bug#367200: ITP: libemail-send-perl -- Simply Sending Email
Milan P. Stanic wrote: On Sun, May 14, 2006 at 01:20:20PM +0200, Krzysztof Krzyzaniak (eloy) wrote: Email::Send provides a very simple, very clean, very specific interface to multiple Email mailers. The goal if this software is to be small ^ and simple, easy to use, and easy to extend. Isn't the term Email mailers vague a little? Right. Fixed. eloy -- [EMAIL PROTECTED] jak to dobrze, że są oceany - bez nich byłoby jeszcze smutniej -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Bug#367200: ITP: libemail-send-perl -- Simply Sending Email
Scripsit Russ Allbery [EMAIL PROTECTED] More generally, Perl modules to send mail rather than using /usr/sbin/sendmail are often useful with web applications (or other applications that need security isolation) that are running in a chroot. To use /usr/sbin/sendmail in the chroot requires setting up a chroot maildrop, and while there are packages to do this, using some module that can speak SMTP is often the path of least resistance. Why not just install some software that can speak SMTP as the chroot's /usr/bin/sendmail? E.g. nullmailer. -- Henning Makholm Wir kommen nun ans Ziel unserer Ausführungen. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Bug#367200: ITP: libemail-send-perl -- Simply Sending Email
Henning Makholm [EMAIL PROTECTED] writes: Scripsit Russ Allbery [EMAIL PROTECTED] More generally, Perl modules to send mail rather than using /usr/sbin/sendmail are often useful with web applications (or other applications that need security isolation) that are running in a chroot. To use /usr/sbin/sendmail in the chroot requires setting up a chroot maildrop, and while there are packages to do this, using some module that can speak SMTP is often the path of least resistance. Why not just install some software that can speak SMTP as the chroot's /usr/bin/sendmail? E.g. nullmailer. nullmailer has to run as a daemon so far as I know (it at least does in the default Debian configuration) and still uses a local maildrop. It therefore requires explicit setup and configuration outside of the context of the CGI script or other application. A Perl module to send mail via SMTP is entirely self-contained and doesn't rely on any system service being installed. -- Russ Allbery ([EMAIL PROTECTED]) http://www.eyrie.org/~eagle/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Bug#367200: ITP: libemail-send-perl -- Simply Sending Email
On Mon, May 15, 2006 at 02:13:46PM +0200, Henning Makholm wrote: Why not just install some software that can speak SMTP as the chroot's /usr/bin/sendmail? E.g. nullmailer. nullmailer is, in general, broken. For one, it doesn't seem to understand errors at the other side; 5xx is simply interpreted as hey, I'll try again next minute. (Nice when the error is because the mail was over 50MB.) Second, the logging is completely obscure; anything fatal doesn't seem to be logged at all, but it's excesively verbose and chatty about seemingly normal occasions. In general, I've only seen problems with it; even sendmail seems easier to get to work. With hand-written config file. Written in ed. /* Steinar */ -- Homepage: http://www.sesse.net/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Bug#367200: ITP: libemail-send-perl -- Simply Sending Email
* Steinar H. Gunderson wrote: On Mon, May 15, 2006 at 02:13:46PM +0200, Henning Makholm wrote: Why not just install some software that can speak SMTP as the chroot's /usr/bin/sendmail? E.g. nullmailer. nullmailer is, in general, broken. For one, it doesn't seem to understand errors at the other side; 5xx is simply interpreted as hey, I'll try again next minute. Known bug. Unfortunately, upstream isn't really responsive. (Nice when the error is because the mail was over 50MB.) There are better ways to transfer big files than SMTP. Second, the logging is completely obscure; anything fatal doesn't seem to be logged at all, but it's excesively verbose and chatty about seemingly normal occasions. This one is new to me. Please write a bugreport. In general, I've only seen problems with it; even sendmail seems easier to get to work. With hand-written config file. Written in ed. Blah. Norbert -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Bug#367200: ITP: libemail-send-perl -- Simply Sending Email
* Norbert Tretkowski: (Nice when the error is because the mail was over 50MB.) There are better ways to transfer big files than SMTP. That's presumably why the receving side rejected the message. Apparently, nullmailer cannot deal gracefully with that situation. 8-( -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#367200: ITP: libemail-send-perl -- Simply Sending Email
Package: wnpp Severity: wishlist Owner: Krzysztof Krzyzaniak (eloy) [EMAIL PROTECTED] * Package name: libemail-send-perl Version : 2.0.5 Upstream Author : Casey West, [EMAIL PROTECTED] * URL : http://mirrors.kernel.org/cpan/modules/by-module/Email/Email-Send-2.05.tar.gz * License : Perl: Artistic/GPL Programming Lang: Perl Description : Simply Sending Email Email::Send provides a very simple, very clean, very specific interface to multiple Email mailers. The goal if this software is to be small and simple, easy to use, and easy to extend. -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable'), (500, 'stable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.16-1-686 Locale: LANG=pl_PL, LC_CTYPE=pl_PL (charmap=ISO-8859-2) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Bug#367200: ITP: libemail-send-perl -- Simply Sending Email
Scripsit Krzysztof Krzyzaniak (eloy) [EMAIL PROTECTED] Email::Send provides a very simple, very clean, very specific interface to multiple Email mailers. The goal if this software is to be small and simple, easy to use, and easy to extend. What's wrong with the legacy /usr/sbin/sendmail interface, mandated by policy, LSB, etc? -- Henning Makholm We will discuss your youth another time. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Bug#367200: ITP: libemail-send-perl -- Simply Sending Email
On Sun, May 14, 2006 at 01:20:20PM +0200, Krzysztof Krzyzaniak (eloy) wrote: Email::Send provides a very simple, very clean, very specific interface to multiple Email mailers. The goal if this software is to be small ^ and simple, easy to use, and easy to extend. Isn't the term Email mailers vague a little? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Bug#367200: ITP: libemail-send-perl -- Simply Sending Email
Henning Makholm wrote: Scripsit Krzysztof Krzyzaniak (eloy) [EMAIL PROTECTED] Email::Send provides a very simple, very clean, very specific interface to multiple Email mailers. The goal if this software is to be small and simple, easy to use, and easy to extend. What's wrong with the legacy /usr/sbin/sendmail interface, mandated by policy, LSB, etc? Nothing wrong probably, but if you can have it better so why not? Second it's used as dependency for other modules for example Catalyst::Plugin::Email which I need. So If I have packaged Email::Send already why not to share with others? eloy -- [EMAIL PROTECTED] jak to dobrze, że są oceany - bez nich byłoby jeszcze smutniej -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Bug#367200: ITP: libemail-send-perl -- Simply Sending Email
Henning Makholm [EMAIL PROTECTED] writes: Scripsit Krzysztof Krzyzaniak (eloy) [EMAIL PROTECTED] Email::Send provides a very simple, very clean, very specific interface to multiple Email mailers. The goal if this software is to be small and simple, easy to use, and easy to extend. What's wrong with the legacy /usr/sbin/sendmail interface, mandated by policy, LSB, etc? Email::Send supports a pluggable interface layer and can therefore do some interesting things, like plugging in a module that stores mail into files for debugging, or posting the message via NNTP rather than mailing it. More generally, Perl modules to send mail rather than using /usr/sbin/sendmail are often useful with web applications (or other applications that need security isolation) that are running in a chroot. To use /usr/sbin/sendmail in the chroot requires setting up a chroot maildrop, and while there are packages to do this, using some module that can speak SMTP is often the path of least resistance. -- Russ Allbery ([EMAIL PROTECTED]) http://www.eyrie.org/~eagle/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
