Tag Info

Hot answers tagged

6

You could also just let your switch be the DHCP server as well. Multi-homing Windows is frequently a bad idea. Unless you do it perfectly right you can have weird DNS and routing issues. You are better off using a relay agent.


4

This is cited from http://www.tipstrs.com/tip/13296/Setting-up-sendmail-with-a-catch-all-for-unknown-email-addresses If you're running sendmail on a Linux server, it's quite easy to configure sendmail so that any email sent to an unknown email address in your domain is forwarded to a known address. Doing this results in getting a bunch more spam, but I ...


4

It would be (much) easier to do this if you had different SMTP domains but yes, you can create do this. See Receiving routing - Use dual delivery under Routing examples and use cases.


4

Just put postfix1.com in mynetworks on mail.postfix2.com.


4

The problem is that you are not authenticating via SASL. You have this set on submission: -o smtpd_client_restrictions=permit_mynetworks,permit_sasl_authenticated,reject The first allows mynetworks (which seems to be only localhost), the second allows ony authenticated users. Your log shows you establishing an anonymous TLS connection, but no SASL auth. ...


3

"helo command rejected" means that your "A" server didn't even get as far as the first verb in the SMTP Relay conversation. The envelope sender and recipient are thus not the problem. They haven't even been sent at the point that the error occurs. The error is response code 554, extended response code 5.7.1. This is the conventional "I don't want to talk ...


3

If this message is an inbound message and you have accounts setup for ned@example.com, if its a standard non-virtual domain setup, you need to ensure that example.com is on your mydestination line, if it's virtual make sure you have a virtual_mailbox_domains entry, and that it points to a file/hash/database table that contains example.com. If you're testing ...


3

Local domains are any domains which are on the server and mail to those addresses is delivered to a local mailbox (or a local alias), eg. john@example.com and john@example2.com both deliver to john's mailbox on the server, no separation. A virtual domain is similar, but there will be separation (eg. /var/spool/mail/example2.com/john is a mailbox). A ...


3

Sendmail is able to do this with the LDAP Routing feature.


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.


3

smtpd_receipient_restrictions are matched from left-to-right, first match wins. You want smtpd_recipient_restrictions = permit_sasl_authenticated, reject http://www.postfix.org/SMTPD_ACCESS_README.html


3

IMHO, your best option is using an exim/spamassassin combination, cofigured to reject mail at STMP time (i.e. before accepting it) to mitigate backscatter. Add in some RBL whitelisting/blacklisting to refuse or (better?) greylist inbound mail at connection time. This should be sufficient to reduce the queue size. There's lots of info on how to configure ...


3

Why would you want to do that this way? It's not going to work. At least GMail rewrites all mail it receives via an authenticated connection to the mail address connected with this account, so a mail from user@example.com would be rewritten to come from yourgmail@gmail.com. Try to explain to your users why all mail they send to GMail appears to come from ...


3

It sounds as though you are speaking of a reverse proxy. The way this would work is that you would run the reverse proxy in your DMZ. You would give the URL of the reverse proxy to your outside users. When the users browse to the URL you gave them, your reverse proxy receives the connection and request. It then translates or rewrites or just forwards the ...


3

I would definitely lean towards the relay agent. While it may not be a huge concern, giving the server a NIC into that network will open up more possible security vulnerabilities (or will require more effort to lock that server's firewall down a little more. Another benefit of using the DHCP Relay is that if for some reason you need to switch your DHCP ...


3

I too agree that configuring a DHCP relay agent is probably the right way to go about this. Multi-homing a Windows server is generally not a recommended configuration except in very specific use cases.


3

Big Warning Generally including special character like ! or % in the local part of an address is usually a bad idea. Exclamation mark a.k.a ! is a site separator in ancient UUCP addresses. For the safety, you should limit local part of email address to common characters such as [A-Z][a-z][0-9]-.+. It will preserve compatibility across other mailserver in ...


2

In the end you basically have to sync two password files, or with some more type could probably use one mysql table to auth the client with postfix and then get postfix to query the same table to auth with gmail. Another idea might be to find a PAM module that authenticates against gmail. Anyway I used this guide http://braiden.org/?p=15 to set up the ...


2

This should work (not tried it, though): Define a separate transport for the other domain and then route mail to this transport using sender_dependent_relayhost_maps option in main.cf. Something like this: In 'master.cf': smtp-other unix - - n - - smtp -o smtp_helo_name=my.other.helo.name In 'main.cf': ...


2

Take look at Managing multiple Postfix instances on a single host, but be aware that multi-instance support is only available with Postfix version 2.6 and later.


2

smtp_recipient_restrictions are evaluated in order. You probably want something that at least starts like this: smtpd_recipient_restrictions = permit_sasl_authenticated permit_mynetworks And then proceed to either reject all (if you are only sending mail and never receiving mail on this server) or reject ...


2

It looks like this is the address the server is trying to use to send mail: alleart@V100723TU7C41-1 and it's being rejected. You may need to specify a valid email address in your php.ini file, or request a change through your hosting provider.


2

WINS and/or the later versions of DNS (which allow auto-registration - Bind 9 and up). Note: neither are NetBIOS, but replacement technologies for spanning/extending Windows resolutions across networks.


2

The MAPI clients don't care how their email is sent out by the server. All they know is that they have Outlook connected to Exchange and when they send an email it goes to the server for delivery. Any changes you do to the outgoing server ports won't be noticed by the Outlook clients. No config changes necessary.


2

you'll need to set up a transport map for b.com http://www.postfix.org/postconf.5.html#transport_maps where the map consists of something like: b.com smtp:mail.b.com:25


2

The relay_domains parameter determines which domains Postfix relays to -- that is, the domains that your email server will accept mail for in addition to its mailname -- so this line isn't going to help you here (I assume this is what you are trying to achieve with it, anyway). You are restricting the MAIL FROM address to those listed in /etc/postfix/access ...


2

It says that the error is a timeout, not a rejection. You have a networking problem not a mail problem. Try connecting with nc or telnet to see how long it takes. Use mtr to see what your packet loss is.


2

Yes, absolutely. It's a little odd for the clients to be unable to route unicast to their DHCP server, but it's not at all a problem; they'll just renew later on in their lease lifetime (which gives you a little less leeway for downtime on the DHCP server).


2

It sounds like you need to allow relaying from server1 on the second server. http://www.sendmail.org/tips/relaying


2

In Exchange 2007/2010 you have to manually enable a receive connector to allow permission for open relay. Run this against your default send connector (the one that accepts from public address space): Get-ReceiveConnector "Your default Receive Connector" | Get-ADPermission -Identity "NT AUTHORITY\ANONYMOUS LOGON" If that comes back with ExtendedRights ...



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