[Alpine-info] Full headers show something else

[Andraž 'ruskie' Levstik]

:2010-01-17T20:26:Dan Mahoney, System Admin:

More OT ;)


> Technically speaking, if you are using alpine on a system that is not always

> connected to the net in the same place, you should be speaking to the SMTP

> server for whomever hosts your inbound mail, doing SPF, and speaking on a port

> other than 25, since it's currently considered a standard best practice to

> block port 25, and if you run an access network (like a college network), you

> should be.


Erm... sounds like stupidity. I believe most if not all mail servers use
port 25 for receiving. Anything other than that would cause failure in
receiving mail from them. Unless you meant outbound port 25 in which case
yes. That is a good idea.


> The two trivial answers are a) run sendmail in "submit" mode wherever you run

> alpine, and let that handle your background sending or b) take out that

> sendmail instance and have alpine speak to the MSA server at your ISP.  Note

> that in either case, there's AFAIK no way to "save" your auth credentials (at

> least the password), unless you're doing certificate auth.


Using something like esmtp/ssmtp to do local -> remote delivery helps as
well :)

Ow yeah and quite a few SMTP servers support SMTP AUTH in which case a
server usually won't complain as who you are sending.

As for SPF and DKIM... no thanks. Same goes for RBL and a ton of other
checks servers do against mail.

This all of course being just my opinion :)
-- 
Andraž 'ruskie' Levstik
Source Mage GNU/Linux Games/Xorg grimoire guru
Re-Alpine Coordinator http://sourceforge.net/projects/re-alpine/
Geek/Hacker/Tinker

Quis custodiet ipsos custodes?