Tag Info

Hot answers tagged

25

TLS just enables encryption on the smtp session and doesn't directly affect whether or not Postfix will be allowed to relay a message. The relaying denied message occurs because the smtpd_recipient_restrictions rules was not matched. One of those conditions must be fulfilled to allow the message to go through: smtpd_recipient_restrictions = ...


10

Every recent mail server is capable of doing the job with that minimal requirements you provide. You are sending only 800 mails per hour. This can be done in 5 minutes without pain. So check the server that fits your requirements. Any of Sendmail, Courier, Qmail, Exim or (my favorite) Postfix can do what you want. Without any problem. Edit: But I would ...


9

main.cf #relayhost = [smtp.domain.net]:587 transport_maps = hash:/etc/postfix/transport /etc/postfix/transport domaintodeliverdirectyto : * smtp:[smtp.domain.net]:587 Don't forget to postmap /etc/postfix/transport May want to use relay instead of smtp as the transport mechanisim. For reference http://www.postfix.org/transport.5.html


8

It's not an open relay if you are merely accepting any mail from a single IP address. (Open relays accept any mail from anywhere.) In this case, simply add the IP address to mynetworks in your Postfix main.cf. Oh, and don't send spam.


7

I'd imagine the MTA will split up a message for different MXes when it has to. From my experience with Sendmail behavior, this will be when it encounters different next MTAs in the recipient list of a given message. If there's just one next MTA it talks to for a given message, there will be just one transaction. With a smarthost configuration, the next ...


5

If your software follows the RFCs no delay is required. You should be able to send multiple emails in the same connection without delays. If your software just sends messages and relies on delays rather than following the RFCs, there is no correct answer. EDIT: If you read the RFCs you will see mail is sent using a conversational protocol. If your ...


5

I fought with this for a few weeks. Here are the settings that I'm using on 3 ASP.NET websites that use SMTP gateway to send their emails: Address: smtp.gmail.com Port: 587 1) The port is very important. You may have to enter it like smtp.gmail.com:587 in your SMTP server. I haven't touched Microsoft SMTP in years, so I can't remember what the setup screen ...


5

It's probably running postfix, not sendmail. The sendmail command is provided mainly for cross-compatibility. You'll find the configuration files for postfix in /etc/postfix and documentation at the Postfix homepage.


4

Well, the log says it: Nov 4 20:38:34 2-5-8 postfix/local[990]: 1492A3E0C6C: to=<info@bhcom.info>, relay=local, delay=0.12, delays=0.08/0.01/0/0.04, dsn=5.1.1, status=bounced (unknown user: "info") Nov 4 20:38:34 2-5-8 postfix/local[990]: 28ED53E0C6D: to=<razvoj@bhcom.info>, relay=local, delay=0.06, delays=0.03/0/0/0.02, dsn=5.1.1, ...


4

By "accessing my mail via my iPhone" do you mean receiving mail on a client? This usually uses either POP3 or IMAP, not SMTP, and Postfix is not a POP3 or IMAP server. You'd need something like Dovecot to provide POP3 or IMAP access for clients.


4

Unless I misunderstand your design, your relay server will be the one making a direct connection to remote mail servers. Therefore whichever public ip your relay uses should be the one seen (and checked and possibly reported) by the remote server(s).


4

My answer is similar to that of splattne but I have a different interpretation of the Recieved header Received: from 1.1.1.1 [2.2.2.2] by mail.mypersonaldomain.com with SMTP; (date and time) The exact format of Recieved lines varies with different servers, but generally the from part consists of the name given in the HELO/EHLO SMTP command with the IP ...


4

Add the following to your sendmail.mc: define(`RELAY_MAILER_ARGS', `TCP $h 587') define(`ESMTP_MAILER_ARGS’, `TCP $h 587′) That should get your outbound mail being sent by Sendmail on port 587. You'll also need to have sendmail configured to do TLS. It's a bit beyond the scope of your question, but you can find a lot of decent guides about how to do it ...


4

2 Questions here.. Is is it possible, yes in a backup MX kind of way. I use Postfix as the backup MX SMTP server, so when the main SMTP point is down on the exchange server (due to reboot, patching or whatever) the linux box will store any overflow mail that the exchange server couldn't cope with. How I do it is with MX records in the domain files, ...


4

The queue viewer will tell you why Exchange feels like it's unable to deliver. Running a sniffer and watching the traffic generated after forcing a queue to retry might give you some insight, too. Failing that you can crank up diagnostc logging, too. See http://support.microsoft.com/kb/823489 for details about the queue viewer and diagnostic logging.


4

I think they've always done this, even when you've configured your gmail to send from other domains. As far as I know, the only way around this is to switch to using Google Apps, which is free if you just use the standard edition. The problem with this is that it means you have to change your MX records so that google handles all of your incoming mail, and ...


4

Here's an article related to setting this up in Exchange Server 2007. http://msexchangeteam.com/archive/2006/12/28/432013.aspx


4

According to Micrsoft support: To replay the messages that are located in the Badmail folder, follow these steps: Stop the SMTP service. a. Open IIS Manager. b. Right-click Default SMTP Virtual Server, and then click Stop. Copy all the files that are located in the Badmail folder and that have the .bad file name extension. Then, paste these files to the ...


4

It sounds like potentially 2 different issues potentially at hand. Now I'm the one that provided the answer for the question regarding forwarding through Gmail and mine was done on an Ubuntu laptop configuration not CentOS and I unfortunately don't have a CentOS machine handy to test this on. It sounds to me like the following may be causing the problems. ...


4

The logging that you posted is just showing the attempted establishment of TLS over SMTP between your Sendmail and Google's server and nothing more. If your Sendmail is able to send to other addresses fine, then it is probably functioning. You might send something to a non-Google address to examine its header. That will provide some quick answers to how ...


4

This, tcp 0 0 78.153.208.195:imap 86-40-60-183-dynamic.:10029 is an external connection using IMAP to read mail from a mailbox on your server. This, tcp 0 1 78.153.208.195:35563 news.avanport.pt:smtp SYN_SENT is your server sending outbound SMTP mail to news.avanport.pt Without knowing more about what it ...


3

It's likely that when your machine was sending spam, some of that couldn't be delivered, and ended up in a queue of messages to be retried later. The bit of the log message that reads "stat=Deferred: Connection refused by www.spdcom.info.com" indicates that. I would run (assuming you're running sendmail) sendmail -bp and check to see what messages you ...


3

Sorry Shane. But Shane is wrong with his recommendation. Now you refuse any connection from outside! It must be smtpd_recipient_restrictions = permit_mynetworks, reject The previous configuration is not the problem. The parameters Shane misses are implicitly set by Postfix if you don't set them. Not smtpd_client_restrictions but ...


3

This is similar to my exim setup. From within my network I can send email to any domain, but from outside the network the only mail exim will deliver to is my local domain, unless the user authenticates to exim first. In this way, I can send mail through my mailserver from anywhere in the world, as long as I authenticate first. Critical sections of my ...


3

It seems that you're trying to set up an SMTP gateway, and do not want to expose your Exchange Server to the "outside" network, right? Because usually I'd just set up the appropiate MX records for the domain. Postfix, by design, won't accept mails for foreign domains, but postfix wouldn't be postfix if it wouldn't be possible. It just requires you to do a ...


3

If you are providing email hosting you should really provide an authenticated and encrypted SMTP relay for users to use. If you don't provide one they would have to use an SMTP server provided by their ISP, which complicates their configuration and makes debugging email problems more difficult. Moving email hosting is not completely transparent and has to ...


3

Yup, it's quite easy with a Receive Connector. I do this on Exchange 2010 at my organization, for example. Server Configuration -> Hub Transport -> Receive Connectors -> New Receive Connector Name it something like "Trusted IP's", leave the default "listen on all interfaces on port 25" rule, then finish the wizard with defaults. Right-click on the ...


3

I switched from windows own SMTP/POP3 services to hmailserver a few years ago, never looked back. I assume you're talking about windows 2003 or earlier here, as 2008+ has no inbuilt mail services AFAIK - this is a decision that microsoft made, and it's very unlikely they'll change this policy, as it was introduced to push sysadmins into using exchange.


3

Yes, doable. But you will have to upgrade to Exchange 2010 - seriously. 2007 / 2010 are all about distributed storage architectures, having a mail procesing backbone, distributed storage etc.



Only top voted, non community-wiki answers of a minimum length are eligible