Sponsored Content
Full Discussion: SMTP Error 553
Special Forums IP Networking SMTP Error 553 Post 302099650 by Sergiu-IT on Wednesday 13th of December 2006 09:44:16 AM
Old 12-13-2006
SMTP Error 553

Hello, guys !

I have a problem on one of my servers and I dont't know how to handle it. When I try to send en email to a mailbox from another server I get the following error:

Quote:
user@domain.ro
SMTP error from remote mail server after MAIL FROM:<myaddress>:
host smtp1d.domain.ro [217.x.x.x]: 553 5.3.0 (code 0x009)
Does anyone have an ideea where the problem could be ? Or where should I start looking ? The problem appears only on one domain. When I send messages to mailboxes on any other domains it work without any problem.
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

uploading Zipped files get 553 error

I am trying to upload .zip files to Unix server and get the error 553 qmerev2002.zip: Permission denied, what is my problem?? I am able to load other files and folders fine. (3 Replies)
Discussion started by: CoastGuard1970
3 Replies

2. UNIX for Dummies Questions & Answers

553 config error: mail loops back to me (MX problem)

I recieve 553 5.3.4 mail.xxxx.com config error: mail loops back to me (MX problem?) when I try to send email from client . The message reaches the server and dies there I'm using sendmail 8.12.9 on OpenBSD 3.3. I can check mail on client with no problem Thanks for any help (5 Replies)
Discussion started by: bluehell
5 Replies

3. Shell Programming and Scripting

reason: 553 Requested action not taken: mailbox name not allowed

Hi all I am sending a mail form a AIX5.2 system to a exchangse server. I get a return receipt as follows :- ----- The following addresses had permanent fatal errors ----- ITS-TOSG@mycompany.com (reason: 553 Requested action not taken: mailbox name not allowed) ----- Transcript of... (2 Replies)
Discussion started by: jhansrod
2 Replies

4. Shell Programming and Scripting

FTP 553 error

Hi , I am doing a ftp file transfer to a remote system.I got an error like "553 FTP_ASCII_PUSH: Permission denied. (upload). " please help (1 Reply)
Discussion started by: Satyak
1 Replies

5. Solaris

ftp 553

hello i want to put a file on a rmote system. the file is owned by the user but the parent folder is owned by root. when I cd to the folder where this file exists, I can "put" the file. when I do not cd the folder, and do put "full path of the file", I receive error 553. any idea?... (1 Reply)
Discussion started by: melanie_pfefer
1 Replies

6. UNIX for Dummies Questions & Answers

Smtp

Hi All, I have a unix box which is in a network with windows machine, I am able to send the mails to the user id's with in the unix box. I dont have Internet connection for this box, so I am not able to test if it can send mails to external network or not? I want to know, if SMTP is already... (1 Reply)
Discussion started by: balu_puttaganti
1 Replies

7. Shell Programming and Scripting

Getting error while sending mail via smtp

Hi All, I used before a simple routine code in tcl to send mail. package require smtp package require mime package require Tcl proc send_simple_message {recipient email_server subject body} { set token mime::setheader $token Subject $subject smtp::sendmessage $token \ ... (0 Replies)
Discussion started by: zivsegal
0 Replies

8. Shell Programming and Scripting

FTP Error 553 I/O error.

Hi All, I have a problem when uploading txt file from windows to Unix server. I got 533 I/O error. I am using .bat file and it works for other batches but with this particular batch it doesn't work. thanks guys for helping in advance. (2 Replies)
Discussion started by: sfaqih
2 Replies

9. Red Hat

[Solved] FTP 553 Could not create file.

Hi, We have one server - "ftpserver", just setup with RedHat 5.7. ftpserver is able to get & put from another server, however, other server are unable to get or put in the ftpserver. # su - ftpuser $ pwd /home/ftpuser $ cd .. $ ls -ltr drwxrwxrwx 3 ftpuser ftpuser 4096 Sep 10 09:19... (0 Replies)
Discussion started by: beginningDBA
0 Replies

10. Solaris

SMTP Server 550 5.1.1 User unknown Error

Hello All, I am currently running a Solaris 10 machine as inbound SMTP server i.e. bringing Emails from outside into our company. In /var/spool/mqueue , I have mails that are pending for the past 4-5 days. They are not being delivered and are causing my mount point size to increase. Error... (0 Replies)
Discussion started by: Junaid Subhani
0 Replies
Server(3pm)						User Contributed Perl Documentation					       Server(3pm)

NAME
Net::SMTP::Server - A native Perl SMTP Server implementation for Perl. SYNOPSIS
use Carp; use Net::SMTP::Server; use Net::SMTP::Server::Client; use Net::SMTP::Server::Relay; $server = new Net::SMTP::Server('localhost', 25) || croak("Unable to handle client connection: $! "); while($conn = $server->accept()) { # We can perform all sorts of checks here for spammers, ACLs, # and other useful stuff to check on a connection. # Handle the client's connection and spawn off a new parser. # This can/should be a fork() or a new thread, # but for simplicity... my $client = new Net::SMTP::Server::Client($conn) || croak("Unable to handle client connection: $! "); # Process the client. This command will block until # the connecting client completes the SMTP transaction. $client->process || next; # In this simple server, we're just relaying everything # to a server. If a real server were implemented, you # could save email to a file, or perform various other # actions on it here. my $relay = new Net::SMTP::Server::Relay($client->{FROM}, $client->{TO}, $client->{MSG}); } DESCRIPTION
The Net::SMTP::Server module implements an RFC 821 compliant SMTP server, completely in Perl. It's extremely extensible, so adding in things like spam filtering, or more advanced routing and handling features can be easily handled. An additional module, Net::SMTP::Server::Relay has also been implemented as an example of just one application of this extensibility. See the pod for more details on that module. This extension has been tested on both Unix and Win32 platforms. Creating a new server is as trivial as: $server = new Net::SMTP::Server($host, $port); This creates a new SMTP::Server. Both $host and $port are optional, and default to the current hostname and the standard SMTP port(25). However, if you run on a multi-homed machine, you may want to explicitly specify which interface to bind to. The server loop should look something like this: while($conn = $server->accept()) { my $client = new Net::SMTP::Server::Client($conn) || croak("Unable to handle client connection: $! "); $client->process; } The server will continue to accept connections forever. Once we have a connection, we create a new Net::SMTP::Server::Client. This is a new client connection that will now be handled. The reason why processing doesn't begin here is to allow for any extensibility or hooks a user may want to add in after we've accepted the client connection, but before we give the initial welcome message to the client. Once we're ready to process an SMTP session, we call $client->process. This may HANG while the SMTP transaction takes place, as the client and server are communicating back and forth (and if there's a lot of data to transmit, well...). Once $client->process returns, various fields have been filled in. Those are: $client->{TO} -- This is an array containing the intended recipients for this message. There may be multiple recipients for any given message. $client->{FROM} -- This is the sender of the given message. $client->{MSG} -- The actual message data. :) The SMTP::Server module performs no other processing for the user. It's meant to give you the building blocks of an extensible SMTP server implementation. For example, using the MIME modules, you can easily process $client->{MSG} to handle MIME attachments, etc. Or you could implement ACLs to control who can connect to the server, or what actions are taken. Finally, a suggested use that the author himself uses, is as an SMTP relay. There are lots of times I need access to an SMTP server just to send a message, but don't have access to one for whatever reason (firewalls, permissions, etc). You can run your own SMTP server whether under Unix or Win32 environments, and simply point your favorite mail client to it when sending messages. See the Net::SMTP::Server::Relay modules for details on that use. AUTHOR AND COPYRIGHT Net::SMTP::Server / SMTP::Server is Copyright(C) 1999, MacGyver (aka Habeeb J. Dihu) <macgyver@tos.net>. ALL RIGHTS RESERVED. You may distribute this package under the terms of either the GNU General Public License or the Artistic License, as specified in the Perl README file. SEE ALSO
Net::SMTP::Server::Client, Net::SMTP::Server::Relay perl v5.10.1 1999-12-28 Server(3pm)
All times are GMT -4. The time now is 05:10 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy