Re: Automated message processing
Hi, * Kyle Wheeler wrote: On Thursday, September 4 at 10:58 PM, quoth Peter Davis: ~i ... or: grep '^Message-ID: ' * Yes, but both of those require searching through a potentially large number of messages to find the matching id. If you use hcache, the ~i pattern match will be just a hash-table lookup, which should be constant time no matter the number of messages. Mutt internally maintains a hash table with message-ids for threading but for ~i this isn't considered. The reason is that ~i takes a regex as argument, and with hash tables you can't do range or partial matches or even regex matches, only exact string matches. Mutt knows about some headers per message one of them being the message-id which is used for ~i. hcache doesn't play a role since mutt always has that header, i.e. ~i doesn't require a disk hit per message. If you want to speed it up and your mutt is recent enough, you can use string instead of regex search if that is sufficient. I.e. =i [EMAIL PROTECTED] should be way faster for a large folder compared to ~i [EMAIL PROTECTED] Regards, Rocco
Re: Gnupg2 vs gnupg
On Wed, Sep 03, 2008 at 10:03:46PM +0200, Stefan Wimmer wrote: > * [EMAIL PROTECTED] <[EMAIL PROTECTED]> [2008-09-03 21:47]: > > On gentoo at least, gnupg2 gets real pissy when there is no X > > environment. I don't use it all that much, but memory says that > > clearing DISPLAY and trying numerous other tricks to force a command > > line passphrase input didn't work, that it always popped up a display > > window to prompt for it. I don't remember now what happened when > > there was no display, only that I was frustrated and never did get it > > to work without a display, or maybe that I could not force it to not > > use the display if it could find one. > > Hmm - last year I would have confirmed your description of the situation of > gnupg2 on Gentoo but I gave it another try this summer and it was very easy > to > get it working with the ncurses interface :) > > Just set > > GPG_TTY=`tty` > > in your SHELL environment and use > > pinentry-program /usr/bin/pinentry-curses > > in your ~/.gnupg/gpg-agent.conf That did it. Ncurses is better than X, but I'd still rather a plain terminal version -- print it and read the response without echo. -- ... _._. ._ ._. . _._. ._. ___ .__ ._. . .__. ._ .. ._. Felix Finch: scarecrow repairman & rocket surgeon / [EMAIL PROTECTED] GPG = E987 4493 C860 246C 3B1E 6477 7838 76E9 182E 8151 ITAR license #4933 I've found a solution to Fermat's Last Theorem but I see I've run out of room o
Re: search backward
On Thu, 04 Sep 2008, Gary Johnson wrote: > > / search-reversesearch backwards for a regular expression Thank you, I can find it now. BTW, can the output of ? screen be redirected to a file or system clipboard? -- regards, GPG key 1024D/4434BAB3 2008-08-24 gpg --keyserver subkeys.pgp.net --recv-keys 4434BAB3
Re: Configuring sendmail on Mac OS X (Leopard)?
Cameron Simpson wrote: On 04Sep2008 23:03, Sahil Tandon <[EMAIL PROTECTED]> wrote: | Peter Davis <[EMAIL PROTECTED]> wrote: | > I have two Macs, one at work and one at home, running OS X 10.5. I'm | > using nearly identical .muttrc files on both, using sendmail to send | > outgoing messages. On my work Mac, this all behaves just fine. On | > the home Mac, Mutt says "Message sent." but the message never arrives. | > Both are running Mutt 1.4.2.3i. | | How do you set the 'sendmail' variable in .muttrc? set sendmail = "/usr/sbin/sendmail"| | > Is there some way to trace the outgoing message to see where it's | > failing? Any tips on configuring sendmail on the Mac? I didn't have | > to do anything on the office Mac ... it just works. | | The binary is called sendmail, but that is just the Postfix to Sendmail | compatibility interface. On OS X, Postfix logs to /var/log/mail.log -- | parse that file for clues, assuming mutt is (via the sendmail command) | passing mails to Postfix. Thanks. I looked here, and see messages like this: Sep 4 22:02:31 PFD-Studio-Mac postfix/smtp[88615]: C037B4D62348: to=<[EMAIL PROTECTED]>, relay=none, delay=30, delays=0.2/0.05/30/0, dsn=4.4.1, status=deferred (connect to mailwash17.pair.com[66.39.2.17]: Operation timed ou t) But that doesn't tell me much. And the "mailq" command should recite the queue of unsent messages, if any. Ah, this could be revealing. I get: postqueue: fatal: Queue report unavailable - mail system is down I don't know how to troubleshoot or start the mailsystem, but that gives me something to Google. Thanks! -pd -- Peter Davis Funny stuff - http://www.pfdstudio.com Ideas Great and Dumb - http://www.ideasgreatanddumb.com Art/Tech Fusion - http://www.arttechfusion.com The Tech Curmudgeon - http://www.techcurmudgeon.com
Re: Automated message processing
Kyle Wheeler wrote: I figured that since I'm using MH format anyway, I should be able to include a path directly to the message file itself ... except that Mutt doesn't seem to give me a way to pass that information when I pipe a message to a script. Of course not - it's a *pipe*. :) In the example: cat foo | somecommand somecommand has no way of ever discovering what or where foo is. That's a feature, not a flaw. I understand that. I guess what I should have said was "Mutt doesn't give me any way to pass a pointer to the message file. All I can do is pipe the contents of the message." Thanks! -pd -- Peter Davis Funny stuff - http://www.pfdstudio.com Ideas Great and Dumb - http://www.ideasgreatanddumb.com Art/Tech Fusion - http://www.arttechfusion.com The Tech Curmudgeon - http://www.techcurmudgeon.com
Re: Configuring sendmail on Mac OS X (Leopard)?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Friday, September 5 at 07:09 AM, quoth Peter Davis: > Thanks. I looked here, and see messages like this: > > Sep 4 22:02:31 PFD-Studio-Mac postfix/smtp[88615]: C037B4D62348: > to=<[EMAIL PROTECTED]>, relay=none, delay=30, > delays=0.2/0.05/30/0, dsn=4.4.1, status=deferred (connect to > mailwash17.pair.com[66.39.2.17]: Operation timed ou > t) > > But that doesn't tell me much. That tells you a lot, actually. It says that the connection to the remote mailserver could not be made. That could be for a lot of reasons, but the most likely is that your home ISP doesn't let ordinary folks like yourself send mail outside their network without funnelling it through their mail server (this is a common anti-spam technique). Try doing this: telnet mailwash17.pair.com 25 If that can't connect, then you have discovered the problem. If it does connect and you get the pair.com greeting, then the problem must be with postfix. >> And the "mailq" command should recite the queue of unsent messages, >> if any. >> > Ah, this could be revealing. I get: > > postqueue: fatal: Queue report unavailable - mail system is down > > I don't know how to troubleshoot or start the mailsystem, but that gives > me something to Google. I think the default in 10.5 is to set up postfix in a queue-less mode, so that there is no actively running "mail system", it just starts up whenever you try to send an email and shuts down immediately thereafter. ~Kyle - -- Three things in human life are important. The first is to be kind. The second is to be kind. And the third is to be kind. -- Henry James -BEGIN PGP SIGNATURE- Comment: Thank you for using encryption! iEYEARECAAYFAkjBJQkACgkQBkIOoMqOI17zRgCeIDqdcdpKFWVEF9E2JLmEM/Am mtMAn2mingj6pgiE4dOagRBxK43O1QCZ =MVeJ -END PGP SIGNATURE-
Basic questions from newbie
I apologize for asking this. I.ve used pine for 10+ years and probably don't understand the mutt terminology enough to find the answer in the documentation. How do I export emails to text files in the current or another dir ? I mean the message headers and body as plain text, not attachments. `Export' is pine terminology for this. Is there a different word in mutt? Many thanks. Chas _ Get all your favourite content with the slick new MSN Toolbar - FREE http://clk.atdmt.com/UKM/go/111354027/direct/01/
Re: Basic questions from newbie
On Fri, Sep 05, 2008 at 02:42:17PM +, Charles Howard wrote: > How do I export emails to text files in the current or another dir ? I mean > the message headers and body as plain text, not attachments. > > `Export' is pine terminology for this. Is there a different word in mutt? Never used Pine, any my mutt experience is far from complete, but you probably want the 'v' key -- it shows every mime section, including the main body, and you can save them wherever you want. -- ... _._. ._ ._. . _._. ._. ___ .__ ._. . .__. ._ .. ._. Felix Finch: scarecrow repairman & rocket surgeon / [EMAIL PROTECTED] GPG = E987 4493 C860 246C 3B1E 6477 7838 76E9 182E 8151 ITAR license #4933 I've found a solution to Fermat's Last Theorem but I see I've run out of room o
Re: Basic questions from newbie
Terrific! Thank you very much. I like the cat method best. I should have thought of just using the editor. It's getting started that's the hardest. Chas > Date: Fri, 5 Sep 2008 09:54:09 -0500 > From: [EMAIL PROTECTED] > To: mutt-users@mutt.org > Subject: Re: Basic questions from newbie > > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > On Friday, September 5 at 02:42 PM, quoth Charles Howard: >> How do I export emails to text files in the current or another dir ? >> I mean the message headers and body as plain text, not attachments. >> >> `Export' is pine terminology for this. Is there a different word in mutt? > > I don't know that there's an explicit word for doing this, but the way > I would do it is via (usually bound to the | key). With > that binding, here's what I'd type: > > |cat> foo.txt > > Exactly what ends up in foo.txt depends on the $pipe_decode setting. > > Another way to do it is to set $mbox_type to "mbox" and then save (or > copy) the message to foo.txt (when mutt asks, tell it that yes you > want to create the mailbox). Granted, it'll technically be in mbox > format, but for a single message, that's essentially exactly what you > want. > > Another way to do it is to use the message editor (usually bound to > the e key). Once the message is loaded up in your favorite text > editor, you can save it wherever you like. > > I guarantee there are several other ways to do it. But there's no > direct "save this message as a txt file" command, if that's what > you're after; though you can create one with a macro if you need it. > > Does that answer your question? > > ~Kyle > - -- > To sin by silence when they should protest makes cowards of men. > -- Abraham Lincoln > -BEGIN PGP SIGNATURE- > Comment: Thank you for using encryption! > > iEYEARECAAYFAkjBSBEACgkQBkIOoMqOI17mXACgoVhdFZ2gCZTY3OSWrN6suzBT > DJ8AnjgRpG3+jBi7A7VjYjbfWxmgQ/9+ > =9rAE > -END PGP SIGNATURE- _ Discover Bird's Eye View now with Multimap from Live Search http://clk.atdmt.com/UKM/go/111354026/direct/01/
Re: Basic questions from newbie
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Friday, September 5 at 02:42 PM, quoth Charles Howard: > How do I export emails to text files in the current or another dir ? > I mean the message headers and body as plain text, not attachments. > > `Export' is pine terminology for this. Is there a different word in mutt? I don't know that there's an explicit word for doing this, but the way I would do it is via (usually bound to the | key). With that binding, here's what I'd type: |cat > foo.txt Exactly what ends up in foo.txt depends on the $pipe_decode setting. Another way to do it is to set $mbox_type to "mbox" and then save (or copy) the message to foo.txt (when mutt asks, tell it that yes you want to create the mailbox). Granted, it'll technically be in mbox format, but for a single message, that's essentially exactly what you want. Another way to do it is to use the message editor (usually bound to the e key). Once the message is loaded up in your favorite text editor, you can save it wherever you like. I guarantee there are several other ways to do it. But there's no direct "save this message as a txt file" command, if that's what you're after; though you can create one with a macro if you need it. Does that answer your question? ~Kyle - -- To sin by silence when they should protest makes cowards of men. -- Abraham Lincoln -BEGIN PGP SIGNATURE- Comment: Thank you for using encryption! iEYEARECAAYFAkjBSBEACgkQBkIOoMqOI17mXACgoVhdFZ2gCZTY3OSWrN6suzBT DJ8AnjgRpG3+jBi7A7VjYjbfWxmgQ/9+ =9rAE -END PGP SIGNATURE-
Re: Basic questions from newbie
On 2008-09-05, Charles Howard <[EMAIL PROTECTED]> wrote: > > From: [EMAIL PROTECTED] > > On Friday, September 5 at 02:42 PM, quoth Charles Howard: > >> How do I export emails to text files in the current or another dir ? > >> I mean the message headers and body as plain text, not attachments. > >> > >> `Export' is pine terminology for this. Is there a different word in mutt? > > > > I don't know that there's an explicit word for doing this, but the way > > I would do it is via (usually bound to the | key). With > > that binding, here's what I'd type: > > > > |cat> foo.txt > > > > Exactly what ends up in foo.txt depends on the $pipe_decode setting. > > > > Another way to do it is to set $mbox_type to "mbox" and then save (or > > copy) the message to foo.txt (when mutt asks, tell it that yes you > > want to create the mailbox). Granted, it'll technically be in mbox > > format, but for a single message, that's essentially exactly what you > > want. > > > > Another way to do it is to use the message editor (usually bound to > > the e key). Once the message is loaded up in your favorite text > > editor, you can save it wherever you like. > > > > I guarantee there are several other ways to do it. But there's no > > direct "save this message as a txt file" command, if that's what > > you're after; though you can create one with a macro if you need it. I must be missing something. How is either the or command not a "save this message as a text file" command? > Terrific! Thank you very much. > > I like the cat method best. I should have thought of just using the editor. The command, bound to C by default, should be the same as piping the message to "cat > foo.txt". The command, bound to C by default, should be the same a piping with 'pipe_decode' set. Regards, Gary
Re: Basic questions from newbie
On 2008-09-05, Gary Johnson <[EMAIL PROTECTED]> wrote: > I must be missing something. How is either the or > command not a "save this message as a text file" > command? It is different if the file already exists and is not-empty. >> I like the cat method best. I should have thought of just using the editor. > > The command, bound to C by default, should be the > same as piping the message to "cat > foo.txt". The > command, bound to C by default, should be the same a piping > with 'pipe_decode' set. I won't contest whether they _should_ be the same, but I will claim they're not the same. The command appends the message to the file assuming it's an mbox format mail folder. "| cat >foo.txt" just saves writes the message to file. If the file exists and is not empty, th two operations are not the same. -- Grant Edwards grante Yow! !! I am having fun!!! at visi.com
Re: Basic questions from newbie
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Friday, September 5 at 08:34 AM, quoth Gary Johnson: >>> Another way to do it is to set $mbox_type to "mbox" and then save >>> (or copy) the message to foo.txt (when mutt asks, tell it that yes >>> you want to create the mailbox). Granted, it'll technically be in >>> mbox format, but for a single message, that's essentially exactly >>> what you want. > I must be missing something. How is either the or > command not a "save this message as a text file" > command? It's not *exactly* that because it expects to save to a mailbox. If $mbox_type is set to "maildir", for example, and you try to use or (or any of the other variants) to save the message to "foo.txt", it will instead create a maildir mailbox called foo.txt and put the email in that mailbox. Yes, inside foo.txt/new/ there will be a text file with that message, but that's pretty roundabout. In any case, as you can see from the part of my message that I quoted, I mentioned that possibility (albeit more succinctly). ~Kyle - -- Blessed are they who can laugh at themselves for they shall never cease to be amused. -- Unknown -BEGIN PGP SIGNATURE- Comment: Thank you for using encryption! iEYEARECAAYFAkjBXNUACgkQBkIOoMqOI14bRgCg2Z9ivdvBwss/J4gmKVZchWqQ 3p0Ani+8lX1XeDAxutZ3uEUHfCceBW+n =LVQ+ -END PGP SIGNATURE-
Re: Basic questions from newbie
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Friday, September 5 at 03:43 PM, quoth Grant Edwards: >If the file exists and is not empty, th two operations are not >the same. It also depends on the value of $mbox_type. ~Kyle - -- May your glass be ever full. May the roof over your head be always strong. May you be in heaven half an hour before the devil knows you're dead. -- Old Irish Toast -BEGIN PGP SIGNATURE- Comment: Thank you for using encryption! iEYEARECAAYFAkjBXQgACgkQBkIOoMqOI16DRgCfTLD57dqWYaHCp6YI8Nwsshtm 3bwAn0PsdOVtMtGM4TJtg4G2HZCcvl56 =dM0k -END PGP SIGNATURE-
Re: Configuring sendmail on Mac OS X (Leopard)?
On Fri, 05 Sep 2008, Kyle Wheeler wrote: > On Friday, September 5 at 07:09 AM, quoth Peter Davis: > > Thanks. I looked here, and see messages like this: > > > > Sep 4 22:02:31 PFD-Studio-Mac postfix/smtp[88615]: C037B4D62348: > > to=<[EMAIL PROTECTED]>, relay=none, delay=30, > > delays=0.2/0.05/30/0, dsn=4.4.1, status=deferred (connect to > > mailwash17.pair.com[66.39.2.17]: Operation timed ou > > t) > > > > But that doesn't tell me much. > > That tells you a lot, actually. It says that the connection to the > remote mailserver could not be made. That could be for a lot of > reasons, but the most likely is that your home ISP doesn't let > ordinary folks like yourself send mail outside their network without > funnelling it through their mail server (this is a common anti-spam > technique). Try doing this: > > telnet mailwash17.pair.com 25 > > If that can't connect, then you have discovered the problem. If it > does connect and you get the pair.com greeting, then the problem must > be with postfix. The server at Pair is relay.pair.com. It authorizes SMTP for 90 minutes after a POP3 or IMAP connection. See: http://www.pair.com/support/knowledge_base/e-mail/smtp_service_at_pair_networks.html JL -- Jorge Luis <[EMAIL PROTECTED]> In the workers' paradise, everyone will have their own dotted quad.
Re: Configuring sendmail on Mac OS X (Leopard)?
Jorge Luis wrote: The server at Pair is relay.pair.com. It authorizes SMTP for 90 minutes after a POP3 or IMAP connection. See: http://www.pair.com/support/knowledge_base/e-mail/smtp_service_at_pair_networks.html Thanks. Anyone know how I configure Postfix on Mac OS X to use that server? Thanks! -pd -- Peter Davis Funny stuff - http://www.pfdstudio.com Ideas Great and Dumb - http://www.ideasgreatanddumb.com The Tech Curmudgeon - http://www.techcurmudgeon.com Art and Technology - http://www.arttechfusion.com
pager width
Hi, - How to set in the pager mode the line character width to '80' its currently 75. Thanks, - Ravi
Re: pager width
On Fri, Sep 05, 2008 at 11:52:12AM -0700, Ravi Uday wrote: > - How to set in the pager mode the line character width to '80' its > currently 75. Well, I'm no expert in mutt, but as far as I can tell it depends on which editor you use inside mutt. Your default editor is probably vim, so I have this in my .vimrc: "For læsning i mutt au BufRead /tmp/mutt-* set tw=72 Hope it helps :-) -- /Niels Registered Linux user #133791 Get counted at http://counter.li.org
Re: pager width
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Friday, September 5 at 11:52 AM, quoth Ravi Uday: >Hi, > >- How to set in the pager mode the line character width to '80' its >currently 75. It's defined by the $wrap setting (i.e. "at what column should I wrap the text"). Positive numbers set the column, negative numbers allow mutt to adapt to whatever width the terminal is. ~Kyle - -- He who dares not offend cannot be honest. -- Thomas Paine -BEGIN PGP SIGNATURE- Comment: Thank you for using encryption! iEYEARECAAYFAkjBklkACgkQBkIOoMqOI14GyQCfRu9+Md1xdRGcps9WxWO1GSON E+4AnAsgPpVm4dC3qV4eMr+o+D1LAPWz =bFiP -END PGP SIGNATURE-
Re: Configuring sendmail on Mac OS X (Leopard)?
On Fri, 05 Sep 2008, Peter Davis wrote: > > Jorge Luis wrote: >> The server at Pair is relay.pair.com. It authorizes SMTP for 90 minutes >> after a POP3 or IMAP connection. See: >> >> http://www.pair.com/support/knowledge_base/e-mail/smtp_service_at_pair_networks.html >> > Thanks. Anyone know how I configure Postfix on Mac OS X to use that server? I'm away from my Macs and unsure of paths. On unicies: In /etc/postfix/main.cf: relayhost = [relay.pair.com] In /etc/postfix/sasl_passwd: relay.pair.com login:password Run: # postconf -m to find out what types of databases are supported by your system. If you can use hash files, which is likely, (other possibilities are btree, dbm, and sdbm) run: # makemap hash sasl_passwd.db < sasl_passwd Adjust the filetype spec according to your system's capabilities. In /etc/postfix/main.cf smtp_sasl_password_maps = hash:/etc/postfix/sasl_passwd Set restrictive permissions on the sasl_passwd and sasl_passwd.db files. If you run into trouble, the postfix mailing list is tetchy, but informative. Good luck, JL -- Jorge Luis <[EMAIL PROTECTED]> "Mad, bad, and dangerous to know." --Caroline Lamb on Lord Byron
Re: Configuring sendmail on Mac OS X (Leopard)?
* Jorge Luis on Friday, September 05, 2008 at 17:26:07 -0400 > On Fri, 05 Sep 2008, Peter Davis wrote: >> Thanks. Anyone know how I configure Postfix on Mac OS X to use that server? > > I'm away from my Macs and unsure of paths. On unicies: > > In /etc/postfix/main.cf: > > relayhost = [relay.pair.com] > > In /etc/postfix/sasl_passwd: > > relay.pair.com login:password > > Run: > > # postconf -m > > to find out what types of databases are supported by your system. If > you can use hash files, which is likely, (other possibilities are btree, > dbm, and sdbm) run: > > # makemap hash sasl_passwd.db < sasl_passwd hash should work fine. > Adjust the filetype spec according to your system's capabilities. > > In /etc/postfix/main.cf > > smtp_sasl_password_maps = hash:/etc/postfix/sasl_passwd > > Set restrictive permissions on the sasl_passwd and sasl_passwd.db files. I don't know about Leopard but on Tiger to get it actually running as a daemon I had to override /System/Library/LaunchDaemons/org.postfix.master.plist with /Library/LaunchDaemons/org.postfix.master.plist $ cat /Library/LaunchDaemons/org.postfix.master.plist http://www.apple.com/DTDs/PropertyList-1.0.dtd";> Label org.postfix.master OnDemand Program /usr/libexec/postfix/master ProgramArguments master QueueDirectories /var/spool/postfix/maildrop and then: $ sudo launchctl stop org.postfix.master $ sudo launchctl unload /System/Library/LaunchDaemons/org.postfix.master.plist $ sudo launchctl load /Library/LaunchDaemons/org.postfix.master.plist $ sudo launchctl start org.postfix.master And, as your relay server seems to do only smtp after pop, my workaround for these kind of servers is to create a postconnect rule in .fetchmailrc; roughly something like: poll ... postconnect '/usr/sbin/sendmail -q' ... all this just in case it doesn't work all by itself on Leopard ;-) c -- Was heißt hier Dogma, ich bin Underdogma! [ What the hell do you mean dogma, I am underdogma. ] _F R E E_ _V I D E O S_ -->> http://www.blacktrash.org/underdogma/
Re: Configuring sendmail on Mac OS X (Leopard)?
On 05Sep2008 07:09, Peter Davis <[EMAIL PROTECTED]> wrote: >> And the "mailq" command should recite the queue of unsent messages, if >> any. >> > Ah, this could be revealing. I get: > postqueue: fatal: Queue report unavailable - mail system is down > > I don't know how to troubleshoot or start the mailsystem, but that gives > me something to Google. As root, "postfix start" should do it. But the system should already be up. Indeed, the presence of entries in the log suggests it was at some point. If you start it, the command "postfix flush" can force a rerun of deferred items in the queue. You don't normally need to do that because they will get rerun anyway, but for debugging it is useful to watch things (fail) right not. Having a "tail -f the-log-file" running in another terminal is handy too. -- Cameron Simpson <[EMAIL PROTECTED]> DoD#743 http://www.cskk.ezoshosting.com/cs/ It is impossible to travel faster than light, and certainly not desirable as ones hat keeps blowing off. - Woody Allen
Re: Configuring sendmail on Mac OS X (Leopard)?
Jorge Luis wrote: I'm away from my Macs and unsure of paths. On unicies: In /etc/postfix/main.cf: relayhost = [relay.pair.com] In /etc/postfix/sasl_passwd: relay.pair.com login:password Run: # postconf -m to find out what types of databases are supported by your system. If you can use hash files, which is likely, (other possibilities are btree, dbm, and sdbm) run: All good so far, but ... # makemap hash sasl_passwd.db < sasl_passwd No makemap on my system. From my Googling, it seems Mac OS X should have this, but I can't find it. Thanks! -pd -- Peter Davis Funny stuff - http://www.pfdstudio.com Ideas Great and Dumb - http://www.ideasgreatanddumb.com Art/Tech Fusion - http://www.arttechfusion.com The Tech Curmudgeon - http://www.techcurmudgeon.com
Re: Configuring sendmail on Mac OS X (Leopard)?
* Peter Davis on Friday, September 05, 2008 at 21:23:38 -0400 > Jorge Luis wrote: >> I'm away from my Macs and unsure of paths. On unicies: >> >> In /etc/postfix/main.cf: >> >> relayhost = [relay.pair.com] >> >> In /etc/postfix/sasl_passwd: >> >> relay.pair.com login:password >> >> Run: >> >> # postconf -m >> >> to find out what types of databases are supported by your system. If >> you can use hash files, which is likely, (other possibilities are btree, >> dbm, and sdbm) run: >> > > All good so far, but ... > >> # makemap hash sasl_passwd.db < sasl_passwd >> > > No makemap on my system. From my Googling, it seems Mac OS X should > have this, but I can't find it. Try above with postmap. c -- Was heißt hier Dogma, ich bin Underdogma! [ What the hell do you mean dogma, I am underdogma. ] _F R E E_ _V I D E O S_ -->> http://www.blacktrash.org/underdogma/
Re: Configuring sendmail on Mac OS X (Leopard)?
Ok, I've done all this, but my outgoing messages still disappear, and the log still says: Sep 6 00:19:46 PFD-Studio-Mac postfix/smtp[4605]: connect to relay.pair.com[209.68.5.9]: Operation timed out (p ort 25) (At least it has the right relay server now.) Thanks, -pd -- Peter Davis Funny stuff - http://www.pfdstudio.com Ideas Great and Dumb - http://www.ideasgreatanddumb.com Art/Tech Fusion - http://www.arttechfusion.com The Tech Curmudgeon - http://www.techcurmudgeon.com
Re: Configuring sendmail on Mac OS X (Leopard)?
Christian Ebert <[EMAIL PROTECTED]> wrote: > > to find out what types of databases are supported by your system. If > > you can use hash files, which is likely, (other possibilities are > > btree, dbm, and sdbm) run: > > > > # makemap hash sasl_passwd.db < sasl_passwd > > hash should work fine. Agreed; and no need for makemap. On Leopard, hash is the default_database_type so you need only type: % postmap /path/to/your/sasl_passwd You also don't need to do any of the Tiger-related reshuffling described by another poster. Just setup the sasl_passwd file and make the requisite entries in your main.cf. And as Kyle mentioned, Postfix is not always running by default on OS X. It "wakes up" to send messages when called by mutt via the sendmail command and then shuts back down after attempting to send the message. -- Sahil Tandon <[EMAIL PROTECTED]>
Re: Configuring sendmail on Mac OS X (Leopard)?
Peter Davis <[EMAIL PROTECTED]> wrote: > Ok, I've done all this, but my outgoing messages still disappear, and > the log still says: > > Sep 6 00:19:46 PFD-Studio-Mac postfix/smtp[4605]: connect to > relay.pair.com[209.68.5.9]: Operation timed out (p > ort 25) Have you checked your pair.com email in the last 90 minutes? Instead of proper SMTP AUTH, they appear to be using some pop-before-smtp setup, so you have to check your pair.com email from 98.217.207.228 (your IP) before trying to connect to relay.pair.com. Just a guess, but perhaps the reason you can relay via pair.com SMTP servers from the office is because pair associates your work IP with your pair account. -- Sahil Tandon <[EMAIL PROTECTED]>
email chess
Years ago, running Window$, I used an application which automated the process of playing chess via email. I don't remember the details, but an email with a chess game file (.pgn ?) would launch an application similar to xboard, and the chess application would create a game file (.pgn ?) for mailing. The automation did away with almost all of the hassle. Is there a Linux package (or perhaps an extension to mutt) which facilitates playing chess via email? Alternatively, is there a good HOWTO on email chess? RLH
