The Tuesday 2005-01-25 at 10:56 -0600, Danny Sauer wrote:
I thought so, but I also thought I had heard somewhere that more complex rules could be used. You see, it can also make sense to choose a different transport based on the from address, similarly to what a MUA does.
I think that's sort of something the MUS *should* be doing. The MTA is handed a message with a recipient because the MTA is supposed to be the "next hop" on the way to the destination.
Yes... it should. Hold on, I don't know the acronynm "MUS". Someone said the other day how to look up those in google, but I forgot. I need a refresher course in google ;-) (I almost do not browse, my connected time costs money, so I minimize it)
Regardless of my opinion on the matter (and how useful it would be to your situation), postfix can't choose a nexthop based on the sender. The transport lookup is only done on the recipient address. If it looked up the sender and the recipient, it would need a way to determine which of the two it should prefer in the event of multiple matches, and that would double the amount of time spent in the trivial-rewrite phase. Now, you could potentially combine some address rewriting filter that, given a sender address, would change the recipient before passing it off to postfix - taking advantage of the user+extension@do.main syntax...
[I'll have to study that syntax] Look. At this moment, I'm trying to download the kernel update. To do this, I connect through teleline, because it has some more bandwidth than tiscali (meaning that probably tiscali doesn't have an access router at my local exchange, but sends the phone call forward perhaps 500 km away. Ftp gets and average of 3-4 Kbps with them). When I started tonight, I could send to this list. A moment ago, I can't. Ok, I say, so say to postfix to route to suse through teleline (teleline uses smtp with authentification). You know what happened? (English version below): Jan 26 02:03:21 nimrodel postfix/smtp[12505]: 4FFC020DD0: to=<suse-linux-e@suse.com>, relay=mailhost.teleline.es[213.4.129.129], delay=56, status=bounced (host mailhost.teleline.es[213.4.129.129] said: 550 5.7.1 ATENCION: Este mensaje no puede enviarse a este destinatario porque esta intentando usar el servidor de correo SMTP de Terra, que solo envia mensajes cuyo remitente sea una cuenta de c orreo Terra. Por favor, cambie la configuracion de su programa de correo, de forma que utilice el servidor SMTP asociado a la cuenta de correo con la cual quiere enviar el mensaje. WARNING: This message cannot be delivered to this recipient because the SMTP Terraserver can only process messages sent from Terra accounts. Please set your email client program to use the SMTP server associated to the mail account from which you intend to send the message. (in reply to RCPT TO command)) Jan 26 02:03:28 nimrodel postfix/cleanup[12501]: 5054520DCF: message-id=<20050126010328.5054520DCF@nimrodel.valinor> ¡&%$@*&%$&%$&%! (4 letter word) ^ 4 See? I can not use the teleline smtp server (my internet connection provider at this instant) if my from address is from tiscali, as it is on this list. So I can not use this relay in the transport file at all! Do you understand the big problem? Do you understand now why I _have_ to email directly, without relays? And also why I can not? Damm. So, my alternative at this moment is to cut off my connection, reconnect through tiscali, and retry hooping for the best. At least tiscali smtp server does accept any from address, but only if my IP is one of theirs. If you get this, it worked. :-}
parameters the script is fed with are:
interface-name tty-device speed local-IP-address remote-IP-address ipparam
Can you switch based on the IP address? Surely their netblocks don't overlap, so you could just use the given IP as a determining factor as to which map you'd use...
If I knew all the ranges they have... remember, we are talking of a provider serving all of Spain. The ranges is not a thing they publish. I can dig each one, one at a time, but all of them... -- Cheers, Carlos Robinson