Bug#244724: EXIM-AUTH
tags #244724 upstream user [EMAIL PROTECTED] usertags #244724 valid-bug thanks On Sat, Nov 26, 2005 at 05:25:47PM +0900, Osamu Aoki wrote: > I forgot to attache diff. > Here is one. I have committed some changes to svn. Thanks for providing a great starting point. Relevant to this bug may also be the discussion following http://www.exim.org/mail-archives/exim-users/Week-of-Mon-20050221/msg00348.html, the essence of the outcome being Andreas writing: > We'll need to use a smarter lookup with or or save the original name > in $hosts_data. That smarter lookup has, however, not proven to be done easily, since we need to search for a line in passwd.client where the first field resolves to the IP we're connected to. This query-style lookup for text files is not yet possible in exim (http://www.exim.org/bugzilla/show_bug.cgi?id=65). The better possibility would be to select the authenticator in the transport where we still know the configured smarthost name for directly matching against passwd client. This also is not yet possible in exim (http://www.exim.org/bugzilla/show_bug.cgi?id=66). Since it would be extraordinarily hard to solve this with current exim (unless a new exciting idea comes up), I am going to tag this bug upstream and let it rot away until exim provides means to do this easier. Greetings Marc -- - Marc Haber | "I don't trust Computers. They | Mailadresse im Header Mannheim, Germany | lose things."Winona Ryder | Fon: *49 621 72739834 Nordisch by Nature | How to make an American Quilt | Fax: *49 621 72739835 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#244724: EXIM-AUTH
On Fri, Jan 06, 2006 at 02:32:39PM +0100, Marc Haber wrote: > tags #244724 upstream > user [EMAIL PROTECTED] > usertags #244724 valid-bug > thanks > Relevant to this bug may also be the discussion following > http://www.exim.org/mail-archives/exim-users/Week-of-Mon-20050221/msg00348.html Hi, After reading interesing discussion, I realise that it may be useful to have *EASY TO ACTIVATE* configuration option to enable debug output to address request: > In the future (we'll use this case as an example) with situations like > this, can you please provide debug output? It would have shown > exactly what Exim was doing and where it was failing - rather than > have me guess at possible problems and stir up trouble. I hope /etc/exim4/debug.conf should have entry EXIM_DEBUG_LEVEL=5 EXIM_DEBUG_LOG=/var/log/exim4/debug.log or something :-) 0 being no debug output. Shoot me because I did not check if you already have this or not. Just my late night thought... Osamu -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#244724: EXIM-AUTH
I forgot to attache diff. Here is one. Osamu --- README.SMTP-AUTH.orig 2005-11-26 16:42:59.677659816 +0900 +++ README.SMTP-AUTH2005-11-26 17:16:54.624300904 +0900 @@ -2,11 +2,34 @@ == If you want to set up exim as SMTP AUTH client for delivery to your -internet access provider's smarthost put the name of the -server, your login and password in /etc/exim4/passwd.client: +internet access provider's smarthost add a following line +to /etc/exim4/passwd.client: name.of.server.example:mylogin:secretpassword +Here, + "name.of.server.example" is the canonical host name of the SMTP server, + "mylogin" is your login name to SMTP server, and + "secretpassword" is your password to the SMTP server. + +You must be careful about "name.of.server.example". Many ISPs provide +only the alias name of their SMTP server in their guide. You need to +check the canonical name by yourself manually using host command. For +example, if your ISP claims to provide SMTP host service at +vsmtp.xx.point.ne.jp, try: + + $ host vsmtp.xx.point.ne.jp + vsmtp.mb.point.ne.jp is an alias for vsmtpxx.dti.ne.jp. + vsmtpxx.dti.ne.jp has address 202.216.228.xxx + +Thus vsmtpxx.dti.ne.jp shall be used as the canonical host name in +/etc/exim4/passwd.client. When your ISP changes CNAME record for the +alias host name, you need to update /etc/exim4/passwd.client file +manually. + +If you do not know about your password for your SMTP host, you should try +using your POP password as a good guess. + (Lines starting with a hash-mark (#) are ignored.)
