![]() Response given for invalid recipient errors message is prefixed by email address. Syntax: g_rcpt_max_in int g_rcpt_msg – Invalid recipient response This limit is only applied to untrusted sessions (incoming mail) Syntax: g_rcpt_max int g_rcpt_max_in – Limit for recipients of untrusted channels, default g_rcpt_max Max recipients per message, default is 1000, can only be lower than 1000. Syntax: g_rcpt_colon bool g_rcpt_max – Max recipients per message, default is 1000 Syntax: g_rcpt_bang bool g_rcpt_colon – Allow colon characters in addressesĪllow colon characters in addresses. > Looking for product ideas? visit _ _G_rcpt_bang – Allow bang characters in addressesĪllow exclamation marks in addresses. > 7188 Main Street | Cincinnati, OH 45244 I believe he works via his wireless connection at home as does most of our remote employees but he seems to be the only one having issues and seems to believe it could be my problem since I run the mail server. Could it have something to do with his network connection. > I have no idea why he is having this issue and it is driving him and I nuts. If it does not, change the port number in the Advanced tab of Account preferences." Also verify that the server accepts connections on port 143. Check your network connection and that you entered the correct information in the Account preferences. ![]() > "Could not connect to this IMAP server. > At the same time he gets an IMAP message like this: Check your network connection and that you entered the correct information in the Account preferences." > "Could not connect to this SMTP server. > He gets an SMTP connection message like this: Sometimes he connects just fine then an hour later he cannot. > He is using Apple Mail on OSX Mountain Lion. > I have a user that intermittently cannot connect to Surgemail and I'm wandering if there is anything I could do to resolve the issue. > If you have a VPN server, you could try setting him up to connect over VPN and see if that makes the problems go away, or alternatively if his VPN connection drops all the time due to the same network issues. ![]() > The error messages certainly seem consistent with a networking issue. I think we're just seeing ever more networks (and perhaps also other transmissions on the same unlicensed 2,4 GHz frequency band). > In my experience, Wi-Fi has been getting less and less reliable over the years, at least in the city. > You could also try to monitor his connection, even by simply running ping in a Terminal window in the background. > If at all possible I would try to convince him to work over an Ethernet connection for a while to rule out problems with his wireless connection. > On Jul 30, 2013, at 11:20 AM, Chris Ferebee > wrote: > I definitely agree he should try connecting hard wired as well as from a different location (wired and wireless) as he could be having an issue with his wireless card. > Are you using SSL, I've had issues if I didn't force Apple Mail to use the ssl ports. > Additionally when your client is experiencing these issues can they browse the web, of use the surge mail web front end? > Apple mail in 10.8 has a connection doctor under the pull down item "Window" it's the 8th item down. > I would expect he is experiencing some sort of network connectivity issue. > I, and a number of my clients use 10.8 without issue. He's tried it at his dads wireless network and also has the same issue unless he changes his smtp to uses his dads service provider (ie. > He can still browse the web when the connection is down. > Hmm, based on that, what ports is he using for smtp, pop (if using pop, I know you commented in imap) and imap ports? 465/587 for smtp, 993 for iMap? > On Jul 30, 2013, at 12:00 PM, Glenn Meadows wrote: Beck" He should definitely be using 587 for SMTP as most ISP's block 25 > It's really best to use SSL and get a proper certificate. > It's convenient to set Apple Mail to "use standard ports" for SMTP, which will try ports 25, 465 and 587 as necessary, but if your server offers SSL with self-signed certificates, this will often cause SSL to be enabled automatically as well, which results in "untrusted certificate" errors later on. On Jul 30, 2013, at 12:21 PM, Chris Ferebee wrote: I have also had Apple Mail not use SSL when it was available.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |