Per-domain SMTP host name

Henry Sværke · Post by **Henry Sværke** » 2008-03-27 07:33

Self-explanatory.

Thank you

redrummy · Post by **redrummy** » 2008-03-27 08:07

If you mean like with HTTP 1.1 host headers, it's not really possible in the same way. With SMTP, like HTTPS or FTP, the client doesn't send a hostname request before the server sends its banner, so it wouldn't know which hostname to use. I suppose if you have multiple IP addresses on the server you could bind different host names to each IP, but that's another matter...

Post by **martin** » 2008-03-27 08:08

Why would you want this to start with?

mattg · Post by **mattg** » 2008-03-27 09:00

I'm not sure about how multiple domains work, or why Henry was asking, but...

I could see that if you were hosting a couple of domains and their mail, say domain1.com and domain2.com and you wanted the users for each domain to specify as SMTP server in their e-mail clients say mail.domain1.com for the users of domain1.com and mail.domain2.com for users of domain2.com that a per-domain SMTP host name could be warranted.

I suspect that multiple SMTP names are set within the appropriate MX records, and that they all just point to the correct ip address.

Matt

redrummy · Post by **redrummy** » 2008-03-27 16:43

You can have multiple DNS records (A or CNAME) for the same host IP without any modification to hMailServer. But no server can know which hostname to answer with when receiving mail. That's a limitation of SMTP, not hMailServer.

Multiple hostnames, could work for outbound mail, the server sending a HELO with the same domain as the sender. Maybe that's the only goal, to have HELO's match senders. But you still can't use more than one hostname to receive mail unless you have multiple IP's.

Henry Sværke · Post by **Henry Sværke** » 2008-03-28 11:35

Alright, here's the deal, sorry about the confusion.

Hotmail's getting pickier with my mail everyday and I figured out that one of the elements causing trouble is mismatching names. In short, the SMTP host name must match whatever's after the @ if I want to successfully get my mail thru. Why? no idea, probably some sort of anti-spam mechanism.

Example of a working config:

SMTP host name: mydomain123.net
E-mail address: me@mydomain123.net

Example of a config Hotmail does not like:

SMTP host name: mydomain321.net
E-mail address: me@mydomain123.net

The reason I need per-domain SMTP hostnames is the fact that I'm working with several domains and the hostname has to be changed quite frequently for the reason exposed above.

^DooM^ · Post by **^DooM^** » 2008-03-28 13:08

Have you setup an SPF record? I'm sure hotmail is not blocking for that reason alone else half the ISP's and hosting companies on the planet would never be able to send email to hotmail.

Henry Sværke · Post by **Henry Sværke** » 2008-03-28 13:20

SPF, Sender ID, MMX, everything, but it's this very specific thing what does the trick. I have no explanation, in fact, a year a go or so it wouldn't even work no matter what

Henry Sværke · Post by **Henry Sværke** » 2008-04-05 19:10

Not to be pushy but any chance of this happening at all?

^DooM^ · Post by **^DooM^** » 2008-04-05 20:07

I believe Martin takes paypal payments.

Post by **martin** » 2008-04-05 21:22

Almost no servers I've seen uses separate host names for separate domains. Yet they manage to send to Hotmail. I send email to Hotmail often from an address hosted on my server like you describe with no problem. Are you certain that this is the silver bullet that will solve the problems for you?

Henry Sværke · Post by **Henry Sværke** » 2008-04-07 06:18

I'm pretty sure. and I can confirm this is not something related to my PC by sending mail using the hmailserver installation at the office.

Shiloh · Post by **Shiloh** » 2008-06-18 20:33

Henry: The feature you are asking for is not required for sending to hotmail. What is required is that the SMTP hostname matches the reverse DNS entry AND that the reverse DNS entry resolves to the same IP. For example, if your email server says its name is mydomain123.net, then the IP of the mail server must reverse DNS to mydomain123.net. And mydomain123.net must resolve to the IP of the mail server.

Also, I suggest creating a SMTP hostname like mail.domainname.com instead of using just domainname.com. That way if you separate the email service from the web service, there will not be any problem. So in your example, set up mail.mydomain123.net to point to the email server's IP. Then set up the reverse DNS for the IP to point to mail.mydomain123.net. And then set the SMTP hostname in hmailserver to mail.mydomain123.net. If you do not control the reverse DNS for your IP range, you will need to ask your ISP to do the reverse DNS for you.

Henry Sværke · Post by **Henry Sværke** » 2008-07-22 06:04

Been there and done that, but it doesn't seem to change a thing

.

Just curious, but even though it wouldn't be a priority, would this really be that hard to implement?

^DooM^ · Post by **^DooM^** » 2008-07-22 11:21

Please post the domain name you are having problems sending from.

birendersinghbudhwar · Post by **birendersinghbudhwar** » 2008-08-06 09:11

Hi,

This is not required to have per domain SMTP host name, you have to give your hosting company domain name in smtp host name. that it.

as according to SPF, sender policy framework. it only checks IP address of your SMTP against the email delivery from where it comes because your smtp server send a host name in helo command and your smtp server send your hosting company domain name like xyz.com to verify that emails is generated from the correct source of SMTP server so receiving server checks xyz.com ip address against your smtp server if ip address is same for the xyz.com and your smtp server then your emails will be delivered to the designated host without any problem.

so there is not need to having multiple host name on smtp server. just follow this your problem will be solved 100% and also check your IP blacklisting status if it is listed then talk to your isp to provide you fresh Ip address. and also check your system for any brontok kind of warms mostly these are the virus which cause most of the IP get blacklisted becasue these viruses generated spam.

Birender

westdam · Post by **westdam** » 2008-09-06 12:03

mmm i believe on Argosoft mail Server PRO it use on SMTP out the domain name used during smtp authentication.

but not so important of course...

FriendSite.com · Post by **FriendSite.com** » 2009-04-17 17:51

I support hMailServer being able to respond with different hostnames depending upon the IP address.

E.g. if a connection came through from 123.123.123.123 it would respond with mail.yourdomain.com and on 234.234.234.234 it would respond with the hostname mail.mydomain.com

This would be simple to add, but valuable in terms of using this as an enterprise mail server, and allowing clients who have their own mailserver IP address having the mailserver respond with the appropriate hostname, both for image purposes and spam.

Another addit to this, would be associating domains to the ipaddress/hostname, so that you could have a default domain for each hostname, not requiring the full email address to validate, rather than 1 default domain for the entire mailserver.

^DooM^ · Post by **^DooM^** » 2009-04-17 19:03

FriendSite.com wrote:This would be simple to add

Really? Then feel free to download the V4 source code and add it

zordex · Post by **zordex** » 2009-07-02 16:49

My machine has multiple IP addresses, and I would like to use different domains on different IPs. However since the HELO request always returns the same host name regardless of domain, this creates a serious issue with outgoing mail appearing as spam since the HELO resolves only to one IP, regardless of domain. I hence cannot use my other IPs, to prevent outgoing mail appearing as spam

The HOST name has to be moved into per domain, and the replies to SMTP and HELO identification must then be looked up per domain.

hMail is fantastic, and free (thank you!). But if possible I would like to know if this functionality is coming soon? Otherwise I may have to bite the bullet and go with smaterMail or another tool that does support this

Post by **martin** » 2009-07-02 19:17

Suggest you use another server if this is vital for you. I've heard a rumor saying that 99.99% of all people can apparently live without this feature without any problem. Most people doesn't have any need in hosting different domains on different IP:s.

Magnus W · Post by **Magnus W** » 2009-07-02 20:01

zordex wrote:My machine has multiple IP addresses, and I would like to use different domains on different IPs. However since the HELO request always returns the same host name regardless of domain, this creates a serious issue with outgoing mail appearing as spam since the HELO resolves only to one IP, regardless of domain. I hence cannot use my other IPs, to prevent outgoing mail appearing as spam

Then you can run two hMailServer processes listening to two different IPs, I guess. That would be the usual setup for such scenarios.

You could also (if you have lots of IPs) setup a SMTP smarthost, listening to a firewalled port (say, port 26) bound to only one IP, and see to it that it used that IP's DNS/PTR name as HELO. Then use that local server, additional server as hMailServer's smarthost. Then you could listen to all IP's with hMailServer but send from one IP only, without anyone knowing.

Magnus W · Post by **Magnus W** » 2009-07-02 20:06

But wait, you even have the option Protocols/SMTP/Advanced/Bind to local IP to activate for SMTP delivery. Then I don't understand the problem. Set it to one of you IPs and use that IPs PTR as HELO. You should be fine.

Post by **martin** » 2009-07-02 20:12

Only if he can live with all email being delivered from the same IP address..

Magnus W · Post by **Magnus W** » 2009-07-02 20:16

Why not? A lot of web hotels live with that.

Post by **martin** » 2009-07-02 20:26

If one of your customer is a spammer, other customers may appreciate that they don't share his IP address.

zordex · Post by **zordex** » 2009-07-03 22:08

Magnus W wrote:Then you can run two hMailServer processes listening to two different IPs, I guess. That would be the usual setup for such scenarios.

Any difficulties I should be aware of when running two servers? Will Helm get confused? Memory? Other issues?
.

^DooM^ · Post by **^DooM^** » 2009-07-03 22:32

Only if they are ran in a VM, you cannot run 2 hMailServers on the same "pc"

Magnus W · Post by **Magnus W** » 2009-07-06 17:10

^DooM^ wrote:Only if they are ran in a VM, you cannot run 2 hMailServers on the same "pc"

Why shouldn't that work, running them against separate databases and from separate directories?

^DooM^ · Post by **^DooM^** » 2009-07-06 17:16

If memory serves registry settings prevent multiple hMail installations and that you cannot use the same port for multiple installs.

Post by **martin** » 2009-07-06 17:24

Assuming you get two services up and running, you won't be able to manage them both using Administrator or WebAdmin. The connection protocol between the service and Admin limits this.

Magnus W · Post by **Magnus W** » 2009-07-07 15:53

Even if you are running them bound to different IPs, connecting to those two with Administrator?

cracknix · Post by **cracknix** » 2009-09-06 08:34

Easy clean solution, Local Host Name defined by IP and Port.
Need seperate IP per Domain anyway for clean Reverse DNS.

as discussed here
http://hmailserver.com/forum/viewtopic.php?f=10&t=14356
http://hmailserver.com/forum/viewtopic.php?f=2&t=16022

Post by **martin** » 2009-09-07 18:25

cracknix,
What's funny with your easy and clean solution is that it's not what the person created this thread requested. Please check the subject of this thread. It says 'Per-domain SMTP host name'. Your solution is not that.

cracknix · Post by **cracknix** » 2009-09-08 03:07

okay sorry for that, I and ^DooM^ (other post) may thought it's more or less the same...

But I still think it's worth a feature request.

^DooM^ · Post by **^DooM^** » 2009-09-08 12:35

I did what now? I believe the post you are referring to was my attempt at mild sarcasm as I am prone to use on many occasions

francescosydney · Post by **francescosydney** » 2009-12-27 06:38

Hi All,

I would like this feature if possible. Currently I'm using a white listing service for my emails and each sender IP address gets listed with them. They suggest sending different categories of emails on different IP addresses. For example account activations/password resets on a different IP address to newsletter/marketing emails.

Hotmail has a spam tolerance of about 2.9% If your sender IP address gets flagged as a spammer then it gets blocked for a certain time period. It's important to make sure that if this does happen your mission critical emails (such as password resets) still get through.

cheers

zordex · Post by **zordex** » 2010-07-26 20:06

Just reviving this feature a tad... my IP was recently banned by yahoo/google. Big pain:
http://www.hmailserver.com/forum/viewto ... =7&t=18755

With a different host name per domain, I would be able to assign a different IP for each domain (without HELO resolves appearing as spam), and my domains would not not of been affected.

Bill48105 · Post by **Bill48105** » 2010-07-26 20:20

zordex wrote:Just reviving this feature a tad... my IP was recently banned by yahoo/google. Big pain:
http://www.hmailserver.com/forum/viewto ... =7&t=18755

With a different host name per domain, I would be able to assign a different IP for each domain (without HELO resolves appearing as spam), and my domains would not not of been affected.

If you have more than one public IP then run different hmail server for each.. Unless you have as many IP's as domains that'd be a fruitless endeavor.. Most every mail server has more than 1 domain per IP so key is managing your servers to be sure they are not being abused and if they do get to work cleaning up the mess.

Btw having different hostname (for HELO) is pretty much pointless because you can only have 1 reverse DNS entry per IP and that needs to match your hostname for many servers to accept your mail. If you move your server to a different IP because the current one is blacklisted then you change your hostname to match the RDNS of that IP.
Bill

zordex · Post by **zordex** » 2010-07-26 20:44

Bill48105 wrote: If you have more than one public IP then run different hmail server for each..

Is there a guide for running two instances of hMail?
Any issues or settings I need to be aware of to prevent conflict?
Anyone running this successfully?

Bill48105 wrote: Btw having different hostname (for HELO) is pretty much pointless because you can only have 1 reverse DNS entry per IP and that needs to match your hostname for many servers to accept your mail. If you move your server to a different IP because the current one is blacklisted then you change your hostname to match the RDNS of that IP.
Bill

That's fine, HELO checks are for matching IP, not the name.

Bill48105 · Post by **Bill48105** » 2010-07-26 21:08

zordex wrote: Is there a guide for running two instances of hMail?
Any issues or settings I need to be aware of to prevent conflict?
Anyone running this successfully?

You can't run more than 1 copy of hmail on 1 server (as far as I know) because of COM issues. You'd need to run in a virtual machine or on separate hardware. The whole world does shared hosting with multiple domains on 1 IP so as I said before you're in a definite minority thinking you're going to reduce your headache having 1 domain per server.

zordex wrote:That's fine, HELO checks are for matching IP, not the name.

Umm.. That almost made sense. Nope it didn't.. HELO is not really even supposed to be used for any kind of filtering but it commonly is. Usually the big test is if the HELO string matches the reverse DNS hostname which is obtained from the IP. SOO in turn they are one in the same. In other words your HELO host name should match your RDNS which should point to your host name. Round & round we go, they better complete a circle.

SO if your mail server supports a hostname per domain or if you run 1 server per domain, you better have an IP for each domain witch matching RDNS or you're in no better shape.
Bill

zordex · Post by **zordex** » 2010-07-26 21:17

Bill48105 wrote:You can't run more than 1 copy of hmail on 1 server (as far as I know) because of COM issues. You'd need to run in a virtual machine or on separate hardware...

Well there goes that idea.

zordex · Post by **zordex** » 2010-07-26 21:24

Bill48105 wrote:...HELO is not really even supposed to be used for any kind of filtering but it commonly is. Usually the big test is if the HELO string matches the reverse DNS hostname which is obtained from the IP. SOO in turn they are one in the same. In other words your HELO host name should match your RDNS which should point to your host name. Round & round we go, they better complete a circle.

SO if your mail server supports a hostname per domain or if you run 1 server per domain, you better have an IP for each domain witch matching RDNS or you're in no better shape.
Bill

Would still be in much better shape. Assuming I place half my domains on one IP, with its own RDNS and host name, and another half on another IP, with its own RDNS and host name, the HELO would check out ok. And if one domain is hijacked (and IP get's listed) it would not affect the domains using the second IP. No?

Bill48105 · Post by **Bill48105** » 2010-07-26 21:31

zordex wrote:Well there goes that idea.

Well it was kind of a joke in the 1st place.. Although running 1 domain per server would indeed do what you want not sure anyone would actually do it or a multitude of reasons..

Seriously though almost the entire world runs more than 1 domain per server/IP/hostname just fine and doing otherwise goes in the face of conventional wisdom & frankly is likely a waste in most every circumstance. Set your stuff up properly & securely and sleep well at night.
Bill

^DooM^ · Post by **^DooM^** » 2010-07-26 22:48

assigning SMTP IP per domain would be useful, SMTP Hostname would make no odds to your current dilemma

ObiWan · Post by **ObiWan** » 2010-07-28 15:04

Henry Sværke wrote:Self-explanatory.

Yeah; got it; you're saying that, in case one is using the same hMail box for (say) foo.com, bar.net and taz.org, the server, whenever SENDING out an email should use a different (and "admin" defined) HELO string; that may be ok, although, sincerely, I don't think it's a real urge, see, it's just a matter of defining the MX/SPF for a given domain so that they'll point to the "base" domain for the hMail; an example; let's suppose you have an instance of hMail running on the example.com domain; you may have...

Code: Select all

@       IN MX 10    mail.example.com.
@       IN A        11.22.33.44
mail    IN A        11.22.33.44
@       IN TXT      "v=spf1 mx -all"

now, let's say you want to use the same hMailServer for the domain "foobar.net", all you'll need to do will be publishing some DNS infos (from the foobar.net zone) like

Code: Select all

@       IN MX 10    mail.example.com.
@       IN TXT      "v=spf1 include:example.com -all"

and that would allow you to use "mail.example.com" as the MX for foobar.net without any need to change the HELO string - bottom line; it may be a useful feature BUT, in general, I'd keep it at the BOTTOM of the wishlist

ddivita · Post by **ddivita** » 2011-03-07 15:08

I can see the importance of this feature when it comes to hosting multiple domains with multiple IPs. Reason being, the SMTP headers always look like the mail is originating from the same place. This can be problematic if a user on your system abuses your SPAM policy. It will cause other users on other domains to have their mail appear as spam.

My previous hosting used a similar mail package that only allowed one SMTP host. Some users of their system were abusing their SPAM policy and in turn all of our email to external systems was considered spam. Every email looked like it was coming from (just an example) mail.thehostingcompany.com. Even though, the return address was our domain it didn’t matter. That mail server host and IP were on blacklists everywhere.

What people are asking for is that this software act as an MTA (mail transfer agent). Most MTAs I have seen and used cost well over 10k. Mainly, because they offer you the ability to send mail on multiple IPs and domains, bounce tacking, grey listing, throttling to major providers (HotMail, AOL, Yahoo, etc.), and they are made for bulk mailing. Personally, I wouldn’t want hMailServer to become that. I do, however, like the multiple host idea so you can shut down specific IPs and hosts that may be abusing your system without affecting other users / domains.

ObiWan · Post by **ObiWan** » 2011-03-07 16:09

ddivita wrote: I can see the importance of this feature when it comes to hosting multiple domains with multiple IPs. Reason being, the SMTP headers always look like the mail is originating from the same place. This can be problematic if a user on your system abuses your SPAM policy. It will cause other users on other domains to have their mail appear as spam.

Sorry, but I think you're totally missing the point, see, whatever DNSBL listing
is made on the sender IP not on the "mail domain", sure, URIBLs may eventually
list the domain, but given what you write above it's really hard for such a thing
to happen; see... it's cool relying on 3rd party email services to setup your own
(domain) mail services and, by the way, there's no problem in setting up aliases
so that "mail.someemaildomain.xyz" will appear as "mail.yourowndomain.kwh" but
that doesn't mean that one has to do the same for MX records... it's just silly
in my opinion and doesn't make much sense

ddivita wrote: My previous hosting used a similar mail package that only allowed one SMTP host. Some users of their system were abusing their SPAM policy and in turn all of our email to external systems was considered spam. Every email looked like it was coming from (just an example) mail.thehostingcompany.com. Even though, the return address was our domain it didn’t matter. That mail server host and IP were on blacklists everywhere.

I suspect that the mailserver host/IP had quite a bunch of other issues to get
"blacklisted everywhere" as you say; see, it suffices NOT having a decent abuse
(a working one) or postmaster or having a bunch of fat-assed folks running the
"postmaster" or "abuse" role and not caring about bounces and abuse reports to
get in a blacklist, and the hostname in this case won't play a role at all; again,
I think you didn't get the point nor understood how blacklisting really works (not
trying to give offense, mind me, but that's what one can understand from what
you wrote and there's nothing wrong with it)

ddivita wrote: What people are asking for is that this software act as an MTA (mail transfer agent).

and hMailServer does, sure, it lacks some (really important imHo) features, like
SRS (needed if you need to setup external forwards or distribution lists containing
external addresses), but all in all, it's a good program; then, by the way, one should
also understand how the whole SMTP mechanism works and how to properly setup
the DNS zones; using aliases makes really NO sense and, as I wrote, I think that
the requeste feature, while possibly interesting, isn't a "vital" one

ddivita wrote: Mainly, because they offer you the ability to send mail on multiple IPs and domains, bounce tracking, grey listing, throttling to major providers (HotMail, AOL, Yahoo, etc.), and they are made for bulk mailing. Personally, I wouldn’t want hMailServer to become that. I do, however, like the multiple host idea so you can shut down specific IPs and hosts that may be abusing your system without affecting other users / domains.

hMS can use multiple IPs and domains, has loopback tracking, grey listing and then some.. and to track an abuser you'll just need to look at the logs, there's no black magic in there, and the name the mailserver uses won't help so much; again, I think such a change isn't worth the effort

ObiWan · Post by **ObiWan** » 2011-03-08 00:01

zordex wrote:My machine has multiple IP addresses, and I would like to use different domains on different IPs. However since the HELO request always returns the same host name regardless of domain, this creates a serious issue with outgoing mail appearing as spam since the HELO resolves only to one IP, regardless of domain. I hence cannot use my other IPs, to prevent outgoing mail appearing as spam

The HOST name has to be moved into per domain, and the replies to SMTP and HELO identification must then be looked up per domain.

hMail is fantastic, and free (thank you!). But if possible I would like to know if this functionality is coming soon? Otherwise I may have to bite the bullet and go with smaterMail or another tool that does support this

And... HOW in the name of deities an SMTP listener could know the name to use whenever someone connects to its IP:port ? Not to say that, such a thing is just plain vanilla idiot for outbound email (the HELO string used to send) it just mean that someone didn't either read the RFCs or either didn't understand them, and ignorance, I'm sorry, doesn't justify the request to add a totally dumb "feature" - sure, it may be useful for spamming, but I don't think we're here to contribute to it, then, ok, maybe I'm wrong

acunningham · Post by **acunningham** » 2011-06-06 12:45

Henry Sværke wrote:Alright, here's the deal, sorry about the confusion.

Hotmail's getting pickier with my mail everyday and I figured out that one of the elements causing trouble is mismatching names. In short, the SMTP host name must match whatever's after the @ if I want to successfully get my mail thru. Why? no idea, probably some sort of anti-spam mechanism.

Example of a working config:

SMTP host name: mydomain123.net
E-mail address: me@mydomain123.net

Example of a config Hotmail does not like:

SMTP host name: mydomain321.net
E-mail address: me@mydomain123.net

The reason I need per-domain SMTP hostnames is the fact that I'm working with several domains and the hostname has to be changed quite frequently for the reason exposed above.

I also had problems because first I did not know that the name must match whatever's after the @. I also guess this is due to anti-spam mechanism. I want some new websites and therefore I am looking for a good webhost. If I have these new domains I will also try the config above. Hopefully it will work then.

^DooM^ · Post by **^DooM^** » 2011-06-06 13:30

If they need to match, why don't we just have hmail send the domain name (taken from the users authenticated login) in helo if SMTP host is not filled in, and use the one supplied if it is filled in.

ObiWan · Post by **ObiWan** » 2011-06-06 14:57

^DooM^ wrote:If they need to match, why don't we just have hmail send the domain name (taken from the users authenticated login) in helo if SMTP host is not filled in, and use the one supplied if it is filled in.

Heh... that's what I've been trying to explain; if one doesn't have his own mailserver for a given domain, I can't understand why they can't just use whatever MX (and mailsender) from whatever other (authorized) domain; sounds like folks here around (not all folks, mind me - and not willing to give offense) are mostly "n00bs" when it comes to email and such stuff; heck, nobody forbids one from having a mailserver (say) mail.example.com being listed as an MX in the DNS zones for foobar.org, baztaz.net, bartang.zoo and whozap.xyz

And btw, the mail WILL just work... as it did till now; it's just a matter of understanding how things work, pity that, a lot of people jumps barefoot into setting up a domain and a mailserver w/o even knowing the basics

^DooM^ · Post by **^DooM^** » 2011-06-06 15:29

I send to hotmail using alternate domains to what is sent via HELO without issue. My MX matches my HELO and my PTR which is all that should be required. If hotmail are blocking because the helo doesn't match the senders domain then they will block millions of legitimate email.

ObiWan · Post by **ObiWan** » 2011-06-06 15:41

^DooM^ wrote:I send to hotmail using alternate domains to what is sent via HELO without issue. My MX matches my HELO and my PTR which is all that should be required. If hotmail are blocking because the helo doesn't match the senders domain then they will block millions of legitimate email.

Which is exactly what I was trying to explain; if you own a domain (say doom.xyz) and you want to rely on a 3rd party mailservices (say gmail.com) you'll just need to list the gmail.com servers (and include their SPF record) as the MX for your domain, there's no need to "alias" those; sure, nobody forbids you to setup some "CNAME" reading "mail.doom.xyz" to use for the mail clients or in any case to give "around", but that has nothing to do with the underlying MX configuration

PavlinII · Post by **PavlinII** » 2013-06-20 22:49

Hello,
is this feature request considered to be "Per-domain SMTP outgoing IP address" as well? Or should I submit new one? Can someone update main title?

I have one server with different customers.
I need to separate each customer (or small group of related customers) to his own outgoing SMTP IP address.
It should affect only responsible customer when IP address gets banned.

Per-domain SMTP host name request makes sence only with per domain IP address because there's different IP in use. And different set of DNS records.

WMware nor other subvirtualisation solution cannot be used in my situation.

Bill48105 · Post by **Bill48105** » 2013-06-20 23:32

PavlinII wrote:Hello,
is this feature request considered to be "Per-domain SMTP outgoing IP address" as well? Or should I submit new one? Can someone update main title?

I have one server with different customers.
I need to separate each customer (or small group of related customers) to his own outgoing SMTP IP address.
It should affect only responsible customer when IP address gets banned.

Per-domain SMTP host name request makes sence only with per domain IP address because there's different IP in use. And different set of DNS records.

WMware nor other subvirtualisation solution cannot be used in my situation.

There is a different feature request for multiple outbound IP. As you aluded to the way people are doing it now is run multiple servers since hmail is so light-weight.
Bill

PavlinII · Post by **PavlinII** » 2013-06-21 11:03

Bill48105 wrote: There is a different feature request for multiple outbound IP. As you aluded to the way people are doing it now is run multiple servers since hmail is so light-weight.
Bill

Can you please provide URL for that thread? I just can't find it

Bill48105 · Post by **Bill48105** » 2013-06-21 17:51

PavlinII wrote:
Bill48105 wrote: There is a different feature request for multiple outbound IP. As you aluded to the way people are doing it now is run multiple servers since hmail is so light-weight.
Bill
Can you please provide URL for that thread? I just can't find it

There have been a few but here were 2 related I found:
http://www.hmailserver.com/forum/viewto ... =2&t=17025
http://www.hmailserver.com/forum/viewtopic.php?t=7755

tarrakis · Post by **tarrakis** » 2014-03-05 15:09

Hi everyone.

I just posted a feature request (http://www.hmailserver.com/forum/viewto ... =2&t=26126), but I hadn't seen this post.

To sum it up:

- YES, you can set up a SMTP server on a particular domain (mailing.domain.com) and IP address (1.1.1.1), set the HELO to mailing.domain.com, and make sure DNS and RDNS are consistent.

- YES, it is safe to send from any other domain (eg, mywebstore.com) using mailing.domain.com as SMTP server, assuming that you set up the correct SPF record. You can authorize mailing.domain.com, and even authorize 1.1.1.1 to send emails.

- HOWEVER, if one of the domains sends massive mail (not talking about spam), there can be a problem: people think it's safer to "report spam" instead of unsubscribing, or the email list is not correctly maintained and old/unused/deleted emails are not being removed, etc.
In this case, IP address 1.1.1.1 will be BLACKLISTED, and any email coming from that IP (from any domain that is using mailing.domain.com) will be blocked (sent to spam, or directly deleted without notification).

- This cannot be fixed by domain-specific anti-spam methods, such as DKIM. If the IP is blacklisted, you are doomed (for a certain time), even if the reason for blacklisting came from another domain.

If you could bind a domain to a particular IP address, with it's own HELO and consistent DNS/RNDS, you could isolate the massive mail from the business mail.
What do you think about this?

mattg · Post by **mattg** » 2014-03-05 16:52

I do trust you realise that hMailserver is open source, and you make whatever changes you need for your install yourself.

And are you talking about outgoing mail and incoming mail??
For incoming mail I'm still not sure how you envisage issuing a host name, before whoever is connecting tells you who they want...

I could see a use for sending on different ports depending on the domain of the sender, but that is not this request

Do you need this feature?