Re: Lee: Re: smail Solution for Dynamic IP's
John Hasler [EMAIL PROTECTED] writes: I've found that it is sufficient to set visible_name to the host part of my popmail address. That is, my email address at BrightNet is [EMAIL PROTECTED] so I put visible_name=win.bright.net in smail/config. This gets my mail out past their anti-spam-relay rules, but with an invalid envelope address such as [EMAIL PROTECTED] If I could just find a way to put jghasler on there instead of the correct username, I be home free. I compose mail in emacs, and have the following in my .emacs: (setq user-mail-address [EMAIL PROTECTED]) Apparently emacs sends the mail to smail with this address and the real name from /etc/passwd, so my mail headers show: From: Bob Hilliard [EMAIL PROTECTED] It should be possible to make any other MUA put a proper From: field in the mail they send to smail. I had difficulty for a long time getting the return_path_field correct. My mail address is 'hilliard', but my user account on my machine is bob. For a long time my return_path_field went out as [EMAIL PROTECTED], which isn't a valid address. I now have the following in my /etc/smail/config: return_path_field= Return-Path: [EMAIL PROTECTED] This return path shows up regardless of what user name I use on my machine. HTH -- _ |_) _ |_ Robert D. Hilliard[EMAIL PROTECTED] |_) (_) |_) Palm City, FL USAPGP Key ID: A8E40EB9 -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: Lee: Re: smail Solution for Dynamic IP's
Bob Hilliard writes: It should be possible to make any other MUA put a proper From: field in the mail they send to smail. That isn't the problem. It is the MAIL FROM address in the smtp transaction that causes difficulty. BrightNet refuses my mail if this address is not in their domain (even though they know my ip!). 'visible_name=win.bright.net' works, but smail insists on prefixing this with $user to generate the address. I'd like to make smail use jghasler instead of $user. I had difficulty for a long time getting the return_path_field correct. So did I, until I got a doamin name. Now I just have to smuggle my mail past BrightNet. Others are not so fortunate, however. -- John Hasler [EMAIL PROTECTED] (John Hasler) Dancing Horse Hill Elmwood, WI -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: Lee: Re: smail Solution for Dynamic IP's
[EMAIL PROTECTED] (Daniel Martin at cush) writes:
However, if smail is handed a from address (either by the SMTP MAIL
FROM: command or by the -f or -r option to the senmail command),
smail will use that address. Therefore it may be perfectly possible
to convince your MUA to hand smail a from address.
Here's an idea then.
First, move the official sendmail out of the way:
# dpkg-divert /usr/sbin/sendmail
Then put a new sendmail in its place (this is a very brain dead
example):
-
#!/usr/bin/perl -w
use strict;
if ((grep {$_ == '-f'} @ARGV) || (!exists($ENV{RETURNPATH}))) {
exec '/usr/sbin/sendmail.distrib', @ARGV;
} else {
exec '/usr/sbin/sendmail.distrib', '-f', $ENV{RETURNPATH}, @ARGV;
}
die sendmail: couldn't exec /usr/sbin/sendmail.distrib: $!\n;
-
Now set RETURNPATH in your environment and smail's sendmail will get
called with -f $RETURNPATH unless there's already a -f in the
command line. (It could have been an sh script, but I don't know how
to look in $@ for -f in bash.) It could be rewritten in C.
This is all completely untested, of course.
--
Carey Evans http://home.clear.net.nz/pages/c.evans/
GNU GPL: The Source will be with you... always.
--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to
[EMAIL PROTECTED] .
Trouble? e-mail to [EMAIL PROTECTED] .
Re: Lee: Re: smail Solution for Dynamic IP's
[EMAIL PROTECTED] (David Stern) writes: This may or may not be justification for refusal, I can't say for sure. My recommendation would be to avoid using potentially problematic fields, of which From (without the colon) seems to definately qualify. He doesn't add a from (without colon) header. This from appearing in the smail logs (and this is the from smail checks) is from the SMTP dialog. Namely the entry MAIL FROM:sender-address - start transaction from sender I think it is also called the envelope (together with the RCPT TO:). If I set the visible name to mindspring.com, then the from looks like: from [EMAIL PROTECTED] Mindspring inserts a return path: Return-Path: [EMAIL PROTECTED] so my returned mail will go to another user. Ciao, Martin -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: Lee: Re: smail Solution for Dynamic IP's
Carey Evans wrote: What about the envelope sender? sendmail writes this as: From [EMAIL PROTECTED] Sun Mar 1 16:12:31 or something similar at the top of the message. qmail puts: Return-Path: [EMAIL PROTECTED] as RFC821 and RFC822 (4.3.1, 4.4.3) suggest. Hi Carey and David, David in another message you were suggesting I not use the from line. Do you know how to turn it off? I haven't found any way to control this line -- smail seems to generate this line as Carey describes for sendmail. Carey, is there a central configuration file for qmail. I would like one file to translate internal names to external names instead of relying on the user to get things right with the MAILUSER? environment variable. Right now it's only one or two users, but I would still prefer the configuration file in case I ever want to handle more people. Is qmail only available for hamm? Any suggestions for building it on bo? Or even better, suggestions to get smail working properly? Thanks, -- Lee Bradshaw [EMAIL PROTECTED] (preferred) Next Level Communications[EMAIL PROTECTED] -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: Lee: Re: smail Solution for Dynamic IP's
[EMAIL PROTECTED] (Lee Bradshaw) writes: David in another message you were suggesting I not use the from line. Do you know how to turn it off? I haven't found any way to control this line -- smail seems to generate this line as Carey describes for sendmail. (This isn't quite what you're asking, but just to clarify things.) If you use normal mailbox files, your will get From lines in them. This is one BSD-ish way of separating messages, and it just happens to have the envelope sender in it. The envelope sender is what smail or another MTA sends in the SMTP transaction: 220 psyche ESMTP HELO psyche 250 psyche MAIL FROM:[EMAIL PROTECTED]# Envelope sender 250 ok RCPT TO:[EMAIL PROTECTED]# Envelope recipient 250 ok DATA 354 go ahead From: [EMAIL PROTECTED]# From can be different Sender: [EMAIL PROTECTED]# Sender can be different Subject: test To: [EMAIL PROTECTED] # This is different test . 250 ok QUIT 221 psyche I'm pretending I Bcc'd this to carey, so the header doesn't contain the envelope recipient. If delivered directly, this message could look something like the following, in [EMAIL PROTECTED]'s mailbox: - From [EMAIL PROTECTED] Mon Mar 2 19:14:40 1998 Return-Path: [EMAIL PROTECTED] Received: (blah blah); From: [EMAIL PROTECTED] Sender: [EMAIL PROTECTED] Subject: test To: [EMAIL PROTECTED] test - Carey, is there a central configuration file for qmail. I would like one file to translate internal names to external names instead of relying on the user to get things right with the MAILUSER? environment variable. Right now it's only one or two users, but I would still prefer the configuration file in case I ever want to handle more people. At one stage I was doing this in a Perl script as part of the serialmail process. You'd need to intercept all outgoing mail somehow and rewrite it, then redeliver it. It sounds a bit hard for me. Alternatively, you could write a script for /etc/profile that looks up the correct addresses and outputs them, so that the shell includes them as: eval `get-qmail-addrs` where get-qmail-addrs prints, for example, - export MAILUSER=c.evans export MAILHOST=clear.net.nz export QMAILSUSER=c.evans export QMAILSHOST=clear.net.nz - Is qmail only available for hamm? Any suggestions for building it on bo? It should build for bo with no problems. Or even better, suggestions to get smail working properly? I only used smail for a couple of days, so I can't suggest anything. BTW, I see nothing wrong with the two example addresses you posted, as part of the header of an email. -- Carey Evans http://home.clear.net.nz/pages/c.evans/ GNU GPL: The Source will be with you... always. -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: Lee: Re: smail Solution for Dynamic IP's
Hi, Well thanks to help from Art, Carey, Daniel, and Martin I think we have the problem narrowed down to the envelope sender (MAIL FROM: in the SMTP dialog). If I connect to the mail server with telnet as Carey suggested, everything is fine. Netscape also has no problem generating mail with the correct headers. Is there a way to get smail to use the From: line as the MAIL FROM: line? I'm having problems with sites rejecting my mail because of these headers. My own isp rejects my mail to their smart host because of this envelope problem. Is smail really a good choice for the default MTA? As more sites implement anti-spam features I imagine new linux users could become very frustrated when their mail doesn't work as well as it does on win95. qmail looks like it handles this problem (according to Carey and the first couple questions in the qmail FAQ.) But new users may ignore software they have to compile. -- Lee Bradshaw [EMAIL PROTECTED] (preferred) Next Level Communications[EMAIL PROTECTED] -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: Lee: Re: smail Solution for Dynamic IP's
I am not sure whether this can help you at all (or whether it has been brougth up before), but the following hack, posted to a debian list a long time ago, works for me in rewriting headers with smail. I am using my university account to connect to the internet, and I want all replies (regardless of who sent it locally) to arrive at that account. This is the smtp entry from my `/etc/smail/routers' file: smtp: driver=tcpsmtp, remove_header=From, insert_header=From: [EMAIL PROTECTED] ($sender_name on satellite), max_addrs=100, # limit on number of addresses -max_chars, inet; # use route-addr addresses for routing -use_bind, # resolve MX and multiple A records defer_no_connect, # try again if the nameserver is down -local_mx_okay, # fail an MX to the local host defnames# use standard domain searching Note the remove_header/insert_header lines. I am using smail 3.2.0.92-1. ---+-- Christian Lynbech | Telebit Communications A/S | Fabrikvej 11, DK-8260 Viby J Phone: +45 8628 8176 | email: [EMAIL PROTECTED] --- URL: http://www.tbit.dk ---+-- Hit the philistines three times over the head with the Elisp reference manual. - [EMAIL PROTECTED] (Michael A. Petonic) -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: Lee: Re: smail Solution for Dynamic IP's
[EMAIL PROTECTED] (Lee Bradshaw) writes: Well thanks to help from Art, Carey, Daniel, and Martin I think we have the problem narrowed down to the envelope sender (MAIL FROM: in the SMTP dialog). If I connect to the mail server with telnet as Carey suggested, everything is fine. Netscape also has no problem generating mail with the correct headers. Is there a way to get smail to use the From: line as the MAIL FROM: line? Short answer: no. This is one of the many reasons I think a new mailer is needed for dailup addresses. However, if smail is handed a from address (either by the SMTP MAIL FROM: command or by the -f or -r option to the senmail command), smail will use that address. Therefore it may be perfectly possible to convince your MUA to hand smail a from address. One thing I'm also doing is rewriting my smail config file each time ppp goes up so that my visible_name is set to the current value (e.g. ppp75.hcf.jhu.edu); this value is also stored in /etc/mailname. -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: Lee: Re: smail Solution for Dynamic IP's
Daniel Martin writes: One thing I'm also doing is rewriting my smail config file each time ppp goes up so that my visible_name is set to the current value (e.g. ppp75.hcf.jhu.edu); this value is also stored in /etc/mailname. I've found that it is sufficient to set visible_name to the host part of my popmail address. That is, my email address at BrightNet is [EMAIL PROTECTED] so I put visible_name=win.bright.net in smail/config. This gets my mail out past their anti-spam-relay rules, but with an invalid envelope address such as [EMAIL PROTECTED] If I could just find a way to put jghasler on there instead of the correct username, I be home free. -- John Hasler [EMAIL PROTECTED] (John Hasler) Dancing Horse Hill Elmwood, WI -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: Lee: Re: smail Solution for Dynamic IP's
On Thu, 26 Feb 1998 22:19:37 EST, Lee Bradshaw wrote: [..] local username had to match the remote username. Check out my web page if you want to see all the effort I've put into HTML so far :^) http://www.mindspring.com/~lee.bradshaw/ And what nice dogs you have. G. If I didn't mention this before, I'm not cc'ing you because ipa.net rejects my from lines as spam. I don't understand why a correct header would be rejected. I'd like to see some details for the basis to this claim, because I use the same address style as you and Daniel. Please tell. I've read the relevant RFC (and more), but some of the terminology is prohibitive to my understanding: - RFC822(STD11) 3.4.6: o Parentheses (( and )) are used to indicate com- ments. o Angle brackets ( and ) are generally used to indicate the presence of a one machine-usable refer- ence (e.g., delimiting mailboxes), possibly including source-routing to the machine. -- What does that bit about one machine-usable reference (e.g., delimiting mailboxes) .. source-routing .. mean? Most importantly are both Joe User [EMAIL PROTECTED] and [EMAIL PROTECTED] (Joe User) in keeping with standards? Is there a more relevant RFC I should be reading? -- David Stern -- http://weber.u.washington.edu/~kotsya [EMAIL PROTECTED] -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: Lee: Re: smail Solution for Dynamic IP's
[EMAIL PROTECTED] (David Stern) writes: On Thu, 26 Feb 1998 22:19:37 EST, Lee Bradshaw wrote: [snip] If I didn't mention this before, I'm not cc'ing you because ipa.net rejects my from lines as spam. I don't understand why a correct header would be rejected. I'd like to see some details for the basis to this claim, because I use the same address style as you and Daniel. Please tell. What about the envelope sender? sendmail writes this as: From [EMAIL PROTECTED] Sun Mar 1 16:12:31 or something similar at the top of the message. qmail puts: Return-Path: [EMAIL PROTECTED] as RFC821 and RFC822 (4.3.1, 4.4.3) suggest. It appears that the Debian list server renames this to X-Envelope-Sender: before passing the message on, which shows that Lee Bradshaw's envelope sender is (or has been) [EMAIL PROTECTED], and yours (David Stern's) is [EMAIL PROTECTED]. At least localhost will succeed in some DNS lookups. (I had my envelope sender set wrong until recently too. It's difficult to notice.) And it *is* forged by spammers. The Return-Path is where bounced email should go, BTW, which is partly why it gets forged. Have either of you received any bounces lately? -- Carey Evans http://home.clear.net.nz/pages/c.evans/ GNU GPL: The Source will be with you... always. -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: Lee: Re: smail Solution for Dynamic IP's
On 01 Mar 1998 16:23:02 +1300, Carey Evans wrote: [EMAIL PROTECTED] (David Stern) writes: On Thu, 26 Feb 1998 22:19:37 EST, Lee Bradshaw wrote: [snip] If I didn't mention this before, I'm not cc'ing you because ipa.net rejects my from lines as spam. I don't understand why a correct header would be rejected. I'd like to see some details for the basis to this claim, because I use the same address style as you and Daniel. Please tell. What about the envelope sender? sendmail writes this as: From [EMAIL PROTECTED] Sun Mar 1 16:12:31 There's some strong negative remarks about the use of the From (without the colon) field in the IETF Mailing Headers Draft: --- 3.4 Sender and recipient indication (1) This header field should From (not not standardized never appear in e-mail being followed by a for use in e-mail sent, and should thus not appear colon) in this memo. It is however included, since people often ask about it. This header field is used in the so-called Unix mailbox format, also known as Berkely mailbox format or the MBOX format. This is a format for storing a set of messages in a file. A line beginning with From is used to separate successive messages in such files. This header field will thus appear when you use a text editor to look at a file in the Unix mailbox format. Some mailers also use this format when printing messages on paper. The information in this header field should NOT be used to find an address to which replies to a message are to be sent. (2) Used in Usenet News mail FromRFC 976: 2.4 for transport, to indicate the path or use in Usenet News through which an article has goneFrom when transferred to a new host. (not followed by a colon) Sometimes called From_ header field. By contrast, the Sender: line is standard (though somewhat vague): The person or agent submitting Sender: RFC 822: 4.4.2, the message to the network, if RFC 1123: 5.2.15- other than shown by the From:16, 5.3.7. header field. Should be authenticated, according to RFC 822, but what kind of authentication is not clear. Some implementations expect that the e-mail address used in this field can be used to reach the sender, others do not. See also X-Sender. or something similar at the top of the message. qmail puts: Return-Path: [EMAIL PROTECTED] as RFC821 and RFC822 (4.3.1, 4.4.3) suggest. It appears that the Debian list server renames this to X-Envelope-Sender: before passing the message on, which shows that Lee Bradshaw's envelope sender is (or has been) [EMAIL PROTECTED], and yours (David Stern's) is [EMAIL PROTECTED]. At least localhost will succeed in some DNS lookups. (I had my envelope sender set wrong until recently too. It's difficult to notice.) And it *is* forged by spammers. Some DNS's confirming localhost (127.0.0.1) is probably why I'm able to post here. Seems wrong, but at the moment I'm glad. The Return-Path is where bounced email should go, BTW, which is partly why it gets forged. Have either of you received any bounces lately? I got bounced mailing today: - '[EMAIL PROTECTED]SIZE=2824' sender address target 'localhost' is not a valid e-mail domain. - In case anyone is picking up and missed my original post, I'll reask my questions. I've read the relevant RFC (and more), but some of the terminology is prohibitive to my understanding: - RFC822(STD11) 3.4.6: o Parentheses (( and )) are used to indicate com- ments. o Angle brackets ( and ) are generally used to indicate the presence of a one machine-usable refer- ence (e.g., delimiting mailboxes), possibly including source-routing to the machine. -- What does that bit about one machine-usable reference (e.g., delimiting mailboxes) .. source-routing .. mean? Most importantly are both Joe User [EMAIL PROTECTED] and [EMAIL PROTECTED] (Joe User) in keeping with standards? -- David Stern -- http://weber.u.washington.edu/~kotsya [EMAIL PROTECTED] -- TO UNSUBSCRIBE FROM THIS MAILING
Re: Lee: Re: smail Solution for Dynamic IP's
David Stern wrote: I don't understand why a correct header would be rejected. I'd like to see some details for the basis to this claim, because I use the same address style as you and Daniel. Please tell. This is from /var/spool/smail/msglog/... I broke it into multiple lines Xdefer: [EMAIL PROTECTED] reason: (ERR151) transport smtp: 451 [EMAIL PROTECTED]... Domain must resolve. It is a criminal offense to send unsolicited e-mail to,from,or through this server. The mail seems to be rejected based on the first line: from [EMAIL PROTECTED] not: From: [EMAIL PROTECTED] (Lee Bradshaw) If I set the visible name to mindspring.com, then the from looks like: from [EMAIL PROTECTED] Mindspring inserts a return path: Return-Path: [EMAIL PROTECTED] so my returned mail will go to another user. I don't know how to get anything besides my user name onto the from line. -- Lee Bradshaw [EMAIL PROTECTED] (preferred) Next Level Communications[EMAIL PROTECTED] -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: Lee: Re: smail Solution for Dynamic IP's
On Sun, 01 Mar 1998 14:34:05 EST, wrote: David Stern wrote: I don't understand why a correct header would be rejected. I'd like to see some details for the basis to this claim, because I use the same address style as you and Daniel. Please tell. This is from /var/spool/smail/msglog/... I broke it into multiple lines Xdefer: [EMAIL PROTECTED] reason: (ERR151) transport smtp: 451 [EMAIL PROTECTED]... Domain must resolve. It is a criminal offense to send unsolicited e-mail to,from,or through this server. The mail seems to be rejected based on the first line: from [EMAIL PROTECTED] not: From: [EMAIL PROTECTED] (Lee Bradshaw) ---IETF Mailing Draft--- - (1) This header field should From (not not standardized never appear in e-mail being followed by a for use in e-mail sent, and should thus not appear colon) in this memo. It is however included, since people often ask about it. not standardized Used to mark header fields defined only in RFC for use in e-mail 1036 for use in Usenet News. These header fields have no standard meaning when appearing in e-mail, some of them may even be used in different ways by different software. When appearing in e-mail, they should be handled with caution. Note that RFC 1036, although generally used as a de-facto standard for Usenet News, is not an official IETF standard or even on the IETF standards track. -- This may or may not be justification for refusal, I can't say for sure. My recommendation would be to avoid using potentially problematic fields, of which From (without the colon) seems to definately qualify. If I set the visible name to mindspring.com, then the from looks like: from [EMAIL PROTECTED] Mindspring inserts a return path: Return-Path: [EMAIL PROTECTED] so my returned mail will go to another user. Regarding lee.bradswhaw going to bradshaw, I thought I read that a dot in this field was not standard and that it may be rewritten if necessary, however I cannot find that now. Again, my impression is that this qualifies as a potentially problematic field entry, and it would be best to avoid the dot. I'm not an authority in this matter, I'm just calling it like I see it. -- David Stern -- http://weber.u.washington.edu/~kotsya [EMAIL PROTECTED] -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: Lee: Re: smail Solution for Dynamic IP's
[EMAIL PROTECTED] wrote: Lee Bradshaw said: Art, is your local user name alemas? My problem is that if I use my isp Yes. And your local user name should be same as what you want as a user name in your e-mail return address (in your case, lee.bradshaw) until we find a solution for sending from any local (local to your machine) account. I'm going to try one more tiny change with Daniel's (hope he doesn't mind) script and get back to you. When we have a complete solution for these kind of accounts (typical dynamic IP PPP's), what say we collaborate to put a good tutorial on a Web page? ;-) Then those who have the know-how can properly format the info for Debian LINUX documentation (or we can learn). By the way, this one replied to you with no header adjustments. _Art I started with a Reply-To: field which I removed once I got the From: line correct. These were the first things I worked on so that other people could reply to my email. I took most of my setup from Daniel Martin's web page. You might ask him to provides links to your page if you want to provide more details on any of the issues. I don't remember seeing a restriction that the local username had to match the remote username. Check out my web page if you want to see all the effort I've put into HTML so far :^) http://www.mindspring.com/~lee.bradshaw/ If I didn't mention this before, I'm not cc'ing you because ipa.net rejects my from lines as spam. -- Lee Bradshaw [EMAIL PROTECTED] (preferred) Next Level Communications[EMAIL PROTECTED] -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Smail Solution for Dynamic IP's
Daniel offered a solution that seems to me to work very (bo used
on this box, so check it) well, except that I changed the smtp-rewrite
in the /etc/smail/routers file to match what it calls in the
/etc/smail/transports file (smtp-remap). I think I typed both in as
smtp-rewrite. I use elm-me+ and fetchmail (for POP downloads), by
the way.
Also, I think it is important to go to the /etc/smail/config file
and make sure your ISP's domain name (not your full machine name) appears
thusly:
visible_name=ipa.net(mine used as an example here)
-domains
hostnames=alemas.ipa.net --(not sure about this line. Is it correct?)
You gurus on the list please take a look the script below, my
suggestions, and the full header of this message. Then please advise.
If it works, maybe it will be useful in the archive. Thank you.
_Art Lemasters
- Forwarded message from [EMAIL PROTECTED] -
From: [EMAIL PROTECTED] (Daniel Gross)
Subject: Re: Problems w/ppp dialup and sending mail
Try the following:
/etc/smail/routers
smart_host:
driver=smarthost, transport=smtp-rewrite;
path=mail.bingo.baynet.de
--
/etc/smail/transports-
[... other transports ...]
smtp-remap:
driver=tcpsmtp, max_addrs=100, -max_chars, inet,
remove_header=From,
insert_header=From:
${lookup:from:lsearch{maps/[EMAIL PROTECTED]
($from:$fullname)}},
remove_header=Message-ID,
insert_header=Message-ID: [EMAIL PROTECTED],
insert_header=Sender:
${lookup:from:lsearch{maps/[EMAIL PROTECTED]
($from:$fullname)}};
use_bind, defer_no_connect, -local_mx_okay, defnames
--
/etc/smail/maps/from--
root[EMAIL PROTECTED] (root)
YOURLOCALUSER [EMAIL PROTECTED] (YOURNAME)
--
--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to
[EMAIL PROTECTED] .
Trouble? e-mail to [EMAIL PROTECTED] .
Re: Smail Solution for Dynamic IP's
To clarify something from my last message in regards to the subject (subject this message, also) at hand, my _machine name_ is alemas. ipa.net is my ISP's domain. Therefore, my full domain name on this machine is alemas.ipa.net. My numerical domain address (e.g., ###.###.###.###) is a different number--only borrowed from my ISP--each time I log on; it is dynamic. Correct me on terms or otherwise, if need be, and thank you. Art Lemasters -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: Lee: Re: smail Solution for Dynamic IP's
[EMAIL PROTECTED] wrote: Hi Art, I'd like to see your solution and also your headers. Could you post a copy of your headers for those of us reading the digest version of the mailing list? Or just reply to this mail? I guess your message will eventually show up in the archive, but it wasn't there yet. Hi, Lee. I CC'd a copy to you just now while posting the answer to the list. I'm a newbie, but maybe my little bit tweaking to your's and Daniel's solutions will help. Oh, and this comes from my LINUX box, so check out the full header, and let me know if anything else needs changing. Thanks. _Art Thanks -- Lee Bradshaw [EMAIL PROTECTED] (preferred) Next Level Communications[EMAIL PROTECTED] -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] . -- Lee Bradshaw [EMAIL PROTECTED] (preferred) Next Level Communications[EMAIL PROTECTED] 331 Wiley Court (770) 319-5605 (Voice and Fax) Marietta, GA 30060 caveat lector -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: Lee: Re: smail Solution for Dynamic IP's
Sorry for the previous empty message. Art, is your local user name alemas? My problem is that if I use my isp for the visible name, I get a from [EMAIL PROTECTED]. Notice there is no colon after the from. This is [EMAIL PROTECTED] Unfortunately my email address is lee.bradshaw and my login on the local system is bradshaw. I think with this from line incorrect mindspring sets the Return-Path: [EMAIL PROTECTED] which sends my bounced email to another user. visible_name needs to be something that can be looked up, because my email seems to be rejected when I use from [EMAIL PROTECTED]. The From: [EMAIL PROTECTED] is correct, but I haven't found a way to modify the username part of the from line to replace bradshaw with lee.bradshaw. [EMAIL PROTECTED] wrote: Hi Art, I'd like to see your solution and also your headers. Could you post a copy of your headers for those of us reading the digest version of the mailing list? Or just reply to this mail? I guess your message will eventually show up in the archive, but it wasn't there yet. Hi, Lee. I CC'd a copy to you just now while posting the answer to the list. I'm a newbie, but maybe my little bit tweaking to your's and Daniel's solutions will help. Oh, and this comes from my LINUX box, so check out the full header, and let me know if anything else needs changing. Thanks. _Art Thanks -- Lee Bradshaw [EMAIL PROTECTED] (preferred) Next Level Communications[EMAIL PROTECTED] -- Lee Bradshaw [EMAIL PROTECTED] (preferred) Next Level Communications[EMAIL PROTECTED] -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: Lee: Re: smail Solution for Dynamic IP's
Lee Bradshaw said: Sorry for the previous empty message. Art, is your local user name alemas? My problem is that if I use my isp Yes. And your local user name should be same as what you want as a user name in your e-mail return address (in your case, lee.bradshaw) until we find a solution for sending from any local (local to your machine) account. I'm going to try one more tiny change with Daniel's (hope he doesn't mind) script and get back to you. When we have a complete solution for these kind of accounts (typical dynamic IP PPP's), what say we collaborate to put a good tutorial on a Web page? ;-) Then those who have the know-how can properly format the info for Debian LINUX documentation (or we can learn). By the way, this one replied to you with no header adjustments. _Art -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: smail Solution for Dynamic IP's
Hi Art, I'd like to see your solution and also your headers. Could you post a copy of your headers for those of us reading the digest version of the mailing list? Or just reply to this mail? I guess your message will eventually show up in the archive, but it wasn't there yet. Thanks -- Lee Bradshaw [EMAIL PROTECTED] (preferred) Next Level Communications[EMAIL PROTECTED] -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
smail Solution for Dynamic IP's
Please take a look at the header for this message for any discrepancies. I am sending this message with smail from a dynamic IP and may have an answer or two for others. By the way, this was sent using elm-me+ and fetchmail, also. Art Lemasters: -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
