Hi,
I use Postfix.
The firewall allows to connect on the port 25
I try a telnet on localhost on port 25 => it works
Myhost:~# telnet mail.myhost.fr 25
Trying XX.X.XX.XX…
Connected to myhost.
Escape character is ‘^]’.
220 XXXXXXX ESMTP Postfix (Debian/GNU)
when I try on an other network (at home)
telnet mail.myhost.fr 25
Trying 88.191.79.97…
It finishes by a time out.
May I provide the main.cf ?
I get rid off this mails problems
is there is a special support for bought virtualmin ? -
Where you’ll need to replace virtualmin.pem with your SSL certificate–you can use a self-signed certificate, if you like, though most mail clients are very chatty about it if you do. (We actually use a cheap chained certificate from GoDaddy, and use the smtpd_tls_CAfile option to specify the CA.)
hi , I crashed everything
start from a brand new install … it does not work !!!
I desactivated the SMTP protection "offered" by the provider
SMTP should be like a fresh virtualmin install, I launched nmap a part of the result is :
25/tcp filtered smtp
What Why how ?
I modified "Restrictions on recipient addresses" to :
permit_sasl_authenticated permit_mynetworks reject_unauth_destination
I’m gonna losse my mind … mail is so … you know … so …
SMTP should be like a fresh virtualmin install, I launched nmap a part of the result is :
25/tcp filtered smtp
Something is still blocking port 25. Again, I suspect your ISP.
But, you should stop iptables on your server just to be sure you don’t have some extra rules that our iptables configuration doesn’t know how to fix (some third party firewall scripts will overwrite our additions and generally make a nuisance of themselves…if you only use firewall tools that manage the standard iptables-save rules, then you should be fine).
true … You just rock !
There is a SMTP “protection” on my box… I had to desactivate it
There was a SMTP protection too in my provider’s dedicated server !
So, I can use the SMTP port as I want, I can send mails … Fun.
Now … I cannot recieve MAILS !!!
AAARRRGGGGGG, I’m green … I’m not D. Banner anymore … AARRRRGGG
The mails are blocked in the postfix mail queue !!
“Mail Queue 1 messages”
Hehehe…We’re still not getting to the heart of the matter–we need to see the log entries related to the failure you want to fix, not just random log messages. The mail.log contains details about every message that comes in and out of your server, plus some other stuff related to the smtpd, pop/imap, and saslauthd servers.
e.g., try to connect with your mail client, and watch the log while you do so–that is the only way we can figure out why sending mail is failing.
We’re probably looking for saslauthd: messages, but they might also be postfix/smtpd: messages. We don’t know until we see them.
I have a couple people having this issue (where their ISP is blocking port 25)…
Any further enlightenment on the postfix setup for this? i.e. a more precise postfix config (ssl creation with a key, without a key, etc.)…
Between being a noob at postfix and VMPro I’d rather be careful than fast right now. But do have a need (and the Fedora/Centos docs arn’t helping… sigh.).
I disabled the anti-virus CLAMSCAN and it works now !
I just can’t believe it … I tried to make it work as daemon, but it didn’t changed anything but left my processor stressless
Joe, thanks for the Help.
Conclusion :
My Postfix conf works since the begenning
Problems were :
[li]my triple play box blocked the port 25[/li]
[li]the clamscan blocked every mails[/li]
[li]clamscan used 99% of the proc[/li]
[li]clamscand blocked every mails[/li]
Hmmm…that’s a pretty dramatic failure mode for clamscan! We can probably help you resolve that problem (without losing AV scanning), if you want to post the relevant procmail log entries where you see mail being stopped by clamscan.