Re: virtual domains and IMAP
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Monday, January 22 at 02:18 PM, quoth Travis H.: > Hey folks, the other day I was troubleshooting someone's server > and had to specify the email address _and @domain_ as the > username. Needless to say, the straightforward way ([EMAIL > PROTECTED]@domain) > didn't work. I found that you could use %40 for the first "@" > and that seemed to do the trick. > > Is this worth putting in the manual? Possibly. Is it mutt that translates the %40 into an @ or is that something that the IMAP server is doing? You can also usually specify it like so: [EMAIL PROTECTED] ~Kyle - -- The test of our progress is not whether we add more to the abundance of those who have much; it is whether we provide enough for those who have too little. -- Franklin D. Roosevelt -BEGIN PGP SIGNATURE- Comment: Thank you for using encryption! iD8DBQFFtSI3BkIOoMqOI14RArMKAJ4iNr/VI/eJCX2u2hDmDpGHt7K4fACgu9Q8 qsWLQU8LSZ8KXUxQehJxQUA= =5weB -END PGP SIGNATURE-
virtual domains and IMAP
Hey folks, the other day I was troubleshooting someone's server and had to specify the email address _and @domain_ as the username. Needless to say, the straightforward way ([EMAIL PROTECTED]@domain) didn't work. I found that you could use %40 for the first "@" and that seemed to do the trick. Is this worth putting in the manual? -- ``Unthinking respect for authority is the greatest enemy of truth.'' -- Albert Einstein -><- http://www.subspacefield.org/~travis/> pgpYzkfRnA7K5.pgp Description: PGP signature
Re: Help please with mutt
* On 2007.01.22, in <[EMAIL PROTECTED]>, * "David Hoover" <[EMAIL PROTECTED]> wrote: > I have a system running Red Hat Linux. We did a reboot on December 20, 2006. > Prior to the reboot, mutt was working great. After the reboot, I have no > e-mails going out using mutt. I have tried to manually send an e-mail using > mutt beside the automated script that had been working prior to the reboot. > My hope is that you might be able to spot what is missing to have cased mutt > to have stopped. If a reboot stopped your ability to send mail, but not to read it, then it's very possible that the problem is your SMTP server, not mutt. Check that sendmail (or postfix, or qmail, or whatever you use) is running. You can verify this with ps (is it running now) and chkconfig (does your system run it on boot). -- -D.[EMAIL PROTECTED]NSITUniversity of Chicago
Re: Help please with mutt, but how?
=- David Hoover wrote on Mon 22.Jan'07 at 7:55:40 -0600 -= > I have a system running Red Hat Linux. We did a reboot on > December 20, 2006. Prior to the reboot, mutt was working great. > After the reboot, I have no e-mails going out using mutt. I have > tried to manually send an e-mail using mutt beside the automated > script that had been working prior to the reboot. My hope is > that you might be able to spot what is missing to have cased > mutt to have stopped. Spot _where_??? You didn't give anything to spot, like error-msgs or log-files excerpts (_NO_ full logs, please!). Please see http://www.catb.org/~esr/faqs/smart-questions.html Also see http://wiki.mutt.org/?DebugConfig for trouble- shooting mutt and how to get more info. Also have a look at your local sendmail log-files, somewhere in /var/log/mail or similar, check /etc/syslog.conf for where it is exactly. > I have tried to send e-mail from a regular user as well as root. No no no, never work as root, unless that's required. Mail does not. ;) > Any help you can offer would be greatly appreciated. You must help us first to be able to help you (yourself). -- © Rado S. -- You must provide YOUR effort for your goal! Even if it seems insignificant, in fact EVERY effort counts for a shared task, at least to show your deserving attitude.
Help please with mutt
I have a system running Red Hat Linux. We did a reboot on December 20, 2006. Prior to the reboot, mutt was working great. After the reboot, I have no e-mails going out using mutt. I have tried to manually send an e-mail using mutt beside the automated script that had been working prior to the reboot. My hope is that you might be able to spot what is missing to have cased mutt to have stopped. I have tried to send e-mail from a regular user as well as root. The automated script is: sh -c 'echo "Shipment for Waterloo test email" | mutt -s "Waterloo PackSlip" -a 11-27-06638X.txt [EMAIL PROTECTED]' The mutt -v shows: [EMAIL PROTECTED] CCL.IMPACS]# mutt -v Mutt 1.4.1i (2003-03-19) Copyright (C) 1996-2002 Michael R. Elkins and others. Mutt comes with ABSOLUTELY NO WARRANTY; for details type `mutt -vv'. Mutt is free software, and you are welcome to redistribute it under certain conditions; type `mutt -vv' for details. System: Linux 2.6.9-42.0.3.ELsmp (i686) [using ncurses 5.4] Compile options: -DOMAIN -DEBUG -HOMESPOOL -USE_SETGID -USE_DOTLOCK -DL_STANDALONE +USE_FCNTL -USE_FLOCK +USE_POP +USE_IMAP +USE_GSS +USE_SSL +USE_SASL +HAVE_REGCOMP -USE_GNU_REGEX +HAVE_COLOR +HAVE_START_COLOR +HAVE_TYPEAHEAD +HAVE_BKGDSET +HAVE_CURS_SET +HAVE_META +HAVE_RESIZETERM +HAVE_PGP -BUFFY_SIZE -EXACT_ADDRESS -SUN_ATTACHMENT +ENABLE_NLS -LOCALES_HACK +HAVE_WC_FUNCS +HAVE_LANGINFO_CODESET +HAVE_LANGIN FO_YESEXPR +HAVE_ICONV -ICONV_NONTRANS +HAVE_GETSID +HAVE_GETADDRINFO ISPELL="/usr/bin/ispell" SENDMAIL="/usr/sbin/sendmail" MAILPATH="/var/mail" PKGDATADIR="/usr/share/mutt" SYSCONFDIR="/etc" EXECSHELL="/bin/sh" -MIXMASTER To contact the developers, please mail to . To report a bug, please use the flea(1) utility. The location of Muttrc is /etc. I can sent this to you if you need it. I have searched the Web for references and have not found any that were able to get me back up and running. The person that originally set up the system (and mutt) is no longer with the company and is not available for questions. Any help you can offer would be greatly appreciated. Thank you. David Hoover Illinois Lock (847) 537-1800 x293
